@anyforge/control 0.6.3 → 0.7.0

package/README.md

@@ -74,9 +74,26 @@ anyforge oracle download <session-id> <file-id> --output ./downloads
 
 Oracle login uses browser authorization with PKCE and stores its credential in
 `~/.anyforge/oracle`. It leaves your inference proxy and MCP setup unchanged.
-`anyforge oracle logout` revokes and clears that Oracle login. For unattended
-use, an attributable API key in `ANYFORGE_API_TOKEN` takes precedence over the
-saved Oracle login.
+For unattended use, an attributable API key in `ANYFORGE_API_TOKEN` takes
+precedence over saved Oracle logins.
+
+Each login belongs to one workspace, and you can keep one per workspace. The
+workspace name shows in the welcome card, the bottom line, `/status` and the
+login message.
+
+```bash
+anyforge oracle login --workspace "Beta Labs"   # add a workspace; it becomes active
+anyforge oracle workspaces                      # list saved workspaces (--json)
+anyforge oracle use "Acme Engineering"          # change the active workspace
+anyforge oracle exec "..." --workspace company-2  # one command only
+anyforge oracle logout                          # the active workspace (--workspace <name>, --all)
+```
+
+`--workspace` on `login` only pre-selects the workspace on the consent page;
+the CLI reports the one you actually connected. In a conversation, `/workspace`
+switches to another saved workspace and starts a new conversation there. With
+`ANYFORGE_API_TOKEN` set, the key's workspace is used and switching is refused
+with an explanation.
 
 Interactive conversations are read only by default. Use `oracle login --write`
 and start with `oracle --write` to enable workspace edits. Consequential edits
@@ -85,9 +102,9 @@ and external MCP writes additionally require `--approve`. `oracle exec` always
 remains read only.
 
 Use Shift+Enter for multiline input. Type `/` for the command palette:
-`/help`, `/status` (session, access, model, last turn, usage and limits),
-`/new`, `/clear`, `/resume`, `/context`, `/attach`, `/copy`, `/files`,
-`/usage`, `/model` and `/exit`. `/design [topic]`, `/catchup` and
+`/help`, `/status` (session, workspace, access, model, last turn, usage and
+limits), `/new`, `/clear`, `/resume`, `/workspace`, `/context`, `/attach`,
+`/copy`, `/files`, `/usage`, `/model` and `/exit`. `/design [topic]`, `/catchup` and
 `/remember [what]` are answered by the Oracle itself, as in the web widget;
 acting on `/catchup` decisions needs a session started with `--write --approve`.
 
@@ -114,7 +131,7 @@ See the [CLI guide](https://anyforge.ai/docs/cli) for the full command contract.
 |---|---|
 | `anyforge init` | Authorise this device and patch local agent configs |
 | `anyforge whoami` | Show the company, scopes and endpoint this key acts as (asks the server) |
-| `anyforge status` | Verify the proxy is reachable and your BYOK key is configured |
+| `anyforge status` | Check server identity, local configuration and personal recorded activity (`--json` supported) |
 | `anyforge logout` | Clear the local credential file **and revert patched configs** (does not revoke server-side) |
 | `anyforge apply-patch` | Apply a unified diff from a file or stdin via `git apply` |
 
@@ -202,3 +219,39 @@ Both validate your AnyForge API key, look up your company's BYOK provider key, f
 ## License
 
 Apache-2.0
+
+### Check a Control installation
+
+Run `anyforge status` after setup and after making a real request in your agent.
+It authenticates against the saved endpoint (or the explicit endpoint override),
+shows the current user, company and granted scopes, and reads the latest recorded
+Control proxy usage and optional Claude Code subscription telemetry for that user
+in that company, across devices. Role checks still apply to individual actions.
+A successful check verifies the Control API used by MCP; confirm the actual MCP
+connection in your agent client. It does not send an inference request or charge
+for a test call.
+
+The three connections are separate:
+
+- **MCP** provides access to AnyForge work and tools. It does not route inference
+  or capture every local conversation.
+- **Inference proxy** routes supported requests through the company's BYOK key.
+  Configured settings and historical usage do not prove forwarding works now.
+- **Subscription telemetry** is optional. Subscription inference stays with the
+  provider; exported token counts and estimated cost appear at `/usage`, not as
+  full conversation traces at `/traces`. No prompts are exported by this setup.
+
+Status inspects the current shell, Claude Code user/project settings and the
+standard stdio MCP configuration written by init. Matching settings are local
+observations, not proof of the client's effective configuration: managed settings,
+other clients and hosted MCP need checking in the client itself. “Not detected”
+does not mean disabled. Missing activity, unavailable history, and an older key
+without user attribution are reported separately. An unavailable history read exits
+1; authentication failures use the normal Control API error exit code 4.
+
+If telemetry has no recorded activity, restart Claude Code after setup, use it,
+allow its exporter interval to complete and rerun status. If inference fails,
+check the company's BYOK provider key and the agent's endpoint. If the displayed
+company or user is wrong, reconnect with `anyforge init` rather than editing an ID.
+The server route and its Firestore indexes must be deployed before a newly built
+CLI can use this diagnostic command; a 404 is not an authentication verdict.