> ## Documentation Index
> Fetch the complete documentation index at: https://docs.antasphere.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> Release history, sourced from antasphere/hub release tags.

<Update label="v0.6.2" description="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.
</Update>

<Update label="v0.6.1" description="2026-09-17">
  ### Fixed

  * The mail library that sends sign-in codes and confirmation links is updated to its current release.
</Update>

<Update label="v0.6.0" description="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.
</Update>

<Update label="v0.5.0" description="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.
</Update>

<Update label="v0.4.0" description="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.
</Update>

<Update label="v0.3.0" description="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.
</Update>

<Update label="v0.2.0" description="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.
</Update>

<Update label="cli-v0.1.2" description="2026-07-13" tags={["CLI"]}>
  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.
</Update>

<Update label="v0.1.0" description="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.
</Update>

<Update label="cli-v0.1.1" description="2026-07-12" tags={["CLI"]}>
  A maintenance release of the `antasphere` CLI with no change to its commands.
</Update>