--- title: "What are agents in Tale?" description: "Tale agents combine instructions, knowledge, tools, and a model. Connect Claude Code, Codex, Hermes, and OpenClaw under one orchestrator you host." --- Agents # What are agents in Tale? A Tale agent is the four-knob combination of instructions, knowledge, tools, and a model. Editors build them once; the team runs them in chat, automations, and projects — including external agents like Claude Code, Codex, Hermes, and OpenClaw. > Animated demo: the Agents list for this page — Support Agent, Docs Agent, Release Agent, Research Agent, and Pilot Agent, each with its model. ## How agents show up in Tale Dock the agents you trust, ground them in knowledge, run them in workflows, and scope them by project. 01 Projects ### Scope agents by team Each project keeps its agents, members, and knowledge in one workspace — support never sees engineering’s stack. > Animated demo: Projects scoped so Support and Platform each keep their own agent stack and members. 02 Knowledge ### Ground every agent in what you know The Support Agent gets macros, brand voice, and the help-center crawl — and nothing else. Each agent searches only the slices you grant. > Animated demo: the knowledge slices granted to one agent — support macros, a brand-voice entry, the agent playbook crawl, and the returns playbook. 03 Automations ### Run agents in multi-step work Workflows call agents as LLM steps with conditions and actions — every run leaves an execution log. > Animated demo: a nightly workflow calls the Release Agent as its LLM step, checks whether anything shipped, and posts a digest to Slack; the Executions table records each run. 04 Sandbox ### Watch the agent in Files and Live External agents work in a sandbox — browse the workspace tree, open the file they just wrote, and watch the live browser as they click through the result. > Animated demo: Hermes edits install_offline.py in the Files pane, then the Live browser shows the air-gapped install checklist. ## What can agents do? What one agent definition gives the whole team — and what it adds beyond a bare model. - 01Four knobs, one unitInstructions, knowledge, tools, and model define how an agent behaves. Change one knob without re-training anything.[Agent concepts](https://tale.dev/docs/platform/agents/concepts) - 02External agents dock inConnect Claude Code, Codex, Hermes, and OpenClaw so work routes to the agent that already lives in your stack.[External agents](https://tale.dev/docs/platform/agents/external-agent) - 03Delegation between agentsSpecialist agents hand work to each other when a thread leaves one domain — without losing the transcript. - 04Skills as reusable bundlesPackage a writing voice or multi-step pattern once and bind it to up to ten agents. - 05Knowledge scoped per agentEach agent searches only the library slices you grant — team docs stay invisible outside the team.[Agent knowledge](https://tale.dev/docs/platform/agents/knowledge) ## Agents FAQ ### What is an agent in Tale? ### Can Tale orchestrate Claude Code and Hermes? ### When should I use an agent instead of a workflow? ### Can each agent use a different model? ## Related modules - [ChatsEveryday AI with citations, tools, and Arena.](https://tale.dev/platform/chat) - [KnowledgeDocuments, websites, and records agents cite.](https://tale.dev/platform/knowledge) - [AutomationsTyped workflows with triggers and approvals.](https://tale.dev/platform/automations) - [GovernanceApprovals, audit trail, and spend controls.](https://tale.dev/platform/governance) ## Read the docs - [Agent concepts](https://tale.dev/docs/platform/agents/concepts) - [Create an agent](https://tale.dev/docs/platform/agents/create) - [External agents](https://tale.dev/docs/platform/agents/external-agent) - [Delegation](https://tale.dev/docs/platform/agents/delegation) - [Agent knowledge](https://tale.dev/docs/platform/agents/knowledge) ## See Tale on your stack Book a guided demo or talk to the team about self-hosted deployment, pricing, and hardware.