Co-author
Teammates join live. They prompt agents, steer the plan and edit the diff alongside you.
Alan for Teams
better. faster. TOGETHER.
Share agent sessions with your teammates, keep every change attributed, search what the whole team has already learned, and catch duplicate work before it ships twice.
Found in team memory: Payments team solved Redis atomicity in “Billing retry limits”, 3 weeks ago.
Works across every agent your team already uses: Claude Code · Codex · Cursor · opencode · GitHub · Slack · Linear
02 / Attribution
Shared sessions are co-authored automatically. Each hunk carries the teammate who asked for it and the agent that wrote it, all the way into the commit and the pull request.
+ export function rateLimit(opts: Limits) {
+ const bucket = createBucket(opts.perKey);
+ return (req, res, next) => bucket.take(req.key) ? next() : res.status(429).end();
+ }+ const take = redis.defineCommand(TOKEN_BUCKET_LUA);
+ // atomic: reuse billing service scriptfeat(api): per-key rate limiting
Co-authored-by: Maya S <maya@acme.dev>
Co-authored-by: Dev K <dev@acme.dev>
Agent-Session: alan://s/rate-limit-api
03 / Team memory
Search across every team’s sessions for previous work, artifacts, context and learnings. Reuse a teammate’s session, artifact or fix in your own work instead of rebuilding it.
04 / Duplicate work
When parallel agents make work cheap, overlap gets expensive. Alan compares work in progress across sessions and flags when two efforts are heading to the same place, so you can join forces instead of racing.
Same files, same goal, started a day apart
rateLimit.ts · gateway.tsthrottle.ts · gateway.tsBoth sessions are building a per-key limiter in the gateway. One shared implementation would cover both.