What shipped.

• Connect a shared mailbox, such as info@ or accounts@, to Gmail as an organisation admin. Members see its mail only when their Data Role allows it, and the Inbox names the mailbox each email came to.
• Pin the links a channel uses every day, such as a checklist sheet, a report, a folder or a Twin session, to its Overview. Paste or drop a link to pin it, or pin a file from the Files tab.
• Type @ to mention a customer, supplier or person in a session, post or comment. It shows as a chip with its card, and in a session the Twin starts from that exact entity.
• Ask about a customer by the name people use, such as "Northwind" for Northwind Ltd. Ask about one that doesn't exist, and the Twin says so straight away instead of searching for minutes.
• When a run fails, it says what went wrong in plain words instead of a one-word error, and each turn shows its progress in one tidy step list.
• Plugin settings, starting with Gmail, show one connection row, one Check button and a switch for sync. Menus and pickers now read clearly in dark themes.

Running in our own workspace first: guest access, which we described as in progress on 4 October, now lets channel owners invite View and Edit guests by email into external channels, and channels can be arranged into groups in the sidebar and on the Channels page. Both reach customer workspaces later.

Update through 5 October. Mentions need entity pages, which are in preview. The Twin also wastes fewer steps loading its tools, a queued follow-up no longer gets stuck behind the turn ahead, and a tab left open across a release picks up the new version on its own.

• Follow one checklist to ask a first question, connect a service, invite your team and create a channel.
• Open a channel on its overview of purpose, members, data sets and recent activity.
• Hover a link, person, channel or view wherever it's named for a card about it, with live Linear and Notion previews through your own connection.
• Read the Inbox at a glance, and from a notification ask the Twin to run something again or what to do next.
• Build richer pivot tables: several measures per row, measures calculated from others, subtotals, record counts, sorting and limits.
• Filter dashboards like a spreadsheet, pick several values at once, and see the period each widget covers.

Released to production workspaces this week. An interrupted run now says so and offers Retry. Also this week: entities, workflow authoring, session controls, scheduled workflows, answer traces; in testing, Twin Build and harness v3.

• Find them in Entities, under Knowledge, by type or by searching for a name.
• Open a page to see their names in each system, what they're connected to, and their records counted by year, such as Xero invoices in 2025.
• Hover a name in an answer or on another page for a quick card, and choose Ask to start a session about them.

The Twin shows how well each connection holds and sets aside the ones that don't. Entities are in preview and on in selected workspaces from 4 October.

• Ask the Twin for a workflow that handles each uploaded document or changed record. It drafts and checks the workflow; you review it and switch it on.
• Approve or reject a workflow's review on the record itself, beside the evidence it used. Correct a field instead, and the workflow checks again.
• See how a run is going in one notification that updates as each step finishes.

Reports that a scheduled workflow posts to a channel now keep their headings and paragraphs, as on the Results tab. You can also ask the Twin to find invoices and receipts in your own Gmail and bring the ones you choose into a channel, where an upload workflow starts on each one. Released to production workspaces on 3 and 4 October.

• Send a follow-up while the Twin is still working, and it runs next. Roll a session back to any earlier turn to try again from there.
• When the Twin needs a detail from you, it asks in a short form. Its steps show as a list that folds away once the answer starts.
• Choose the neutral Charcoal theme or the refreshed light themes. Lists, settings and menus follow one plain layout, and the Inbox shows only what needs you.

The Evidence tab names each source in plain words and shows each cited value once. Dashboards gain waterfall charts for bridges such as MRR or cash, target lines on charts, and colour scales on pivot tables. Released to production workspaces on 3 and 4 October.

• Twin Build now knows what the codes in a source mean, as the provider documents them, starting with Xero. A product can hold only sales invoices or only supplier bills, and says exactly which.
• Products keep the IDs that connect their records, so the Twin counts customers and suppliers by ID, not by how their names are spelled.
• In testing, questions about a specific customer or supplier took 20 to 39% fewer steps when the Twin read that entity's page first, with the same or better accuracy. Results on other questions were about the same.

