# Connect any AgentOS to your coding agent with one command

> Service accounts give AgentOS proper machine identities in the form of agno_pat_... personal access tokens.

- Published: 2026-07-07
- Author: Agno Team
- Category: Changelog
- Canonical: https://agno-com-nine.vercel.app/articles/connect-any-agentos-to-your-coding-agent-with-one-command
- Markdown: https://agno-com-nine.vercel.app/articles/connect-any-agentos-to-your-coding-agent-with-one-command.md

Service accounts give AgentOS proper machine identities in the form of `agno_pat_...` personal access tokens. Run `uvx agno connect` and it mints a per-client token, writes the MCP config into your coding agent, and verifies the handshake, so you skip hand-editing JSON. The tokens are built for real security: stored as SHA-256 hashes, scoped per user, expiring after 90 days by default, revocable on demand, and enforced across every deployment mode, including `/mcp` and WebSockets.

See [docs](https://docs.agno.com/deploy/templates/aws/deploy#connect-your-frontends).