@lesscap/baton-cli 0.8.2 → 0.8.4

package/README.md

@@ -4,7 +4,7 @@ The baton CLI: register/run a **worker** on a machine and manage
 workspaces/projects/requirements/tasks/sessions against a baton server.
 
 A worker is the thing that actually runs agent sessions: it listens to the
-server's command stream and, per session, spawns `claude` in a git worktree.
+server's command stream and, per session, runs Claude or Codex in the worker’s working directory.
 
 ## Install
 
@@ -19,17 +19,16 @@ in (the worker spawns it to run each turn). Override the path with
 ## Run a worker
 
 ```sh
-# 1. cd into the git repo the agent should work in
-#    (each session gets its own worktree branched off it)
+# 1. cd into the directory the agent should work in
+#    (sessions share files; Agent conversations remain independent)
 cd /path/to/your-repo
 
 # 2. register this machine as a worker for a project
 baton worker register \
   --url https://baton.fmap.dev/api \
   --project <projectId> \
-  --name my-machine \
-  --baseBranch main
-#    → generates ./.baton.json with server, project, base branch, and worker token
+  --name my-machine
+#    → generates ./.baton.json with server, project, and worker token
 
 # 3. run the worker daemon (foreground; Ctrl-C to stop)
 baton worker run
@@ -40,17 +39,33 @@ running, it shows up (alive) under the project's workers in the web back-office;
 new sessions / inbound DingTalk messages are then executed by it.
 
 `.baton.json` is per-directory local state (gitignored by convention) and is
-generated by `baton worker register`; `baton init` is optional. `--baseBranch`
-wins over `BATON_BASE_BRANCH`, then an existing saved value. If none is set,
-registration records the repo's current branch, falling back to `main`.
-
-Before creating each new session worktree, the worker fetches that branch and
-forks from the updated `origin/<branch>` ref without moving the source checkout.
-Repositories without an `origin` use their local branch. Environments that keep
-Git credentials in a separate broker can set `BATON_GIT_SYNC_BIN` to a trusted
-executable; Baton invokes it as `<executable> <repo> <branch>`, then verifies the
-updated remote-tracking ref before creating the worktree. The helper must print
-the synced commit hash to stdout.
+generated by `baton worker register`; `baton init` is optional. Session startup
+never rewrites this project configuration, fetches Git branches, or creates a
+worktree. Existing directories, including non-Git and empty Git repositories,
+can host sessions. Development skills may manage worktrees explicitly.
+
+Agent subprocesses inherit `BATON_SERVER`, `BATON_PROJECT_ID`, `BATON_WORKER_ID`,
+and `BATON_WORKER_TOKEN`, so Baton commands keep their context from subdirectories.
+Server resolution is `--url > BATON_SERVER > .baton.json.server > BATON_URL > localhost`;
+project resolution is `--project > BATON_PROJECT_ID > .baton.json.project`.
+
+Baton runner records and attachments live under
+`${XDG_DATA_HOME:-~/.local/share}/baton/runtime/<server-hash>/worker-<id>/sessions/<id>`.
+Deleting a session removes its Baton runtime files and preserves project files.
+
+## Development services
+
+```sh
+baton service run web --cwd /absolute/project/path -- pnpm dev
+baton service ls
+baton service stop web
+```
+
+`--cwd` is required; relative paths resolve from the CLI's current directory.
+Services belong to the worker and continue after a session stops or is deleted.
+They stop when explicitly stopped, when the application exits, or when the worker
+exits. Restarting the worker does not restart services. Logs live in the worker's
+runtime `services/` directory; the run result prints their path.
 
 ## Other commands