Conversations that compound.
Every question becomes a thread. Every turn gets a name. You can branch, reference, edit, and re-run. Your team's analytical work stops being one-off charts in Slack — and starts becoming a library that ages well.
Every turn is citable.
T1, T2, T3 — every turn in a thread gets a stable name. Reference them in follow-ups ("compare to T2"), in other threads, in dashboards. Your reasoning stops disappearing into chat history.
- @-mention any turn. Auto-completes across all your threads. Even ones from teammates.
- Stable URLs. Every turn has its own link. Drop one in Slack, see a live preview.
- Cross-thread references. Build on last week's analysis without re-doing the work.
What-if without losing what-was.
Branch any thread to explore an alternative. The original answer stays intact. The branch carries forward the context — sources, parameters, prior reasoning — so you don't start over.
- Branch from any turn. Pick the fork point. Arcus carries the context.
- Compare branches side-by-side. Diff numbers, prose, and SQL across branches.
- Merge insights back. When a branch wins, promote it to the trunk.
Like Jupyter for analysis.
Don't like a step? Edit the question, change a parameter, swap a join. Arcus re-runs from that point forward. Old versions are kept, with diffs you can read.
- Edit any turn. Re-runs everything downstream automatically.
- Version history. Every re-run is saved. See what changed and why.
- Pin a version. Lock the answer your CFO signed off on. Re-run later, compare.
Built for how teams really work.
Review inline
Use thread context to discuss the answer, assumptions, and source trail before sharing.
Ask "why" on a number
Use a chart or table value as context for the next question when the underlying result supports it.
Drop into raw SQL
Edit the generated query, save it as a custom metric, or skip the agent entirely when you know what you want.
For the heavy stuff
Notebook-style workflows are roadmap or customer-scoped extensions, not default launch behavior.
Turn threads into tools
Promote reviewed answers into reusable surfaces when the workflow is approved.
Preview with permission
Share thread context with teammates who have access to the workspace and underlying data.
Open your first thread in 60 seconds.
Connect a warehouse, type a question, and inspect the reasoning trail before you act.