Orgonaut

We publish substantial product improvements, workflow changes, and major fixes here. Small internal refactors, maintenance-only work, and invisible cleanup are intentionally omitted.

October 9, 2026

Connect AI assistants on every plan

Remote MCP access is now included on every plan, including Team and the free trial. Connect ChatGPT, Claude and other MCP clients through OAuth, or create a token in Settings → API and MCP.
An organisation saved from a ChatGPT draft can connect back to ChatGPT straight away.
Member roles and token scopes still decide what a connected assistant can see and do.

Smoother organisation modelling in ChatGPT before signup

Assistants can read the OrgSpec format and a worked example before building your first draft.
When a draft has a problem, the assistant now sees each field to fix, so it can correct it without starting over.
Edits return only what changed, which keeps long modelling conversations fast.
Busy periods no longer block new users who share an assistant's network; limits now apply per assistant user.

October 2, 2026

Safer scenario deletion

Deleting a planning scenario removes its organisation records and allocations without moving them into Live.
Snapshots, applied scenarios, archived scenarios, and locked scenarios remain protected from deletion through the planning scenario route.

One Orgonaut connection for every eligible organisation

The shared MCP endpoint works for all organisations with MCP access. Sign in, choose an organisation and approve the connection; switching organisations in the web app does not change its scope.
Connected agents can browse actors, teams, classifications, Business Capabilities, AI Solutions and Transformation Cases, alongside existing staffing reports and scenario planning tools.
Existing permissions still protect costs, pay and workforce data. Scenario changes continue to require a preview and explicit confirmation.

September 30, 2026

Remove sample data while keeping your work

Account owners can remove demo data from Settings → System after adding their own organisation data.
Your own records and placements are kept. Shared teams and departments stay in place, and existing scenarios and snapshots are preserved.
Sidebar shortcut hints now sit beside menu labels, the CSV import and HRIS setup buttons align on onboarding, and scenario header buttons stay on one line.
Archive a planning scenario directly from its yellow banner, beside Manage Scenario, with the same confirmation as the Scenarios list.

September 29, 2026

Plan changes

Capabilities, AI Solutions, and Transformation Cases (including their reports) are now available on the Enterprise and Agency plans only. The Work catalog stays available on every plan.

Data processing agreement

Organisations on the Business, Enterprise and Agency plans can download a GDPR data processing agreement, filled in for their organisation, from Settings → Data Processing Agreement.
The archive kept after an organisation is permanently deleted is now removed automatically after 30 days. The Security and Data page explains this, along with our certification status.

September 28, 2026

Fixes

Signing up with Google, GitHub, Microsoft or SAML no longer ends in a "too many redirects" error.
Astro counts headcount by department, team, title or role level from everyone who is placed, including people without a position, and you can name a scenario from any page, for example "What does Path to 2030 look like on 1 June each year?". When Astro can't retrieve something, it now says so rather than asking you to reword the question.
The duplicate warning on an AI Solution deployment's cost forecast displays correctly and offers Count duplicates once. Pricing and control rows that can't be saved now show an error next to the row.
Changing the Compare on date date quickly no longer shows the previous date's figures.
New personal access tokens keep the name you type.
The CLI sign-in screen lists access to cost data and to Capabilities, AI Solutions and Transformation Cases.

September 27, 2026

Scenario figures are fairer and look further ahead

People cost is now weighted by FTE, so part-time staff are costed at their share of full-time pay. Agent cost from agent pay records and approved AI Solution deployments now appears beside people cost in scenario comparisons.
Dates after today are projected from dated placements, pay and approved deployments instead of repeating today's figures.
Every scenario delta page has Compare on date, and the scenario home page shows a year-by-year Path over time against its source. Each year loads on its own, so large organisations see results as they arrive.
Existing figures calculated with the older cost formulas are rebuilt automatically, so today's comparisons no longer mix old and new totals.

