Build your first crew

This guide builds a four-model crew for a web app: a manager, an engineer, a tester and a researcher. It takes about fifteen minutes.

Decide what the crew is for

Write one sentence about the project. The manager will read it before every task.

A Next.js web app with a Postgres backend. Keep it fast,
keep tests green, never deploy without approval.

Add the members

1. Manager — ClaudePlans and reviews. Give it read access to every folder.
2. Engineer — DeepSeekWrites code. Give it write access to app/ and api/.
3. QA — GPTWrites and runs tests. Give it write access to tests/ and run access for the test command.
4. Research — GeminiReads docs and history. Read access only.

Check the connections

Open Crew → Structure. Lumen already drew the default lines. They should look like this:

YouYou

ClaudeManager

GeminiResearch

DeepSeekEngineer

GPTQA

Run a first mission

Start small so you can watch every handoff:

Add a "last seen" timestamp to user profiles.
Show it on the profile page. Add tests.

Expect this order in the group chat: Claude asks Gemini whether anything similar exists, plans two tasks, assigns them, DeepSeek hands a PR to GPT, GPT reports, Claude asks you to approve.

Tune it

• If Claude keeps relaying messages between two members, add a direct connection between them.
• If a member is idle most of the time, remove it or give it a recurring job.
• If results are weak in one role, try another model for that role. See Models & roles.