New features, improvements, and fixes from the Crew One team.
Your crews can now read the company wiki and cite what they read, and your connections tell you when they break instead of failing quietly inside a workflow.
The Chief of Staff now reads the pages your company writes down — handbook, metrics, decision log — and answers from them directly. Every answer names the page it came from, so you can check the source rather than trusting a paraphrase. Ask "what did we decide about vendor spend?" and you get the decision and where it was recorded.
A broken connection used to surface as a workflow that quietly returned nothing. Connector health now tracks each connection and alerts you when one needs attention, so a lapsed token is something you fix in a minute rather than something you discover a week later in a briefing that was missing half its input.
Each connection resolves through a per-user rail. If your token cannot be resolved the call fails rather than falling back to a shared credential, so one person’s access is never quietly borrowed to do another person’s work.
If you keep objectives in Notion, they now sync into durable Goals that crews can read and track against. You keep writing them where you already write them, and the rest of the system stops being blind to what you are actually aiming at.
When a commitment is met, Crew One detects the resolution and closes it rather than waiting to be told. Anything that no longer matters, you can dismiss outright, so the open list stays a real list of what is outstanding.
The weekly company Review became a real surface built on live data, Goals became objects that persist, and every run now has a cost and a stop button.
Once a week, Crew One assembles what moved, what stalled and what needs your judgement, then publishes and delivers it. It is built from live runtime data rather than a summary of a summary, so the Review reflects what actually happened rather than what was reported.
Goals are now durable objects with their own read path and surfaces, instead of context that evaporates between sessions. An At-risk view derives from each goal’s review date, so the ones drifting out of attention surface on their own rather than waiting for you to remember them.
Every run writes to a durable cost ledger, and you can set spend limits per run and per company. You can see what the work costs before the invoice tells you, and a runaway job hits a ceiling instead of a bill.
You can pause or cancel a running execution. Anything it was holding for your approval is revoked at the same time, so cancelling means cancelled — not a stopped run with an approved action still queued to fire behind it.
Evidence cites the connector it came from. When a source cannot answer, it says so plainly rather than returning a confident gap, so you can tell the difference between "nothing happened" and "we could not look".
Crews began doing work on a cadence rather than only when asked, and started working from the tools your company already runs on.
A proactive worker now runs in production, scheduling crew work and delivering the result to Slack. Your briefing arrives because it is due, not because you remembered to ask for it — which is the difference between a tool you operate and one that operates alongside you.
Each integration is authorised from your own account over OAuth, and configured per user rather than per workspace. Crews read the context they need from the systems you already work in, so you stop re-explaining your company to a blank chat box.
The morning briefing reads your actual calendar, your actual inbox and your real Linear tasks. It tells you what changed overnight, what needs your judgement and what can wait, drawn from the same sources you would have checked yourself.
A consolidation pass runs monthly and quarterly, folding what happened into durable context rather than letting it pile up as raw history. Context compounds instead of accumulating, so the system gets more useful over time rather than slower.
Company context became a queryable store that answers with citations — scoped to your company, not pooled across everyone.
Ask the brain a question and the answer names where it came from, wired end to end through the provider adapters. A citation is what separates an answer you can act on from one you have to go and verify first.
Company isolation is enforced at the brain endpoint, so one company’s context is never served to another. This is the foundation the rest of the product is built on — memory is only useful if it is also contained.
Company knowledge and customer records live in tables with role grants and row-level security. Crews read what they are entitled to read, and the boundary is enforced by the database rather than by convention.
Crew One now follows you across Slack, WhatsApp, and the web with unified identity and persistent memory.
Introducing PaL - the brain that routes your requests by complexity, learns from every interaction, and gets faster over time.
A three-tier memory architecture that ensures Crew One always remembers what matters - your preferences, your history, and your commitments.
Meet your crew - seven specialised AI agents handling calendar, email, research, tasks, Slack, Notion, and file operations.
Access Crew One from your browser with a full-featured dashboard and a Chrome extension that brings your AI crew to any webpage.