More for agents, the API and the CLI

POST /api/v1/batch runs up to 200 actor, placement, compensation and position writes in one request. Later operations can reference earlier results, and the batch rolls back as a whole by default.
GET /api/v1/scenarios/{scenario}/timeline returns scenario, source and difference figures for up to 12 dates in one call. The CLI adds orgonaut scenario timeline, and connected AI tools get the same figures from the MCP tool scenario.timeline.
API limits now follow your plan, per user per organisation.
Astro can answer how a scenario looks in future years or on dates you name, drafts several explicit changes as one all-or-nothing bundle, and knows what's on this page.
CLI 0.1.3 signs in with read access to Capabilities, AI Solutions and Transformation Cases. Actor responses include location, and actor updates list any fields they did not write.

Clearer data protection

A new Security & Data page explains hosting region, tenant isolation, access controls, how Astro uses your data, the services we use, and retention.
API, MCP and CLI tokens without costs.read no longer receive salaries, day rates, budgets or cost totals, even when their owner can see them. Responses that withhold costs say so in an X-Orgonaut-Redacted: costs header.

Fixes

Scenario delta pages load more reliably on large organisations, and partly typed years no longer produce an empty comparison.
When the AI provider refuses a request, Astro now says why: out of credit, a request too large for the provider's limit, or a short rate limit.
AI Solution pricing rejects two rows with the same label, and warns about rows that repeat an existing label and rate.
Form fields on AI Solution and Transformation Case pages no longer overlap on narrower screens.

September 24, 2026

Astro can navigate transformation catalogues

Astro can now list and search Work Activities, Business Capabilities, AI Solutions, and Transformation Cases, then inspect a selected record by name or from its open detail page.
Work, Capability, and Solution answers preserve Live, scenario, and snapshot context; Transformation Case answers use the source and target stored on the case.
Answers link back to the matching Orgonaut screen and retain the same plan, role, cost, workforce, and metric redaction rules as the underlying product surfaces.
These additions are read-only and do not let Astro alter Work, Solutions, Cases, approvals, economics, or publications.

September 19, 2026

Capabilities, AI Solutions, and Transformation Cases are now available

Capabilities now connect contextual assessments, outcome measures, Work mappings, governed evidence, ownership, and completeness warnings so teams can show what should improve and what is still missing. Capabilities are available on Team and above.
AI Solutions provide governed catalogues, immutable published versions, claims, mandatory controls, contextual deployments, forecasts, risk, autonomy, cost, and accountable human ownership. AI Solutions are available on Business and above.
Transformation Cases bind an explicit source to a target scenario and keep scope, capability movement, changed Work, separate value lanes, assumptions, readiness, human approval, and the native twelve-section report connected. Cases and reports are available on Business and above; Agency adds whitelabel reporting.
Permission-filtered API, Astro, MCP, and Orgonaut CLI reads are available for these domains. Those surfaces do not gain new write, approval, publication, or autonomous restructuring authority.
The September 17 private-Alpha notes remain below as the historical record of the implementation that preceded this general-availability release.

September 17, 2026

Transformation Cases turn scenarios into printable AI value propositions

Private Alpha organisations can now bind one baseline to one exact-lineage target scenario and build a guided capability-led business case without copying organisational totals into a separate report store.
The builder keeps cash savings, avoided cost, released capacity, service, growth, risk, implementation, recurring cost, and consultancy fees separate, with explicit assumptions, confidence, evidence, and workforce decisions.
Readiness checks surface stale or incomplete inputs before approval, while the twelve-section report can be projected for client-safe, restricted, or consultancy-internal audiences and printed for review.
Released capacity is never presented as payroll saving unless a compatible approved workforce or procurement action supports the claim.
Capability, Solution, and Transformation Case facts are now available through permission-filtered API, Astro, MCP, and Orgonaut CLI reads, with the same scenario semantics and no new AI write authority.

