What changed

Cadre, the persistent-teammate platform, joins the store. It has no OAuth or API keys yet, so nothing is read from it; instead you paste a bot's webhook URL and secret, choose the events, and every document committed, branch merged or piece of feedback arrives in the bot's thread as one sentence with a link back. Secrets are stored encrypted, every delivery leaves a receipt, and a bot that stops answering is paused rather than hammered.

Operate is now read through its own MCP server: every space, list, task, member and agent run lands in the ledger and in the Tasks, Operate projects and Agent runs tables. Operate pushes each change to Company OS within seconds over a signed webhook, and a task can be created in Operate from the Work tab on its app page. Connections made before this need reconnecting once to grant the write permission.

Creating a company now opens its Stored workspace in the background, with the founder as owner, so the brain is connected and indexing before the first document is written. If Stored cannot be reached the page says so and an owner can try again or connect by hand. The company brain no longer counts as one of a plan's partner apps.

A Brain page in every company. Ask a question and the answer is drawn only from what the company has committed, streamed as it is written, with every claim cited back to the document, table row or fact it came from. When the brain has nothing on a question it says so rather than guessing. Conversations are yours and stay in the page.

Connect Stored with the write permission and every document, table row and recorded fact the company commits is written into that workspace as memory, with the people, customers, products and departments it concerns as connected entities. It stays current on every commit, and the Brain tab on the Stored app shows what is indexed, waiting and failed.

HR keeps people, time off and reviews as tables: who is away today is read off approved requests, a review that slipped shows the day after its due date, and headcount is a metric. Manufacturing keeps bills of materials and work orders; completing an order posts the components out and the finished units in to Inventory under the order's number.

A Playwright suite opens all 62 routes against a stand-in backend and runs axe over the key surfaces in both themes at both widths, so a page that throws or fails accessibility cannot merge. Every native select is gone, replaced by one Select built on the product's menu.

Every write an app makes now carries Undo on its toast, restoring the previous revision forward. A skip link is the first tab stop on every page, sideways-scrolling tables are keyboard reachable, and an axe-core pass over twelve surfaces in both themes reports nothing.

The Tables page groups every dataset under the app that writes it. The App Store opens inside the company, so installing never leaves the rail. Data became Tables and Evidence became Research, with the old addresses redirecting.

Everything waiting on a person is in one queue with chips per kind. The top bar keeps saying which branch you were on after a page drops it. Direction has a page of its own, and the rail folds the sections you are not in.

The README, deployment guide, marketplace architecture and connector guide describe paid apps, the reviewer console and the design language as they are today.

Items, locations and movements as tables, with on-hand stock derived from the movements and cover in days read off them. The second app that depends on Sales.

The app moved to a dashboard aesthetic: a dark canvas with hairline separation, a 288px rail, 36px controls, a 15px body size and one type scale, tuned page by page in light and dark.

An app can carry a monthly price. It shows on the listing and the install screen before you approve, is billed through Stripe on the same account as the plan, and is cancelled by uninstalling.

Reviewers named on the deployment read the queue oldest first, run the discovery check against the partner's origin, and record a decision the submitter sees on the page they filed from.

Invoices and payments as tables, outstanding and collected as metrics, and a link from a won deal to its invoice. The first app that depends on another.

Tickets with priority, channel and reply-by, a board of what is late, and a record page with history for every ticket.

Free, Team and Business plans with limits on members, agent keys and apps, bought through Stripe Checkout and managed in the Stripe portal. Export stays on every plan.

A full company export as JSON, an uninstall that removes the page and keeps everything it wrote, and restore of any earlier revision as a new one.

A partner lists software that syncs into the ledger through a discovery document at its own origin, and submits it for review from the developers page.

Stages, weighted forecast, stale-deal chips, an activity log, and a close dialog that records why a deal was lost.

A manifest names the tables and metrics an app creates, so two apps cannot fight over one table and a partner sync lands in the table the company already reads.

Drafts to review, finished agent work, stopped syncs and slipping direction in one list, with a daily or weekly digest by email.

One search over documents, tables, apps and people inside a company, opened from anywhere with a keyboard shortcut.

A new company gets a setup path that says what to do next, and the rail shows the departments with their document counts rather than every template.

Typed pages for every department, an agent key with capabilities, an MCP endpoint that reads and commits, and a founding interview an agent can run.

Canvas templates for the business model, value proposition and positioning, editable in the app and readable by an agent.

The first agent endpoint: a company's context served over the Model Context Protocol from the same backend the app reads.