Live now: when a question needs more than 20 groups, such as revenue for every customer, the Twin is told the list was cut short and asks again, rather than treating the first 20 as the whole answer.

• Invite someone by email into a channel you've marked as external.
• Make them a View guest, who can read, ask the Twin and comment, or an Edit guest, who can also add and change records and upload files.
• A guest sees only the channels they're invited to. In those channels the Twin answers only from that channel, for guests and members alike.

You'll also be able to arrange your channel list into groups, such as one per client. Guest access will stay off until an organisation admin turns it on.

• Open any step of an answer's trace in an inspector beside the canvas, with each step's outcome shown and the answer's path highlighted.
• Switch between Graph and Steps, or ask for an explanation, from the trace toolbar. A plugin's tool calls fold into one card.
• Scroll every canvas with the mouse wheel, and zoom with a pinch or Ctrl+scroll.

Dashboards also gain a "YTD previous month" preset, and date filters no longer overwrite a shared link's filters. Released to all production workspaces on 30 September.

• Ask the Twin for a recurring report, and it builds, tests and schedules the workflow for you.
• A scheduled workflow runs as its owner and posts each result to a channel as a dated document.
• See every scheduled run and test in Runs, and pause or resume a live workflow from its Operations panel.

Workflows remain in preview and private to their owner. Released to production workspaces on 30 September.

Organisation administrators can try it in our test environment, from a new Session's developer controls or from the Twin CLI. All results below come from a synthetic test ledger.

• On questions it hadn't seen before, it offered all the data a question needed 82% of the time, up from 58%. On a fresh set written before any results were in, it reached 78%, up from 46%.
• Wrong shortcuts, where one matching phrase tied a question to a single Data Set, fell from 30 to 1 across 13 test builds.
• Where v3 newly offered the right data, answers took about 40% fewer steps and 30% fewer tokens. Accuracy across the run stayed at 91%.

We can now check a change to how the harness picks data in about ten seconds, without running the whole product.

• Connect steps on a canvas to build a workflow, with every save kept as a version.
• Watch a run move across the canvas, then inspect each step's inputs, outputs and errors. A failed run names the step that failed.
• Start from step templates, and see each workflow's health in the list.
• Build workflows that read each document, look up matching records, flag likely duplicates and cite the exact lines behind each finding.
• Narrow a whole dashboard by date, with one-click ranges such as month to date.
• Type @ to attach a file that's already in the workspace, and open a record linked in an answer beside the conversation.

Microsoft 365 Copilot and Teams chats keep long answers alive with progress updates, and SharePoint document reading can be switched on per connection.

Workflows remain private to their owner, and date filters are not yet in the Mac app.

• Open an answer's evidence as a sheet beside the conversation, with the cited cells highlighted.
• Create, drag and resize calendar entries in place, undo from the notification, see the next four weeks in the agenda, and colour events by any field.
• Filter people fields by "Me", and narrow the sidebar to your own Sessions.
• Describe a workflow and the Twin drafts it; test it on a read-only sample, browse its versions and restore an earlier one.
• Answers appear block by block as they stream, with quieter updates while the Twin is thinking.
• A new product tour walks through asking, the Inbox and Channels.

Teams replies keep their formatting, such as tables and lists, and HubSpot changes recover safely if a response from HubSpot is lost.

Workflows are an early preview: drafts and samples only, with no scheduled runs or actions.

Project Venus can now highlight how confident the model was in each word, shows how much of its context window a conversation has used, and now serves from one path that prefers the best available hardware. Access remains limited to approved administrators.

• Open a finished answer as a separate report you can check.
• Follow any cited figure back to the source rows and fields it came from.
• See how each calculation was worked out, which documents were used, and where the source data stops.
• Point the Twin at workspace content and it can find and read it, within your existing access.