Governed AI solutions can now be versioned and deployed into scenarios

Private Alpha organisations can maintain reusable copilots, agents, automations, workflows, platforms, and service assets in a searchable Solutions catalogue.
Draft versions capture purpose, supported Work, assurance controls, risk, autonomy, and pricing defaults; publishing locks the exact reviewed specification.
Live and scenario deployments pin one version and record organisation scope, accountable human ownership, optional agent actors, timing, effort, confidence, and cost completeness.
Mandatory controls gate activation, cost forecasts respect separate permissions, and snapshots and archived scenarios remain read-only.

Business capabilities connect AI change to measurable outcomes

Private Alpha organisations can define outcome-oriented capabilities and assess maturity, performance, resilience, AI readiness, ownership, and confidence in Live or a scenario.
Capability detail now connects supporting Work, candidate AI solution deployments, dated outcome measures, explicit limitations, and governed evidence references in one reviewable workspace.
Portfolio warnings make missing ownership, Work, outcomes, and proof visible before a capability is used in a client decision.
Snapshots and archived scenarios remain read-only, while plan, rollout, and role permissions control access throughout the workspace.

September 5, 2026

Promotion rollups, Positions, and account controls are more reliable

Scenario promotion now rebuilds Live rollup metrics from the newly promoted structure while preserving earlier aggregate history in the archived Live snapshot.
The Positions page no longer performs a duplicate controller-side data load before Livewire renders the filtered list.
Profile deletion now completes reliably after password confirmation and signs the user out immediately; owners must still transfer ownership before deleting their account.
Product analytics no longer send user email addresses or organisation, tenant, and scenario names or slugs; telemetry uses internal numeric identifiers and route context instead.

July 31, 2026

OrgSpec files now import into Orgonaut

The Imports wizard now treats .orgspec.yml as the primary format and accepts canonical OrgSpec YAML or JSON directly, with a preview of actors, units, positions, placements, and compatibility warnings before import.
OrgSpec imports preserve human, agent, and robot actor kinds and build explicit hierarchy, manager, position, and placement records in either the Live View or a new scenario.
Canonical files are checked against OrgSpec 0.1 plus graph reference and cycle rules before any records are written; the versioned bridge remains supported for existing automation.
Stable OrgSpec source IDs make repeated imports update matching records, while unsupported protocol data remains attached as OrgSpec metadata.
Invalid OrgSpec entities are quarantined as source records to correct and reimport; existing CSV quarantine editing remains unchanged.

April 25, 2026

CLI scenario team and department workflows expand

The Orgonaut CLI can now create, update, and delete teams and departments inside active draft scenarios.
Team and department commands use the same --input, --body, --set, and --json patterns as the existing scenario write commands, so agent workflows can model org-structure changes without switching to the web UI.
Live baseline mutations remain blocked for cli.access tokens; these new writes are scenario-only.

April 19, 2026

Position forms now open in place

Adding or editing a position now opens a wide modal from the Positions list, Position profile, Charts/Org Units menus, and scenario add menus instead of navigating to separate create or edit pages.
Position forms keep the same role, budget, team, and metadata controls while moving planning controls, budget fields, and effective dates into Advanced to reduce modal height.
Legacy Position create/edit URLs now return 404; backend store and update routes continue to support modal saves and integrations.

Team forms now open in place

Adding or editing a team now opens a wide modal from the Teams list, team detail pages, department team tables, Charts/Org Units menus, and scenario add menus instead of navigating to separate create or edit pages.
Team forms keep the same core fields while using a more compact layout: parent and type sit together, with purpose and effective dates tucked into Advanced.
Legacy Team create/edit URLs now return 404; backend store and update routes continue to support modal saves and integrations.

Department forms now open in place

