Skip to content

docs(seats): explain CLI publishing and seat restart path #2743

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lilyshen0722 merged 2 commits into from
Oct 25, 2026
Merged

docs(seats): explain CLI publishing and seat restart path #2743

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2b2e862
docs(seats): explain CLI release and seat restart path
lilyshen0722 Oct 25, 2026
5b5dbbc
docs(seats): locate operator pins and clarify manual deploy
lilyshen0722 Oct 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions packages/seats/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,21 @@ The adapters that run an agent CLI as a supervised seat: one prompt in, one CLI

It is private and is not published on its own. `@commonlyai/cli` depends on it as `file:../packages/seats` and lists it in `bundleDependencies`, so it ships inside the CLI tarball.

## Release path

- A push to `main` touching `cli/` or `packages/seats/` triggers
[npm publish](../../.github/workflows/npm-publish.yml). If the packed files changed,
it publishes the next CLI patch with seats bundled ([CLI package](../../cli/package.json)).
[Deploy Dev](../../.github/workflows/deploy-dev.yml) is manually dispatched and builds service images separately.
- The publish job assigns the version. PRs leave version lines alone
([version guard](../../.github/workflows/package-version-guard.yml), TASK-466).
- Operator-pinned fleet seats select their CLI path in each seat's local `run.sh` launcher,
outside this repo. Update that pin and restart the seat to load a release.
Global CLI installs must be upgraded too; publishing does not update a running seat.
- Check the running wrapper's CLI path and the live spawn argv to see what it runs
([diagnosis guide](../../docs/runbooks/diagnosing-a-silent-seat.md#2-read-the-live-spawn--the-prompt-is-in-argv)).
The registry describes configuration; it does not prove what was loaded.

**Rule:** nothing here imports Commonly code. An adapter that needs Commonly policy (the memory preamble, the legacy sandbox-trust names, the fleet seat-model switch) takes it as a host object through its factory, for example `createHermesAdapter(host)`. The CLI binds that host in `cli/src/lib/adapters/<name>.js`. `cli/__tests__/seats-package.test.mjs` enforces the import rule and checks that the tarball carries every source file.

The extraction plan is D62, extract-in-place.
Expand Down
Loading