SunSystems handles very large journals and answers account balance enquiries directly, and recovers analysis codes more reliably. Granola updates arrive as they happen, booking data recovers from interruptions more gracefully, and GitHub shows comment counts.

This checks the cited figures and the arithmetic, not whether the source data itself is right. Also this week: a Twin hub, richer links and channel files.

Project Venus added a faster, measured serving option to its private production pool, with clearer status while it starts up. Advanced models remain limited to approved administrators.

• Open the Twin hub from the top bar for setup, Marketplace, members, access, style and billing.
• Set your organisation's writing style once, and the Twin writes in it.
• Paste a link to see its title and key details; private files preview through your own connection.
• Browse a channel's files and Twin-made documents in one pane, and see who gains access before you share.
• Get told when one of your connections needs attention, and see each connection's health in Plugins.

From a channel's Add menu, the Twin can also set up a data set, document, sheet or view for you. Released to all production workspaces on 13 September.

• Preview documents, spreadsheets and linked Google Workspace files without leaving the workspace.
• See where each source came from, how current it is, and which Data Sets it feeds.
• Start a question with the exact file or Data Set already attached.
• Browse synced Gmail by mailbox and label.
• Review the Twin's suggested links, definitions and actions in one place in the Inbox.
• Answers now refuse a total built from incomplete rows, and say when a period isn't finished yet.
• A short first-visit tour shows how to ask, follow, decide, organise and inspect, and unsaved record edits are protected.

Google Sheets can be chosen as a source, several tabs at a time. Google Drive, SharePoint, GitHub, Slack and Linear connections improved; Xero covers more of your accounting, and GoCardless data can be queried.

Knowledge shows only what you're already allowed to see, under your organisation's roles and each source's permissions. Reviewing a source there doesn't certify its contents.

Project Venus tested a Deep Space mode, in which the main model can consult several specialist helpers in parallel before answering. It remained an internal test.

• Install the Twin in Slack, then message it directly or mention it in a thread. It answers in the same thread, and each thread keeps one lasting Session.
• Invite the Twin into an existing Slack discussion and it can use the conversation so far, without you pasting it in.
• Use one Twin app across Teams chats, approved Teams channels and Microsoft 365 Copilot, with progress updates on long answers.
• See mentions, replies, approvals, failed tasks and watched changes in one Inbox, with who did what, where, and why it needs you.
• Choose which updates you get and where they go, and which records or discussions to keep watching.
• See whether a piece of work started in Slack, Teams or Copilot, and who started it.

Xero gained a fuller connection to your accounting data, including invoice lines and journals. Each integration needs a configured connection. The Teams app isn't in the Microsoft marketplace, and email notifications aren't included yet.

Project Venus reached a private interactive preview for approved internal administrators, with separate capacity for everyday use and for research. Long, tool-heavy conversations also became less likely to fail late.

• Click a chart category to filter the whole dashboard; every widget follows.
• Turn series on and off from a chart's legend.
• Drag widgets by their headers to rearrange the layout.
• Open the records behind a metric, and compare it with the previous period and the last 12 months.
• Start a Session from a channel or saved View: the Twin begins with that context, and the same records stay open beside the conversation.
• Browse a channel's files as a list or as icons, and give select options their own colours.

Outlook mail gained a native connection, the Twin can read Granola meeting notes directly, and work began on delivering your notifications to you in Microsoft Teams.

Also this week: answers stream with their working.

Every answer already showed its sources. Now you can watch it happen: the answer appears as it's written, and the sources panel beneath it fills in as each source is read. The finished trace stays with the answer afterwards, so you can check it later.

• Every memory keeps its versions and where it came from.
• Each run records which memories it was given.
• Correct, retract or forget a memory, and the Twin stops using it.
• A policy on each run decides whether memory is used at all.
• Elsewhere in the app, new colour themes arrived, including high-contrast violet and teal, and the Mac app caught up with the web on channels, Views, discussions and the Feed.

Memory was in internal development and not yet released to customers.

