Build a development crew

#Goal

A #backend channel where a Developer agent changes code only with your approval, and a Reviewer agent that can read the project but never change it. You will approve a write and see a hand-off.

#Prerequisites

• LoCrew installed and running (Installation).
• Claude Code installed and signed in. (Codex works too, but LoCrew's approval dialog is only shown for Claude Code.)
• A small test project folder you do not mind an agent editing.

#1. Create the Developer

1. Agents → Create agent.
2. Name & avatar: Developer, description Implements changes in the backend.
3. Provider & model: Claude Code. Wait for Claude Code found.
4. Instructions: Implement what you are asked in this project. Explain what you changed and why. When you finish a change, call send_message to ask Reviewer to review it. Set Working directory to your test project and Workspace access to Ask first.
5. Tools: leave the defaults and press Continue. On Review, press Create agent.

Expected: Developer's DM opens, and it shows Ready in the Agents view.

#2. Create the Reviewer

Repeat with Reviewer, description Reviews changes and reports problems., instructions Review the work you are given. List concrete problems first, most serious first. Do not change files., the same working directory, and Read only.

Behind the scenes: a Read only Claude Code agent is denied Write, Edit and shell tools by LoCrew's permission check, whatever its instructions say.

#3. Create the channel

1. + next to Channels.
2. Name: backend. Topic: Backend work for the test project.
3. Leave both agents selected. Optionally set Project directory to the same folder, so every agent in the channel works there.
4. Create channel.

#4. Ask for a change

Send:

@Developer add input validation to the main entry function, with a short test.

Expected: only Developer's reactions appear on your message. When it tries to write, an approval dialog opens: Developer wants to edit …, with a diff.

#5. Approve the write

Read the diff. Choose Allow once for this change, or Deny to refuse it. Closing the dialog also denies.

Behind the scenes: Developer's run waits as Waiting for you with ❓ on your message. Only one agent writes in a folder at a time, so another writing agent would wait for the folder's lock.

#6. Watch the hand-off

When Developer finishes, it should call send_message to wake Reviewer, as its instructions ask.

Expected: Reviewer's reply appears in the channel. In Activity, Reviewer's run is marked by an agent. Your message started one chain: Developer and Reviewer used two of its six hops.

#Common mistakes

• Mentioning nobody. In a channel, a message without @ wakes nobody.
• Expecting "@Reviewer" in Developer's reply to work. Only a send_message call hands off work. Make the instruction explicit.
• Giving the Reviewer Full access. A reviewer should be Read only.
• Using your main repository. Access levels are limits, not a sandbox.

#Troubleshooting

• Stopped here: … Send a new message to continue. A limit stopped the chain; see Limits.
• Developer stuck in Queued: another run is writing in the same folder, or Max agents working at once is reached.
• "Developer" has read-only access…: you set Developer to Read only by mistake.

#Next steps

• Use Claude Code and Codex together
• Run a flow from chat: make the review a repeatable flow.