Adding or editing a department now opens a wide modal from the Departments list, department detail pages, Charts/Org Units menus, and scenario add menus instead of navigating to separate create or edit pages.
Department forms keep the same fields, validation, scenario banner, parent selector, and department-type picker while preserving the current screen context.
Legacy Department create/edit URLs now return 404; backend store and update routes continue to support the modal workflow and integrations.

April 18, 2026

People creation now opens in place across the app

Creating a new person now opens a wide modal from the People directory and other supported launch points instead of sending you to a separate /people/create page.
The modal keeps the same core People form fields and validation flow, so the create experience stays familiar while fitting better into matrix, charts, department, and scenario workflows.
People create links that used to navigate away now keep you on the current page, then close the modal and show the new profile immediately after save.

People editing now opens in place across the app

Editing a person now opens a wide modal from the People list and the person profile instead of navigating to a dedicated /people/edit/{actor} page.
The modal focuses on the core People profile form while compensation, detailed placements, and delete actions remain on their dedicated person profile sections.
People edit actions now stay in context: save closes the modal, shows the standard toast, and refreshes the current list or profile without a full-page detour.

Agent and robot forms now use the same modal flow

Creating or editing agents and robots now opens the same wide in-place modal pattern used for People instead of navigating to dedicated create or edit pages.
Agent and robot lists, profiles, department actions, and scenario add menus now keep you in context while saving the actor profile.
Legacy Agent and Robot create/edit URLs now return 404; backend store and update routes continue to work.

April 10, 2026

Astro capability answers are faster and less noisy

Broad Astro help questions such as What can you do?, What can Astro do here?, and Help me get started now answer directly in both Live and scenario contexts instead of refusing in Live or routing through a long recommendation-style response.
Those capability/help replies now stay intentionally minimal by default: Astro answers the question and suggests a few example prompts inline, without automatically adding generic Why, Assumptions, Sources, How Astro worked, or extra follow-up action cards.

April 9, 2026

Astro phased programs and trace details are easier to review

Phased scenario programs now keep review-only checkpoints out of the write path, so Astro stops at a real checkpoint instead of drafting placeholder scenario updates that later fail generic validation.
The phased-program card now shows one active checkpoint plus a compact timeline, with metrics, dependencies, rollback notes, and risks moved behind checkpoint details instead of repeating the same data in nested blocks.
The reply details panel now uses How Astro worked and shows per-agent summaries for the planner, resolver, and bundle-expansion steps that contributed to the turn.
Astro reply options are now quieter by default: one primary follow-up prompt plus one primary navigation action, with remaining links and prompts behind More options.
Clarification candidates now split Use as prompt from Open record, so Astro no longer hides two different outcomes behind one ambiguous chip.
Reply actions now use explicit intent labels across workspace and overlay, such as Open settings, Review changes, View activity, and Open guide, so prompt-vs-navigation outcomes stay obvious.

April 6, 2026

Astro now shows real runtime steps while it works

Astro reply details still expose the actual execution path, agent, tool calls, retries, and fallback or clarification reasons for the turn instead of cycling through canned “thinking” labels.
The workspace and overlay now also show live in-flight routing, tool, and fallback steps on the pending card while Astro is still working, rather than a static canned status line.
Server-intercepted phased-program checkpoints also report their planner path from stored proposal metadata so larger scenario programs stay inspectable even when no model run was needed.

April 4, 2026

CLI installs and browser login are now production-ready

The first-party CLI can now be installed from app.orgonaut.co/cli/install.sh, with stable versioned binary URLs served from Orgonaut-hosted downloads instead of raw repository links.
Browser login now issues the full default CLI v1 ability bundle, so a successful orgonaut auth login session can use the shipped read, report, and scenario-safe write commands immediately.

April 3, 2026

Astro expands governed scenario execution for larger restructures

