Your team. Your agents.
One place to ship.
Bring your people, coding agents and project context together.
Plan the work, run it in parallel and review what ships.
Works with the agents and tools you already use
- Claude Code
- Codex
- Cursor
- opencode
- GitHub
- Slack
01 / Hand off
Give it the goal.
Not the next prompt.
Start with a task, the relevant context and a clear outcome. Ask Alan to split the work into parallel sessions, each with the agent and environment you choose.
Pick Claude Code, Codex or Cursor for each session. The brief, the diffs and the history stay on one task.
Read Welcome.tsx · WorkspaceSetup.tsxEdit onboarding.test.tsxpnpm test -- onboardingThe checks cover the first visit and the recovery paths. A failed connection keeps the setup in place and gives the user a way to retry.
02 / Review
See the change.
Check the evidence.
Ask agents to run tests and browser checks, then review the diff, report and recordings together. Keep the merge in your normal pull request review.
3 agents · 3 flows · cloud sandboxes3/3 checks passed
- First visitRecording 0:04 · screenshotPassed
- Connection retryRecording 0:06 · screenshotPassed
- Returning userRecording 0:05 · screenshotPassed
Simplify the first-run experience #42
onboarding-polish → main · 2 files · +34 −3
- Typecheck
- Unit tests · 18 passed
- Browser checks · 3 flows
Illustrative run on a sample app · checks run when you ask
04 / Shared context
Keep the reasoning
with the work.
Give agents access to your codebase, specs and earlier decisions. With code search and memory enabled, they can find relevant work and trace it back to its source.
Code index and memory on Pro and above
GitHub, agent runs, docs, Linear and Slack feed Alan's code, product context and memory layers, and Alan brings that context to Claude Code, Codex, Cursor and OpenCode.
Use a token bucket for burst traffic.
The billing service already handles bursts with an atomic Redis script. Reuse that approach for the public API.
- The task brief and acceptance criteria
- Relevant code and earlier changes
- Past decisions, with references
Give the next agent the reasoning behind the work.
05 / Team
Fast agents.
Faster teams.
Bring a teammate into the session. Read the same conversation, steer the agents together and keep the task, decisions and results in reach of the next person.
MayaLet's get the onboarding redesign out this week. UI and edge cases can run in parallel.- Alan split this into 2 sessionsClaude Code · UI changesCodex · Edge cases
- Claude CodeUpdating the welcome screen and the setup steps.Editing Welcome.tsx
- CodexCovering an empty workspace, a returning user and a failed connection.Running onboarding.test.tsx
DevI'll review the copy as it lands.- CodexKeep the old setup route behind a flag while this rolls out?Needs a decision
MayaYes, behind a flag.- Simplify the first-run experience #42+34 −3 · checks passed · review required
- Dev approved #42 through pull request review
Illustrative session · shared sessions on Team and above
Explore Alan for Teams07 / FAQ
Before you
hand it over.
How is this different from running my agent on its own?
Which agents and models can I use?
Does it run tests on every change?
Where does my code go?
How does Alan use past team work?
What happens when a cloud sandbox is paused?
How do I start?
Set the direction.
Let the agents run.
One workspace for your people, your agents and the work ahead.
Free to start · Paid seats from $10 a month
