# OS Manager answers framework questions from the Agno docs

> Agno's OSManager gives the OS Manager team its own connection to the Agno documentation, so it looks up a concept question itself and hands Platform Manager only narrow, scoped tasks.

- Published: 2026-10-19
- Author: Ashpreet Bedi
- Categories: Changelog
- Canonical: https://www.agno.com/blog/os-manager-answers-framework-questions-from-the-agno-docs
- Markdown: https://www.agno.com/blog/os-manager-answers-framework-questions-from-the-agno-docs.md

Agno's `OSManager` now connects the OS Manager team itself to the Agno documentation MCP server at `https://docs.agno.com/mcp`, sharing the connection its Platform Manager member already had. OS Manager is the team you talk to through AgentOS to check activity, run diagnostics, run components and have its members build new ones.

Say you ask the manager "How does learning work?" In earlier releases the lead team had no docs tools, so it handed the question to Platform Manager, and a one-paragraph explanation could grow into a review of your deployment. Now the lead runs a focused docs query and answers. When it does delegate, its prompt keeps the task as narrow as your request and asks the specialist for a concise answer.

We built the default manager on both releases and listed the lead team's tools. No model call is needed for this:

```text
# real output, tools on the OS Manager lead team

# Before
['StudioRunnerTools']

# Now
['MCPTools(https://docs.agno.com/mcp)', 'StudioRunnerTools']
```

The release's own test drives the same question with a scripted stand-in model, and the run finishes with one `search_docs` call and no member runs. `access_docs` still defaults to `True` and now covers both agents. Pass `access_docs=False` to switch the docs off for an offline deployment.

See the [cookbook](https://github.com/agno-agi/agno/blob/main/cookbook/05_agent_os/29_manager/manager_source.py), and learn more about [AgentOS](https://docs.agno.com/agent-os/introduction) in the documentation.