Docs

Quickstart

This guide walks you from a fresh Agenties install to watching your first agent team execute a real task. The whole process takes about 10 minutes.

Note:Make sure you have completed the Installation steps and that Claude Code is authenticated before continuing.

1. Create a company

Before creating a project, you need a company. The company is the workspace container for all your projects — it groups them together and is required. Click New Companyin the sidebar and give it a name (e.g. "My Startup" or your client's name).

Tip:Think of a company as a workspace or organisation. All projects belong to a company. You can have multiple companies for different clients or domains.

2. Create your first project

Inside your company, click New Project or press Ctrl+N (⌘N on macOS). In the dialog:

Project nameGive your project a memorable name, e.g. "my-saas".
Project folderPoint to an existing codebase or an empty directory. Agenties will create .agenties/ inside it.

Click Create. Agenties initialises the .agenties/ directory, creates an empty team and issue tracker, and opens the project dashboard.

3. Build your team

You have two ways to set up your team:

Option A: Hire manually

Navigate to the Team panel and click Hire member. Fill in a name, role, model, and optional instructions:

Team member config
Name:          Alex
Role:          builder
Model:         claude-sonnet-4-6     # good balance of quality and speed
Effort:        high                  # how many tokens to spend per turn
Instructions:  You are a senior TypeScript developer. Prefer functional
               patterns. Always write tests alongside implementation.

Option B: Let the orchestrator hire automatically

If Autonomous hiring is enabled in Settings, just describe what you need in the chat and the orchestrator will hire the right team members for you. The orchestrator knows the canonical org chart — Frontend Dev, Backend Dev, Tech Lead, DevOps, QA, Designer, Scout, Reviewer, Tester — and will create the appropriate roles based on your project description.

Tip:A good starting team: one builder (Sonnet), one reviewer (Haiku — fast and cheap for reviews), and one scout (Haiku — for codebase research). This keeps costs low while covering all delegation patterns.

4. Send your first message

Open the Chattab. You're now talking to the Intelligent Manager for this project. Try something concrete:

Create a simple REST API endpoint at GET /api/health that returns {"status":"ok","timestamp":"<ISO8601>"}. Use Express.js. Add a Jest test.

Press Enter (or Ctrl+Enterif you've configured multi-line mode). The orchestrator receives your message and begins its first turn.

5. Watch agents spawn

Switch to the Agents tab. Within a few seconds you should see:

Orchestratorrunning
Planning the task, reading shared state, about to spawn a builder.
Alex (builder)spawning
Claude Code process starting. Will receive the task via the mailbox.

You can click on any agent card to open its live output stream. The builder will show its full Claude Code session — tool calls, file writes, test runs, everything.

6. Review the results

When the builder finishes, it posts a task-done message to the mailbox. The orchestrator auto-wakes, reads the result, and (if you have a reviewer configured) spawns a reviewer to check the work.

The final response appears in your chat thread. The orchestrator summarises what was done, links to the created files, and marks the task complete in the issue tracker (if an issue was open).

Note:The first spawn is the slowest — Claude Code needs to load the project context. Subsequent spawns in the same project are faster because the orchestrator caches the shared state.

Next steps

Now that you've seen the basic loop, explore what makes Agenties powerful: