Visualize Arm CPU orchestration with Ollama and a local AI agent
Introduction
Understand the agent and how work is split between CPU and GPU
Set up your environment before running the agent
Serve a model locally with Ollama
Understand the concierge agent code
Run the agent and read the timeline
Understand the CPU's role in the agentic workflow
Next Steps
Visualize Arm CPU orchestration with Ollama and a local AI agent
Review frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Confirm Ollama is running and serving the
gemma3:4b model. The local API at http://localhost:11434 should be available before starting the script.Activate your Python virtual environment and set
SERPER_API_KEY in the same terminal session. The agent reads this variable at runtime for web search.You should see a greeting that explains the agent browses websites in real time and a prompt asking for your question. Type
quit or exit to end the session.CPU entries in the timeline correspond to tools (web search, scraping) and the orchestration pipeline (query expansion, ranking, deduplication, extraction). GPU entries correspond to the Gemma model running through Ollama. The agentic chain interleaves these steps.
Open
concierge_agent.py. It groups the tools, the LLM “brain,” the orchestration pipeline, and the agentic chain, and indicates which components run on the CPU or GPU.