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.

​

Workspace Setup

The first time you sign into Pentagon, you land in a guided setup flow. It walks you from “who are you” to a working teammate on your canvas in about three minutes. This page covers every step — what each one does, what’s actually saved, and how to change it later.

​

1. Intro

Headline: “Pentagon is a work studio that turns AI agents into teammates.” The opening slide is informational. Click Let’s do some work to continue.

​

2. Profile

Headline: “First: what should we call you?” Enter the name you want to be known by in Pentagon. This is your display name — it appears next to your messages in every chat (DMs with agents, group conversations, human teammate DMs).

• Just a first name is fine
• The field starts empty even if Google or GitHub gave us a name — you always make the call
• You can change it later in Settings → Profile. Updates sync to teammates in real time

​

3. Role

Headline: “What kind of work do you do?” Pick a role from the grid: Founder, Product, Engineering, Design, Marketing, Sales, Operations, Other. If you pick Other, a text field appears for free-text entry. Role is used to tailor the Tactical step later — the starter templates Pentagon offers (“Review open PRs” vs. “Sharpen positioning”) depend on what you pick here. It’s not visible to your agents and isn’t shared anywhere. You can change it later in settings, but the templates only show up during setup — re-picking won’t reopen the Tactical slide.

​

4. Company

Headline: “Join or create a studio.” This is where you choose between joining an existing Pentagon organization or starting a new one. Studio and organization mean the same thing — the container for your teammates, shared canvases, and connected apps.

​

Join an existing studio

If a teammate already on Pentagon shared an invite link with you, paste it here. The link looks like pentagon://invite/<token> or you can paste just the token. Click Join studio. You inherit your teammates’ workspace setup state — if they’re already past Connectors, you’ll skip ahead to the next unfinished step.

​

Create a new studio

Enter a studio name (your company, project, or just your name). You become the first admin and the only member until you invite teammates. You can rename the studio later, but it’s a small annoyance — pick something close to what you want. See Organizations for the post-setup details.

​

5. Connectors

Headline: “Let’s connect your apps.” Pentagon shows a grid of popular apps (Slack, Google Drive, Gmail, Notion, GitHub, Linear) plus a search box that hits the full 200+ app catalog. Click any app to OAuth into it in your browser. You don’t need to connect anything to continue. Click Continue with zero apps connected if you’d rather set them up later — connectors are added per agent in the Create Agent flow, so the only thing you lose by skipping is the convenience of having them already authorized.

• Connections are organization-wide — once you OAuth into Gmail, anyone in your studio can grant their agents Gmail access
• OAuth failures or browser-cancelled flows surface a “Couldn’t finish Gmail connection. Please try again.” message — just click the tile again
• The catalog is OAuth-only in this UI; API-key-only services aren’t listed yet

See Apps & Connectors for the complete reference.

​

6. Agent Primer

Headline: “Great job. It’s time to build your first agent.” A short explainer that frames the next few steps. An agent is described as a combination of three things — typically displayed as a 3-up card row covering instructions, model, and the apps/folder it works with. Click Let’s build to continue. Nothing to fill in here.

​

7. Workspace Folder

Headline: “Agents live in workspaces.” Pentagon explains that a workspace is just a group of folders, then asks you to set up your first one. You have two choices: The Workspace name field is pre-filled with your studio name; override it with whatever you want. The name controls the new folder’s path (if you picked “new folder”) and labels the workspace tab in Pentagon. You can change the default location for new folders in Settings → Folders if ~/Pentagon isn’t where you want them.

​

8. Tactical

Headline: “Let’s give your agent a mission.” A free-text input where you describe what your first agent should own (“Review pull requests, triage customer issues, keep the docs current…”). Below the input, three starter templates appear — they change based on the role you picked in step 3. Examples by role:

• Engineering — “Review open PRs”, “Triage stale issues”, “Write technical docs”
• Marketing — “Sharpen positioning”, “Draft content”, “Plan a campaign”
• Operations — “Create a runbook”, “Write a status digest”, “Clean up handoffs”

Click a template to populate the input with a starter prompt, then edit it or leave it as-is. Or type your own from scratch. Click Build my first agent to continue. Pentagon hands what you typed to an LLM that drafts the first agent’s instructions in the background — you’ll review the draft in step 10.

​

9. Local Runtime Check

Headline: “One local check before we create your agent.” Pentagon needs Git and at least one coding-agent CLI to spawn local agents. This slide verifies both:

• Git — required (no workaround). Install via xcode-select --install or git-scm.com.
• Claude Code — supported runtime. Install with curl -fsSL https://claude.ai/install.sh | bash, then run claude to sign in.
• Codex — supported runtime. See github.com/openai/codex. Sign in to your ChatGPT account.

You need Git and at least one signed-in CLI. Pentagon labels each row with one of: Ready (green), Missing (red), Sign in (red — installed but not authenticated), Optional (gray — not required because the other CLI is ready). The Continue button stays disabled until requirements are met. If you install a CLI mid-setup, click Check again to re-detect — no need to restart Pentagon. See Agent Runtimes for picking between them and how the model dropdown routes work.

​

10. First Agent

Headline: Full-screen Create Agent flow. Pentagon opens the same Create Agent view you’ll use forever after, pre-filled with the draft from the Tactical step:

• Name — Pentagon suggests one based on what you typed. Override it.
• Instructions — LLM-generated markdown describing the agent’s mission and how it works. Edit by hand or click the ✨ Enhance button to refine.
• Folder — the workspace folder from step 7 is selected by default.
• Model — defaults to your workspace default. Override per-agent if you want.
• Apps — the connectors you authorized in step 5 are available; tick the ones this agent should use.
• Skills — empty by default. Add later if you want.

Click Create when the brief looks good. The agent appears on your canvas with its own folder, its own model, and (if it touches a Git repo) its own branch. See Spawning Agents for the full reference.

​

After setup

You land on your canvas with your first agent ready to receive a message. The setup flow is over and you won’t see it again. Things you can change at any time: Things you can’t redo:

• The Tactical templates only show up during setup. After setup, you draft instructions yourself or use Enhance inside Create Agent.

​

What’s next