## Summary Build-out **and hardening** of the `/orchestrator` coding-agent workbench, plus a small app-shell startup-robustness fix. Continues the orchestrator-view work and **stays in lockstep with the team's parallel orchestrator commits on `develop`** — where this overlapped (the sub-agent credential bridge, the DRY capability const, the `getCodingAgentStatus` thread fold-in), I took `develop`'s canonical version and kept only what's genuinely additive. Synced to **0 behind `develop`**. The two transient `orchestrator-task-service` naming reds were `develop`'s own WIP and are resolved by the sync (the team re-pointed those assertions at the ACP spawn payload). Full verification below. ## What's in here ### Orchestrator - **`plugin-task-coordinator/src/index.ts`** — capabilities are a single shared `ORCHESTRATOR_CAPABILITIES` const reused across the GUI/XR/TUI views, with param schemas so a voice/NL planner can discover each capability's arguments (converged with `develop`). - **Capability manifest↔dispatch parity regression test** (new) — `orchestrator-capability-parity.test.ts` fails if the declared capabilities ever drift from what `runOrchestratorCapability` dispatches (this drifted before: `orchestrator-update-task`/`-validate-task`). Adds a `test` script so CI (`turbo run test --filter=./plugins/*`) actually runs it. - **`packages/app-core/src/api/server.ts`** — mount `handleSensitiveRequestRoutes` (built + unit-tested upstream); each branch self-authorizes via `ensureCallerAuthorized`, so it doesn't widen the unauthenticated surface. - **`agent-routes.ts`** — document the intentionally-empty `/metrics` and `/workspace-files` stubs; **`docs/orchestrator-buildout-followups.md`** — code-grounded status + Tier-2 roadmap. ### App-shell startup hardening (separable concern) - **`packages/ui/src/state/startup-phase-poll.ts`** — a stale `elizaos:active-server` pointing at a now-unreachable / CSP-blocked remote backend used to wedge first-run forever (the poll retried the dead address until `BACKEND_TIMEOUT`; clearing cookies didn't help — the pointer is in localStorage). Now: on a **connection-level** failure (no HTTP response) against a non-loopback, non-same-origin base on an http(s) page — **never on native mobile**, where the remote IS the agent — clear the saved server, re-point at the local origin, and reach the backend (one-shot). Decision is a pure exported `shouldFallBackToLocalOrigin`. - **Regression tests** — a unit matrix over `shouldFallBackToLocalOrigin` (fires for the wedge; never for HTTP errors / loopback / same-origin / mobile / non-http) plus an end-to-end test driving full recovery from a dead remote to `BACKEND_REACHED`. > This app-shell fix is logically separate from the orchestrator feature; happy to split it > into its own PR if reviewers prefer. It's included here because it was found and fixed in the > same first-run-hardening pass. ## Explicitly NOT duplicated Where `develop` shipped the same thing in parallel — credential-bridge source, the `getCodingAgentStatus` thread fold-in, a `getCodingAgentStatus` test, the orchestrator naming tests — this branch takes `develop`'s version. `client-agent.ts` is byte-identical to `develop`; `server.ts` differs only by an auth-safety comment; `index.ts` differs only by a biome-compliant line wrap. ## Verification - `plugin-agent-orchestrator` unit suite: **500 passed / 6 skipped** (the 2 prior naming reds resolved by the sync). - `packages/ui`: startup-fallback tests + `getCodingAgentStatus` test — **11 passed**. - `plugin-task-coordinator`: capability-parity test — **1 passed** (15 declared = 15 dispatched). - Typecheck clean across touched files (only pre-existing missing-optional-module errors remain); biome clean on every touched file. - Live (earlier): `/orchestrator` loads styled, controls work, agent responds via model. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

Greptile Summary

This PR adds Cerebras as a first-party BYOK provider across the full stack (auth types, provider-switch config, vault, first-run catalog, UI account dialog), hardens the app-shell startup poll with an auto-recovery path for the "auth-required + pairing-disabled" dead end, and adds an orchestrator error-boundary so unhandled service rejections return HTTP 500 instead of leaving requests hanging. - **Cerebras provider wiring**: `cerebras-api` is registered end-to-end — `DirectAccountProvider`, `FIRST_RUN_PROVIDER_CATALOG`, `PROVIDER_DEFAULT_MODELS`, `directProviderBaseUrl`, and the vault key-to-id map. `PROVIDER_LABELS` is missing the matching `cerebras` entry, causing the raw env-var name to surface in the vault UI. - **Startup poll hardening**: `isRecoverableRemoteBase` is extracted and reused in the new auth-dead-end path. New regression tests cover fresh-user, returning-user, and pairing-enabled guard cases. - **Orchestrator error boundary**: `handleOrchestratorRoutes` wraps `dispatchOrchestratorRoutes` in a try/catch; a new regression test verifies the 500 path.

