Skip to main content
2026-10-18
hub 0.19.0 — The hub owns the catalogue of connected tools: a descriptor per tool, served with the organization’s verdict
2026-10-18
hub 0.18.0 — Tools open from the browser’s cache and bootstrap in one round trip (PRDCT-3584)
2026-10-13
hub 0.17.0 — The phone shell, the refreshed shell and the MCP gateway
2026-10-10
hub 0.16.5 — A restricted tool’s grant listed only in a granted organization
2026-10-10
hub 0.16.4 — Restricted tools listed per organization, tool cards open in the selected organization, the contract package on npm
2026-09-30
hub 0.16.3 — One login for every Antasphere CLI: the account CLI ships with the hub, the sign-in walls sized for a room
2026-09-30
hub 0.16.2
2026-09-30
hub 0.16.1
2026-09-30
hub 0.16.0
CLI
2026-09-30
@antasphere/cli 0.3.0
2026-09-28
hub 0.15.0 — Demo links, the refusal page after the form, a pass session mints nothing, one navigation on a tool sign-in
2026-09-27
hub 0.14.0 — Teams in an organization and tool access per team, and the purchase end to end
2026-09-25
hub 0.13.0 — The billing page in tabs, an Admin area of its own, and referrals that cannot be gamed
2026-09-25
hub 0.12.0 — Phase 3 of the billing rail: Stripe in the hub, the money comes in
2026-09-23
hub 0.11.0 — Billing rail phase 2: the hub keeps the credits
2026-09-22
hub 0.10.0 — The billing rail, phase 1: billing accounts, the usage ingest, the tool’s machine scope
2026-09-21
The account mails wear the brand: one shell for every mail Antasphere sends you, with the mark and the band.
2026-09-19
Each organization has a settings page: its name, its look (colour, form, gradient and grain) and its members, in one place. The mails your account sends come from Antasphere’s own mail service.
2026-09-19
A new dashboard, in the Antasphere look. Each organization now has a look of its own — a colour and a form — that every member sees. A tool you sign into with your account can create an organization for you when you set up a workspace there.
2026-09-17

Changed

  • This documentation is now written for account holders: what the account is, the tools that use it, and how to connect the CLI or an agent.
2026-09-17

Fixed

  • The mail library that sends sign-in codes and confirmation links is updated to its current release.
2026-09-17
A confirmation step for new accounts, and the dashboard in the Antasphere brand.

Added

  • A new account is confirmed from the “did you create this account?” email before it can be used, so an address nobody typed on purpose never becomes a live account.

Changed

  • The account dashboard wears the Antasphere brand: the woven-A mark, the Sentient face, the palette shared with every Antasphere tool.
2026-08-28
A durability and control release: you can see and manage the tools connected to your account, and operators get a restore path they can rehearse.

Added

  • A Connected applications page lists every Antasphere tool connected to your account, when it first connected, when it was last used, and what it can reach.
  • Instances can cap how many OAuth clients one account registers, and can retire registrations that were never used.

Changed

  • antasphere logout revokes the standing tool access that login granted, and the CLI now states exactly what it does and does not revoke.
  • An API key pinned to one organization behaves the same way as every other credential, and lists only the organization it is pinned to.

Fixed

  • Signing keys survive a restart and a secret rotation, so a deploy no longer invalidates the tokens tools are holding.
  • Restoring a backup brings back the secret the database is keyed to, checks every archive before replacing anything, and puts the previous instance back if any step fails.
  • Readiness now re-checks file storage instead of reporting the state it saw at boot, so an instance that has lost its store stops taking traffic.
2026-07-15
Signing in to an Antasphere tool now feels like one product rather than two: fewer screens, and pages that know which tool sent you.

Added

  • First-party Antasphere tools no longer show a consent screen. Following a tool’s sign-in link takes you to the tool.
  • Sign-up and confirmation pages carry the name of the tool you came from, so you know what you are signing in to.
  • Signing out of the hub also signs you out of the first-party tools you are signed in to.
  • Your account page lists the Antasphere tools you have used.

Fixed

  • Signing in part-way through a tool’s sign-in flow now returns you to the tool instead of stopping on the dashboard.
2026-07-15
A cleanup release that finishes the move to user-held credentials started in 0.2.0.

Changed

  • Tokens the hub issues now describe the person signing in. Which organization a request works in is chosen per request by the tool, not fixed into the token.
  • The earlier, transitional account-status endpoints and their scope are gone. Nothing in the documented surface uses them.
2026-07-15
Your credentials now belong to you rather than to one organization, so a single login reaches every organization you are a member of.

Changed

  • When you approve a tool, you approve it as yourself. The approval is not tied to one organization, and it keeps working as your memberships change.
  • Pick a default organization from the dashboard or the CLI, and new sessions start there.
  • Tools that work per organization can name the one they mean on each call, and fall back to your default when they do not.

Added

  • API keys can be pinned to a single organization at mint, and the dashboard shows which key is pinned where.
  • antasphere org list and antasphere org use show your organizations and set the one tool CLIs work in.
CLI
2026-07-13
The antasphere CLI can now show your organizations and choose the one other Antasphere tool CLIs work in.

Added

  • antasphere org list prints the organizations you belong to and marks the active one.
  • antasphere org use <id> sets the organization federated tool CLIs read as their context, and --unset clears it.
2026-07-13
The first release of the Antasphere hub: one account that signs you in to every Antasphere tool.

Added

  • Sign up with an email address and get a personal organization straight away, then create shared organizations and invite people into them.
  • Sign in to first-party Antasphere tools with your Antasphere account, so one login carries across the family.
  • The antasphere command-line client signs in from a terminal with a code sent to your mailbox, and stores the result in a local profile.
  • A tool’s command-line client can trade your hub login for its own short-lived credential, so you sign in once for every tool.
CLI
2026-07-12
A maintenance release of the antasphere CLI with no change to its commands.