Astro now makes its execution boundary explicit before confirmation, showing whether you are in hard rails or inside a mutable scenario sandbox for supported governed changes.
Inside mutable scenarios, Astro can now draft bulk compensation updates, placement redistribution, and broader restructure programs from higher-level goals instead of requiring low-level record ids up front.
The governed plan-and-confirm flow now stays reviewable across the product and remote MCP, with affected counts, before-and-after totals, dependency checks, rollback notes, and phased checkpoints for larger transformations.

April 1, 2026

Change Log launches in the app footer

Added a public /updates page for published product updates.
Added a Change Log link in the shared app footer and the public auth-page footer links.
Added a Codex publishing skill so substantial shipped work can append a new published entry here.

March 31, 2026

Astro answers product questions from indexed knowledge

Astro now grounds product-help answers in indexed Orgonaut docs, API reference, CLI guidance, and runbooks instead of relying on generic model memory alone.
Retrieval now includes reranking and usefulness evaluation so how-to and troubleshooting answers stay closer to shipped product behavior.
Documentation updates can flow into Astro on a recurring reindex path instead of waiting for manual prompt rewrites.

March 29, 2026

Astro can draft restructure plans and hand them off safely

Astro can now produce read-first restructure plans for AI-first operating model changes and broader organisational redesign work.
Governed proposal bundles turn approved plans into bounded scenario changes instead of freeform mutations.
New transformation playbooks and apply-ready handoff prompts make it faster to move from analysis to controlled execution.

March 26, 2026

Orgonaut CLI v1 ships

Added a first-party CLI for teams that want scripted access to Orgonaut workflows outside the browser.
The CLI complements the web app for technical evaluators, automation work, and MCP or API-adjacent operating patterns.
Product docs now cover setup and usage guidance for the CLI surface.

March 25, 2026

AI Tooling usage sync lands

Orgonaut can now ingest AI coding-tool usage data and map it back to actors by email.
Usage metrics roll up to actor, team, and department surfaces so leaders can compare AI activity with org structure.
Demo data and API endpoints now support experimenting with these metrics without wiring a live provider first.

March 24, 2026

Branding and white-label controls arrive

Organisations can upload and serve tenant-specific brand assets across the product.
Brand name and visual changes now refresh immediately with cache-busted asset delivery.
Plan entitlements now control access to branding features so white-labeling can be sold cleanly by tier.

March 22, 2026

Self-serve billing and subscriptions go live

Tenant owners can now compare plans, start paid subscriptions, and open the Stripe-hosted billing portal from billing settings.
Trial state, subscription lifecycle, and product limits now run through a real commercial model instead of placeholder access rules.
Member role management also expanded in the same release window, making it easier to invite users with the right level of access.

March 17, 2026

Astro and MCP become first-class product surfaces

Launched the dedicated Astro workspace alongside the quick overlay for in-context questions while browsing.
Added tenant-bound OAuth and remote MCP access so external clients can connect to the same governed Orgonaut model.
Astro gained chat history, scoped memory, capability browsing, governed proposal confirmation, and scenario-aware routing across live, scenario, and snapshot views.

February 4, 2026

People, agents, and robots become first-class contributors

Orgonaut now models contributor kinds explicitly, with dedicated people, agents, and robots views across the product.
Team rosters, charts, matrix, scenario deltas, and activity language now distinguish human and machine capacity more clearly.
Agent profiles, machine cost tracking, and agent budgets make AI-native staffing visible in the same operating model as people.

January 31, 2026

New matrix and charts views make org structure explorable

Added an interactive matrix view with team-type columns, role-oriented rows, filters, tooltips, and export options.
Replaced the older org tree experience with a richer charts canvas built for navigation and analysis.
Performance work in aggregates and tree traversal keeps larger organisations more usable while exploring visualisations.

January 28, 2026

Snapshots, restore, and lineage complete the scenario loop

Scenario promotion now includes review flow and stronger baseline safety checks before live changes are applied.
Snapshots let teams archive baseline states, inspect historical views, and restore an older baseline when needed.
Lineage views connect promotions and restores so teams can audit how the baseline evolved over time.