Confidence Score: 4/5

Safe to merge after adding the missing Cerebras label in the vault. The vault's PROVIDER_LABELS map is missing a cerebras entry despite CEREBRAS_API_KEY being added to PROVIDER_KEY_TO_ID. defaultLabel falls back to label ?? key, so the vault UI would display the raw string CEREBRAS_API_KEY rather than Cerebras for any user who stores a Cerebras key. Everything else — startup-poll recovery logic, orchestrator error boundary, Cerebras provider wiring, and escape-hatch buttons — looks correct and is well-tested. packages/vault/src/inventory.ts — the PROVIDER_LABELS map needs a cerebras entry to match the new PROVIDER_KEY_TO_ID registration.

Important Files Changed

| Filename | Overview | |----------|----------| | packages/vault/src/inventory.ts | Replaces regex-based provider-key classification with exact-key lookup. Adds CEREBRAS_API_KEY to PROVIDER_KEY_TO_ID but omits the matching entry in PROVIDER_LABELS, causing the vault UI to show the raw env-var name instead of Cerebras. | | packages/ui/src/state/startup-phase-poll.ts | Extracts isRecoverableRemoteBase and adds auth-required+pairing-disabled dead-end recovery path. Logic and test coverage are solid; IPv6 loopback check bug was flagged in a prior review thread. | | plugins/plugin-agent-orchestrator/src/api/orchestrator-routes.ts | Adds top-level error boundary wrapping dispatchOrchestratorRoutes; unhandled service rejections now return 500 instead of leaving requests hanging. Clean and well-tested. | | packages/agent/src/api/provider-switch-config.ts | Adds Cerebras to PROVIDER_DEFAULT_MODELS with a shared CEREBRAS_MODEL key for small/large, and extends clearPersistedFirstRunConfig to purge all provider-default model env vars on reset. | | packages/ui/src/components/shell/PairingView.tsx | Adds Use a local agent instead escape button; correctly placed inside the pairing-disabled branch so it is never shown when actual pairing is available. |

Flowchart

```mermaid %%{init: {'theme': 'neutral'}}%% flowchart TD A[runPollingBackend loop] --> B{getAuthStatus} B -->|required=false| C[Check firstRunStatus - BACKEND_REACHED] B -->|required=true with token| D[BACKEND_REACHED firstRunComplete=true] B -->|required=true no token| E{bootstrapRequired?} E -->|yes| F[BACKEND_REACHED firstRunComplete=false] E -->|no| G{pairingEnabled=false AND isRecoverableRemoteBase?} G -->|yes| H[recoverToLocalOrigin - clear server, reset deadline] H --> A G -->|no| I[BACKEND_AUTH_REQUIRED - PairingView] I --> J[User clicks Use a local agent instead] J --> K[startFreshFirstRunReload] B -->|network error| L{shouldFallBackToLocalOrigin?} L -->|yes| H L -->|no| M[accumulate error - eventual BACKEND_TIMEOUT] ```

Comments Outside Diff (1)

1. `plugins/plugin-task-coordinator/__tests__/unit/orchestrator-capability-parity.test.ts`, line 817-818 ([link](https://github.com/elizaos/eliza/blob/1ee907a7f8b073de53c86ff139599f79d6ba6b03/plugins/plugin-task-coordinator/__tests__/unit/orchestrator-capability-parity.test.ts#L817-L818))

**Regex silently misses single-quoted case labels** The pattern `/case\s+"(orchestrator-[a-z-]+)"/g` only captures `case "..."` with double quotes. Any capability dispatched via `case 'orchestrator-...'` (single quotes) would be treated as absent, causing the parity test to falsely report a dispatch-without-declaration violation. This is likely enforced by Biome today, but a comment noting the assumption would harden the test against future formatter changes.

_{Reviews (7): Last reviewed commit: ["fix(ui): add a "Start over" escape to st..."](https://github.com/elizaos/eliza/commit/940a01c32c906641dedc6771861ea544a90c2e58) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=34764168)}

elizaOS

🏗️ Work in Progress