Hiring Agents from the Gallery

Hiring Agents from the Gallery

Step-by-step walkthrough for adding agents to a team using built-in or custom templates.

---

Prerequisites

• A team already exists. If not, see Your First Team first.
• At least one provider or ACP runtime configured. See First Launch.
• At least one agent in the gallery is marked whitelisted (see Troubleshooting#no-whitelisted-agents-in-gallery if the hire modal says otherwise).

---

The hire flow

Step 1 — Open the team

Sidebar → Teams → [your team].

Step 2 — Pick the role

Every team needs exactly one Lead (the coordinator); everyone else is a Teammate (worker) or a Queen (drift watcher, rare).

Button	What it does
Hire Lead	Only appears if the team has no Lead yet. Team must have a Lead to start messaging.
Hire Teammate	Most common — adds a worker.
Hire Queen	Advanced, rare; adds a drift-detection supervisor.

Step 3 — Choose Browse Gallery (or Custom)

Two paths from the hire modal:

• Browse Gallery → 34+ pre-built templates across 7 categories
• Custom → write your own system prompt inline (see Using Custom Assistants)

Step 4 — Pick a template

Filter by category (Technical, Sales, Marketing, PM, Data, Ops, Strategy) or search by keyword.

Each card shows:

• Name + avatar
• Category chip
• Description (one-liner)
• Default runtime — what the template is optimized for
• Skills — attached skills that'll load with the agent
• Padlock icon — if it's source='master' (fleet-pushed, read-only)

Click the card to see the full preview:

• System prompt preview
• Skill list
• Tool allowlist
• Recommended use cases

Step 5 — Pick a runtime

The default runtime (shown prominently on the template card) is a starting recommendation. You can override:

• Claude Code CLI — if you have the CLI installed and want subscription-based use
• Claude (API) — via Anthropic's API using your API key
• Gemini 2.5 Pro — fast, strong multi-step
• OpenCode / Codex / any other detected ACP runtime

See ACP Runtimes for the full list.

Step 6 — Name it

Give the agent a human-readable name (e.g., Blake for Backend, Quinn for QA). The name is what you + teammates refer to in messages. Must be unique within the team.

Step 7 — Pick avatar

Use the template's default or pick from the 64-sprite avatar sheet.

Step 8 — Review + Hire

Final confirmation:

• Role — Lead / Queen / Teammate
• Name — your entered name
• Template — e.g., "Backend Engineer"
• Runtime — Claude Code CLI
• Avatar — selected sprite
• Workspace access — inherited from team settings (shared / isolated)
• Tool allowlist — auto-applied from template

Click Hire. The new agent appears in the team with status pending, then flips to idle within a few seconds.

---

Agent Farm hiring (for fleet operators)

If your fleet has farm-role slaves available, a fourth option appears in the hire flow:

• Backend: Farm (Device B) — the agent's turns execute on Device B's machine, not yours

When you hire a farm teammate:

1. Pick the device from the farm-device picker
2. Pick the template (same gallery)
3. Pick the runtime for the slave to use
4. Set the tool allowlist (enforced slave-side)
5. TitanX fires team.farm_provision — the slave immediately materializes a mirror team + ACP session
6. From then on, every turn you delegate to this teammate is dispatched via signed agent.execute envelopes

See Agent Farm Setup for the hybrid-team walkthrough.

---

After hiring

The new agent appears as a chip in the team view. Click the chip for:

• Chat panel — read the agent's output stream
• Settings — rename, change model, edit system prompt, adjust temperature, remove
• Activity — tool calls + policy decisions specific to this agent

You can now send the team Lead a message referencing the new teammate ("Blake, can you…") and the Lead will delegate accordingly.

---

Tips

• Name teammates consistently across teams — if you always name Backend Engineers "Blake" and QA Engineers "Quinn", your Lead's delegation logic becomes predictable.
• Keep teams small — 3-5 teammates + 1 Lead is a sweet spot. More than 6 and coordination overhead eats productivity.
• Heterogeneous runtimes work — mixing Claude Code + Gemini + Codex on the same team is fine and often faster than homogeneous (different runtimes excel at different things).
• Hire roles you actually need — 34 gallery templates is generous; start with 2-3 per team.
• Rename anytime — right-click chip → Rename. Changes propagate.

---

Removing an agent

Chip → Remove from team (or Settings → Remove).

Consequences:

• Agent's conversation is archived but not deleted
• Agent's ACP runtime (if any) is SIGTERMed
• Workspace files remain (for audit)
• Tasks owned by the agent become un-owned — reassign or cancel manually

Undo: re-hire from gallery. The agent resumes a new conversation; prior context is in the archive.

---

Related pages

• Your First Team — the full first-time walkthrough
• Agent Gallery and Templates — template internals
• Agents and Teams — roles + lifecycle
• Using Custom Assistants — writing your own agent from scratch
• Agent Farm Setup — hiring remote-compute teammates