Limited beta · macOS
Draw how your agents work together.Lotus runs it.
Real agent terminals on one canvas. They hand work to each other, and they stop and ask when they need you.
The list opens shortly. The field is off rather than quietly dropping your address. Privacy.
Lotus, running


Work Lotus runs on its own: on a schedule, or when someone asks for a review in Slack.
- Weekday PR brief
- Review PRs asked for in Slack1
The accounts automations act through. Tokens stay in the macOS Keychain or with the tool that owns them, and never reach this window.
- SlackReview requests from mentions and :eyes:, results to your DM.Connected to lotus-demo
- GitHubPull requests, diffs and reviews, through the gh CLI.demo via gh
- GoogleReport rows to a Sheet and files to Drive. Only files Lotus makes or you pick.Not connected
- NotionNotion databases as ticket sources in Tasks. Changes only where you allow them.Not connected
Why does the e2e suite pass here and fail on CI?
Thought for 9s
Two things differ on CI: a cold dev server and no session cookie from a previous run.
The login test waits 2 s for /login to compile. On a cold runner it takes longer, so the first assertion times out.
Start the server before the suite and wait for “Ready”, then the test stops racing the compile.
- 01Say itType or speak who does what.
- 02AnswerAn agent that needs you asks in its own words.Tap 1 — the agent asks in its own words.
- 03Show itMark the live page; the note lands with the agent.
- BYO
- Your Claude Code and Codex subscriptions. No markup.
- 54
- MCP tools agents inside Lotus call to hand off work, drive the browser and keep notes.
- 3
- Generations deep — a chain of agent-spawned agents stops there.
- Rust
- A native Tauri app. Not a bundled browser.