Project Venus added on-demand trials with two GPU providers, so serving options could be compared on cost and speed without opening them to general use.

• Use one Data Set six ways, as a table, board, calendar, timeline, dashboard or pivot, with the same filters working in every one and no copying of data.
• Discuss a record, Session, file or report in a thread beside it, mentioning people, channels, Data Sets and Views.
• Follow workspace and connected GitHub activity in the Feed.
• Bring the same Twin into supported assistants and developer tools, with the same permissions and history.

The Twin reads HubSpot pipelines, companies and contacts and, when explicitly allowed, creates or updates selected records, checking each change with HubSpot straight away; it can't delete anything. Xero connects as soon as you sign in and stays within Xero's daily limits, and a packaged Claude connector reaches the same Twin. HubSpot changes and the assistant connections started in limited preview.

Project Venus moved into short, bounded trials and practised answering from approved company data. It stayed an internal test.

• See at a glance whether a Data Set is current, refreshing, getting older, stale or failed.
• Tell an intentional snapshot apart from a live source, and see when the data was last updated and when it refreshes next.
• Follow what changed across your workspace in a personal Feed that remembers what you've read.
• Schedule a recurring question or report for chosen weekdays, run it on demand, and look back through its history.
• Keep the reports and exports the Twin makes as versioned documents you can review, revise and export as PDF.

Choose GitHub repositories to bring their commits and pull requests into the Twin, with up to two years of history. Answers from connected finance and operations data, such as Xero and SunSystems, now cite the tables they used, and Xero gained an account-level balance sheet.

Freshness follows each source's schedule; a scheduled sync is not a live feed. GitHub, scheduled questions and versioned reports started in limited preview.

Project Venus, our work to run open models under our own control, began this week. Its first test route was held back at a readiness check rather than serving customer work.

• Connect through sign-in, the REST API, MCP or the Twin command-line tool.
• Ask questions and work with channels, Views and records from those tools.
• Your organisation's permissions and your own travel with every request.
• Channel conversations are kept in one place, whichever tool they came from.
• Switch between your organisations without signing in again.
• Session titles are clearer and easier to scan.

Your organisation enables each tool first. Progress updates show what the Twin is doing without exposing private prompts or its reasoning.

• Choose exactly which schemas and tables a connection exposes to the Twin.
• Every query runs read-only, with limits on time, rows and size.
• Each query's scope and destination are checked before it runs.
• Connections can use encrypted links and client certificates, with credentials held centrally rather than in the workspace.
• Dashboards gain compact reference tables, and a Session shows which reasoning mode it used.

A connection must be set up and approved by your organisation. The Twin can't write to the database.

• Save a View's layout, filters and settings, and return to it any time.
• Switch between tables, boards, calendars and timelines over the same records.
• Ask the Twin to export a query's results as CSV.
• Page back through a long Inbox history on the web, iPhone and Mac.
• Dashboards, boards, calendars and large tables load faster.

Granola meeting notes can now be brought in and keep their place between syncs, and Slack conversations carry more of their context to the Twin.

• Make a channel private, so only its named members can see or change its content, including through the Twin.
• Shared channels stay visible to the whole organisation, as before.
• Every run records the data it queried, so you can see where an answer came from.
• Upload a spreadsheet and the Twin can read it.
• Revenue trend views load faster.
• The pre-release iPhone app gained an approvals queue, with notifications that open the right Session.

Privacy is set per channel, not per row or field. Seeing an answer's sources makes it easier to check, but doesn't by itself make it right.

• Add supported documents to a Session; the Twin extracts their contents and works from them.
• An uploaded file is context for that work. It doesn't become approved company knowledge on its own.
• Export a channel's records as CSV.
• Resize and rearrange dashboard widgets, including from the keyboard.
• An early iPhone app connected to Sessions and workspace updates, for reviews and approvals away from a desk.

