---
title: "Introducing AI Subscriptions: account health without a shared password page"
summary: "A privileged workbench for model-account status, usage and sign-in repair, with the login custodian kept outside the browser."
created: "2026-11-15"
updated: "2026-11-17"
revision: "4"
previous: "bfb91cf1c9db85f0aac8dca9349c7877b4489170"
reviewedThrough: "db9c004f146ca49dc313bc6b0a28d308d0d4b824"
sourceDigest: "23448bad02a277edf8e88402959cc7d2a8ae747572b094c14ae57ad6a8c4c8e9"
---

With this, your mind can show its members which connected AI accounts are usable and where a sign-in needs repair. This is account administration, not a public pool of model credentials. A copied dashboard does not grant a model plan, a provider login or permission to use somebody else’s subscription.

## Keep the custodian separate

`apps/ai-subscriptions/app.ts` serves the page and installs a capability on `/ai-subscriptions`; `backend.ts` exports its durable classes. `service.ts` keeps account summaries, activity, repair state, retry state and recipient locks in local SQL. `schema.ts` and `api.ts` define the checked contract. The browser in `public/app.js` asks for status or a repair interaction rather than receiving provider passwords.

```ts
case "ai-subscriptions":
case "subscriptions": // compatibility host, not a separate app
  return this.auth.require(request) || aiSubscriptions.fetch(request, this);
```

The service talks to a separately configured login custodian, whose runtime origin and token-secret path are validated configuration. The login material stays with that custodian. A five-minute maintenance schedule checks work without requiring an open tab. Activity delivery and mail matching live in their own modules; receipt routing is optional configuration, not a reason to forward arbitrary mail to a provider.

## Publishing credentials is a separate privileged operation

The `egress-publication` modules implement optional provider-specific secret publishers. They lease allowed accounts from the custodian and keep a stable vault secret for the mind’s sandbox egress. `egress-maintenance` handles the renewal path. Device authorization, allowed account sets and provider API origins belong in trusted configuration, never browser input. Do not copy this company’s publisher configuration or account names into another mind.

## What another mind would need

The basic pattern needs the complete app folder, the platform facet and schedule support, suitable UI packages, and a custodian service the owner controls or is authorized to use. It also needs the owner’s own eligible provider accounts and a vault-held device credential restricted to the custodian origin. Optional egress publication adds carefully scoped vault and provider integration requirements. There is no new service to connect merely to read this recipe, and this backport connects nothing. When rebuilding, start with a fake custodian, test sign-in and repair refusal, renewal expiry, duplicate maintenance events and receipt matching before enabling real accounts. Keep the whole host member-only and all secret material out of returned status objects. [Coding agents](/introducing/coding-agents) consume model access through their configured runner; [the Dash](/introducing/dash) is the broader member control plane.

Before calling the workbench ready, verify a signed-out request and a signed-in nonmember are refused on both the page and its RPC route. Then test a member using synthetic account summaries. A healthy status is not proof that a model request will succeed: expiry, provider limits and the separate runner configuration still matter. Keep repair and publication operations auditable, and make optional receipt routing explicit rather than treating every incoming message as login material.
