Documentation Index

Fetch the complete documentation index at: https://docs.pentagon.run/llms.txt

Use this file to discover all available pages before exploring further.

​

Agent Identity

Every Pentagon agent carries a set of documents that shape how it works. These aren’t throwaway prompts — they persist across sessions, build up over time, and define the agent’s behavior. Corrections stick. Context compounds.

​

Instructions

The Instructions document is the agent’s brief — who it is, what it does, and how it works. New agents get one combined Instructions doc (drafted when you create the agent, optionally enhanced by Pentagon). This is the document you’ll edit most often. A good Instructions doc includes:

• Mission — the specific goal or ongoing responsibility
• Scope — what the agent owns; what it stays out of
• Working style — how it communicates, how thorough it is, what it prioritizes
• Collaboration — who it works with and how (e.g., “when API changes ship, message frontend-lead”)
• Success criteria — how to tell the work is done well

Example:

I’m a senior backend engineer. I write Go, design APIs, and think in terms of data flow and failure modes. I own everything in api/ and middleware/ — I don’t touch the frontend. When I make breaking API changes, I message frontend-lead so they can update their calls. I’d rather ship a correct but minimal implementation than a feature-rich but fragile one.

Edit the Instructions in the agent’s Settings tab → Instructions section.

​

Soul & Purpose (legacy)

Older agents (created before the unified Instructions doc) carry separate Soul (personality and expertise) and Purpose (mission and scope) documents. Both are still readable from the agent’s Settings tab. New agents skip this split — everything is in Instructions. If you have older agents, their Soul and Purpose continue to work as before. There’s no migration to do.

​

Memory

Memory is accumulated context the agent builds up over time. Unlike Instructions (which you write), Memory is maintained automatically — distilled after each conversation turn from the agent’s growing Knowledge Base. Pentagon agents use Pentagon’s own memory system exclusively — the underlying CLI’s built-in auto-memory is disabled. All persistent context is in one place, visible to you in the Settings tab. Conversations, decisions, what worked and what didn’t — your agents build up tribal knowledge over time. An agent that fixed a tricky deployment last week already knows the gotchas when it comes up again. Memory helps agents:

• Retain context across sessions
• Remember decisions and why they were made
• Avoid repeating mistakes
• Build compounding institutional knowledge

You can view Memory in Settings tab → Memory. For the detailed articles memory is distilled from, browse the Knowledge Base in Artifacts mode.

​

CLI settings passthrough

Pentagon passes a safe subset of your personal coding-agent CLI settings (e.g. ~/.claude/settings.json for Claude Code) through to each agent. Agents inherit:

• Model overrides — custom model routing (Bedrock, Vertex, etc.)
• Environment variables — custom env vars for the CLI process
• AWS configuration — Bedrock auth, credential export settings
• API key helpers — custom authentication scripts
• Preferences — language, effort level, output style

Security-sensitive settings (hooks, permissions, sandbox config) are stripped automatically and never reach agents. If you use Claude Code with Amazon Bedrock or Google Vertex, your agents pick up the same provider configuration with no extra setup.

​

Why identity matters

Agents without identity documents work fine for one-off tasks. But for ongoing work — where agents collaborate, make decisions, and maintain codebases — identity is what makes them reliable. A well-defined agent:

• Makes consistent decisions aligned with its role
• Communicates clearly with other agents about scope boundaries
• Knows when to ask for help vs. when to proceed independently
• Builds on past work instead of starting from scratch each time