The Inbox gained Xero invoices as they fall due and a daily digest of new bookings, and Microsoft Teams messages arrive through a more robust entry point. Which files can be read depends on how extraction is set up, and the iPhone app was pre-release.

• Mention the Twin in a linked Teams conversation to start work.
• The result arrives back in that thread, and the full Session stays in your Twin workspace.
• Each Teams user is linked to their own Twin identity, so the Twin works with their access and no one else's.
• Connect your Microsoft account separately to let the Twin read the Teams and Microsoft 365 content you can see.

Slack mentions and direct messages also began arriving in the Inbox, and channels gained dashboards. Teams needs a configured integration and isn't in the Teams Store.

• Pick up a Session on the web or on your Mac.
• See workspace changes arrive in the web app without reloading.
• Edit a record in place. If someone else changed it after you opened it, you're told, instead of overwriting their work.
• Set a Session to run again every day.
• Turn a connected tool on or off for your workspace, and see each channel's record counts at a glance.
• Follow-ups and Stop work the same way on every app.

The Mac app was in development. It keeps a local copy for speed, while the server stays the source of truth.

• Organise records, Views and files in Channels your team shares.
• See items from connected services arrive in the Inbox.
• Keep each conversation with the Twin, and its history, in Sessions.
• Ask the Twin to work with a channel's records; it does so with the same permissions as everything else.

The web and native apps didn't all have every part at first.

• Review a proposed change beside the evidence behind it.
• Follow each proposal's status in a lasting record.
• See progress, failures and retries while an approved change is applied.
• Keep the reports and files a run produces, and reach them through the API and SDK.

This first version was later replaced, but its principle stayed: the Twin suggests, and people review before anything is published.

• Follow sign-in and setup steps written for each provider.
• See up front when a step needs an administrator.
• Check that a connection actually works, not just that its settings are saved.
• Each run is tied to the exact version of the Twin's instructions it used, so changes to them can be reviewed and compared.

Xero data became available to the Twin's questions, and Notion gained its first connection. What you can connect depends on your organisation and the account you sign in with.

• An interrupted import resumes from its last checkpoint instead of starting over.
• Temporary errors from a provider are retried automatically, waiting a little longer each time.
• Each connection reports when it last synced successfully and whether it's healthy.
• Every change read from a source is kept, so what the Twin knew and when can be checked later.
• Answers can show document previews and charts, with the logos of the connected tools each answer used.

Xero, Stripe, GoCardless and SharePoint gained their first native connections, covering accounting, payments and documents, and the first Google Workspace and Slack connections arrived. Each needs an approved account and working provider setup.

• Come back to an answer later: responses are saved as messages, not lost when the page closes.
• Stop the Twin while it's working.
• Ask a follow-up, and the Twin carries the earlier turns forward.
• Connected services keep their credentials out of the Twin's prompts, so a connection can be reused safely.
• Watch the Twin's tool activity as it happens.

Work also began on Google Workspace and Slack connections, which reached the product the following week.

• Each task carries the scope of data your organisation allows it into every query it makes.
• A query that can't be shown to stay inside that scope is refused before it runs, not after.
• If a task has no scope at all, its queries don't run.

This check comes from the data layer itself, not from instructions to the model, and the shared data layer still enforces it today.

• Write, version and publish Skills, reusable instructions for the Twin, from the workspace instead of setup scripts.
• See which Skills and context each run used.
• Follow progress, answers and tool activity in one consistent format across the app.
• Connect scripts and tools with an API key issued by an administrator, and build on the Twin with a first API description and TypeScript SDK.

Skills shape how the Twin works. They never give it access to more data.

• Start a piece of work with one prompt; the task and its first run begin together.
• Follow the work in a chat-style view, with the Twin's tool activity condensed into short progress messages instead of raw logs.
• Copy any answer as Markdown, ready to paste into a document or email.
• Every run records the instructions and context it was given, so an unexpected answer can be traced back to how it was set up.

An early development milestone. It laid the foundation for Sessions, which carry this idea today.