January 15, 2026

CSV org import launches

Added a structured CSV import flow with validation, progress tracking, review screens, and quarantine handling.
Imports can populate live baseline or seed a scenario, with manager resolution and safer org-unit handling.
The importer creates a practical path for bringing external org data into Orgonaut without large amounts of manual re-entry.

December 31, 2025

Live View becomes the product home

Added a Live View summary dashboard with baseline metrics, highlights, and recent activity instead of the older dashboard and flight-deck split.
Scenario deltas gained clearer badges and stronger summary cues so teams can review change impact faster.
Activity surfaces on scenario and live pages became easier to scan as the product moved toward a narrative review experience.

December 7, 2025

Scenario comparison becomes much more reviewable

Added dedicated scenario delta comparison with changed-record focus, event classification, and an API/UI path for comparing a scenario with its source.
Scenario pages were rebuilt around aggregate cards, FTE totals, delta charts, and cleaner Livewire-driven review flows.
Slug-based scenario routing and compare actions made sharing and reopening scenarios more reliable.

December 4, 2025

Single sign-on and linked accounts arrive

Added Socialite-based sign-in flows and social login buttons across the auth pages.
Users can now manage linked social accounts from settings instead of relying on one-time login setup only.
Deployment and environment handling were expanded in the same release window to support OAuth, session, and production setup more cleanly.

November 24, 2025

Financial rollups become currency-aware

Added centralized default currency management, formatting, and conversion across key org and team metrics.
Org unit aggregate snapshots matured into a stronger reporting backbone for cost, headcount, and team-count rollups.
Teams and departments started surfacing clearer cost figures instead of raw unformatted values.

November 21, 2025

Scenario cloning ships with task tracking

Added async scenario cloning with batch jobs, progress tracking, rollback and resume paths, and dedicated task management screens.
Cloned scenarios preserve more structural context so larger modeling branches can be created without rebuilding everything manually.
The cloning flow also became available through an API-based async creation path instead of a single synchronous UI action.

October 30, 2025

Activity logging moves to a real audit model

Replaced legacy logging with append-only audit_events, structured diffs, request metadata capture, and observer-driven event creation.
Activity screens started moving from raw log rows toward narrative review, filtering, and grouped event exploration.
This laid the groundwork for replay, scenario-safe auditing, and richer historical review later on.

October 25, 2025

Placements, FTE, and compensation modeling level up

Added person compensation management, variance tracking, API support, and richer compensation workflows in the UI.
Standardized FTE and allocation handling across placements so staffing capacity is modeled more consistently.
Position budgeting and actual compensation became clearer to compare, which made scenario planning and staffing review more practical.

September 30, 2025

Org structure management becomes org-unit first

Finished the shift toward org-unit-first structure management, with teams, departments, people, and positions increasingly routed through canonical org-unit relationships.
Added tenant-scoped department types, team types, and improved hierarchy-aware forms so structure metadata became more explicit and reusable.
Context-bleed protections were extended across org units and related editing flows to keep baseline and scenario data separated.

September 18, 2025

Scenario-aware routing lands across the app

Added scenario context services, middleware, prefixed routes, helper functions, and scenario-aware links so users could move through the app without losing modeling context.
Baseline and scenario navigation became much more explicit with context banners, tabs, and shared route helpers.
This was the turning point where scenarios started behaving like a first-class working mode instead of a thin overlay.

August 28, 2025

Orgonaut’s first multi-tenant platform foundation ships

Established the early multi-tenant app foundation with tenant resolution, subdomain support, a tenant chooser, onboarding, and tenant-aware authorization.
Shipped early API v1 coverage, Sanctum ability controls, token management, initiatives, and stronger Scribe-backed API documentation.
The initial matrix board, org-unit tree work, and Livewire-heavy management screens set the direction for Orgonaut as a planning platform rather than a simple CRUD app.