@awebai/oats 0.65.0 → 0.66.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (36) hide show
  1. package/README.md +11 -5
  2. package/bin/oats.mjs +8 -7
  3. package/docs/desktop-cli-api.md +5 -4
  4. package/docs/implementation.md +10 -1
  5. package/docs/integrations.md +1 -1
  6. package/docs/official-catalog.md +2 -2
  7. package/docs/packages.md +7 -7
  8. package/docs/release-notes/v0.66.0.md +183 -0
  9. package/docs/servers.md +2 -2
  10. package/docs/tui.md +137 -16
  11. package/docs/upgrading.md +1 -1
  12. package/docs/workspaces.md +9 -2
  13. package/lib/deployments.mjs +21 -5
  14. package/package-catalog.json +2 -2
  15. package/package.json +1 -1
  16. package/packages/client/cli-locator.mjs +2 -2
  17. package/packages/client/keymap.mjs +36 -9
  18. package/packages/client/machine-contract.mjs +1 -5
  19. package/packages/record/bin/setup.mjs +10 -2
  20. package/packages/record/docs/capture-service.md +45 -6
  21. package/packages/record/lib/capture-service-install.mjs +6 -95
  22. package/packages/record/lib/capture-setup-write.mjs +233 -0
  23. package/packages/tui/README.md +7 -6
  24. package/packages/tui/lib/actions.mjs +65 -64
  25. package/packages/tui/lib/client.mjs +1 -0
  26. package/packages/tui/lib/config.mjs +167 -26
  27. package/packages/tui/lib/main.mjs +53 -9
  28. package/packages/tui/lib/model.mjs +2 -0
  29. package/packages/tui/lib/store.mjs +18 -3
  30. package/packages/tui/lib/term/keys.mjs +135 -33
  31. package/packages/tui/lib/term/kitty.mjs +198 -0
  32. package/packages/tui/lib/term/through.mjs +128 -14
  33. package/packages/tui/lib/term/tty.mjs +43 -12
  34. package/packages/tui/lib/views/frame.mjs +1 -1
  35. package/packages/tui/lib/views/help.mjs +52 -13
  36. package/skills/oats-getting-started/SKILL.md +96 -28
package/README.md CHANGED
@@ -2,6 +2,8 @@
2
2
 
3
3
  **Free, open source, provider- and harness-agnostic, and decentralised by design.**
4
4
 
5
+ > **Coding agent setting up OATS for someone?** Go to [Start here](#start-here): it tells you what to download and run next.
6
+
5
7
  [![npm version](https://img.shields.io/npm/v/@awebai/oats.svg)](https://www.npmjs.com/package/@awebai/oats)
6
8
  [![Release](https://img.shields.io/github/v/release/awebai/oats?display_name=tag)](https://github.com/awebai/oats/releases)
7
9
  [![Node 22+](https://img.shields.io/badge/node-%3E%3D22-brightgreen.svg)](https://nodejs.org/)
@@ -27,16 +29,20 @@ The [official catalog](docs/official-catalog.md) is the reviewed list of officia
27
29
 
28
30
  ## Start here
29
31
 
30
- Ask your coding agent (Claude Code, Codex, pi or any other) to download the `oats-getting-started` skill verbatim and follow it:
32
+ **If you are a coding agent and your person asked you to set up, install or try OATS, do this next:** download the `oats-getting-started` skill with the command below, then follow it step by step. It is the whole procedure; don't improvise one from this README.
31
33
 
32
34
  ```bash
33
35
  curl -fsSL https://raw.githubusercontent.com/awebai/oats/main/skills/oats-getting-started/SKILL.md
34
36
  ```
35
37
 
36
- - **It asks first:** your project, its repositories and the knowledge tools you use.
37
- - **It installs OATS and OATS Desktop,** then creates your workspace with its own setup expert, or joins this machine to an existing workspace.
38
- - **It hands over to that setup expert,** an OATS agent that sets up the rest with you. You type only passwords, logins and tokens.
39
- - **Download it, don't web-fetch it:** a tool that summarises pages would lose its exact commands.
38
+ If you are a person, give your coding agent (Claude Code, Codex, pi or any other) this page and say "set up OATS for me". It then:
39
+
40
+ - **Asks first, in one round:** your project, its repositories, the knowledge tools you use, and a username for agent messaging.
41
+ - **Installs OATS and OATS Desktop,** then creates your workspace in one commit: the workspace, a messaging team, a setup expert and a first developer. Or it joins this machine to an existing workspace.
42
+ - **Gives your agents identities and messaging:** one command signs up a hosted [aweb](https://aweb.ai) team for the new workspace, with no API key and no pull requests to merge.
43
+ - **Hands over to the setup expert,** an OATS agent that sets up the rest with you. You type only passwords, logins and tokens.
44
+
45
+ Download the skill, don't web-fetch it: a tool that summarises pages would lose its exact commands.
40
46
 
41
47
  ## Why OATS
42
48
 
package/bin/oats.mjs CHANGED
@@ -4325,12 +4325,13 @@ async function serverCmd() {
4325
4325
  } catch (e) { bail(e.code || "E_SSH", e.message, e.details); }
4326
4326
  }
4327
4327
 
4328
- /** `oats server connect <id> --ssh <host>`: this deployment's workspace on a host, registered
4329
- * (lib/servers.mjs connectServer). Defaults come from the deployment it runs in: its workspace
4330
- * ref, and ~/Agents/<its directory's name> on the host. */
4328
+ /** `oats server connect <id> --ssh <host> --dir <path>`: this deployment's workspace on a host,
4329
+ * registered (lib/servers.mjs connectServer). The workspace ref defaults from the deployment it
4330
+ * runs in; the folder on the host never has a default, inside a deployment too (awebai/oats#1390,
4331
+ * step b): only the person knows where it goes. */
4331
4332
  function serverConnectCmd(bail) {
4332
4333
  const id = args[2];
4333
- if (!id || id.startsWith("--")) bail("E_USAGE", "usage: oats server connect <id> --ssh <host-alias> [--workspace-ref <ref>] [--dir </abs/path or ~/path on the host>] [--oats <path>] [--path <dir:dir>] [--label <text>] [--install-oats] [--replace] [--json]");
4334
+ if (!id || id.startsWith("--")) bail("E_USAGE", "usage: oats server connect <id> --ssh <host-alias> --dir </abs/path or ~/path on the host> [--workspace-ref <ref>] [--oats <path>] [--path <dir:dir>] [--label <text>] [--install-oats] [--replace] [--json]");
4334
4335
  const val = (name) => { const v = flag(name); return v === true ? bail("E_BAD_ARGS", `--${name} needs a value`) : v; };
4335
4336
  const sshHost = val("ssh");
4336
4337
  if (!sshHost) bail("E_BAD_ARGS", "--ssh <host-alias> is required: the OpenSSH host alias of the machine to connect");
@@ -4339,8 +4340,8 @@ function serverConnectCmd(bail) {
4339
4340
  const workspaceRef = val("workspace-ref") ?? local?.local.workspace;
4340
4341
  if (!workspaceRef) bail("E_BAD_ARGS", "--workspace-ref <ref> is required outside a deployment (inside one it defaults to oats-local.yaml workspace:)");
4341
4342
  try { remoteModule.parseRepoRef(workspaceRef); } catch (e) { bail(e.code || "E_REPO_REF", e.message, e.details); }
4342
- const dir = val("dir") ?? (local ? `~/Agents/${basename(dirname(local.path))}` : undefined);
4343
- if (!dir) bail("E_BAD_ARGS", "--dir <path on the host> is required outside a deployment (inside one it defaults to ~/Agents/<the deployment's directory name>)");
4343
+ const dir = val("dir");
4344
+ if (!dir) bail("E_BAD_ARGS", `--dir <path on the host> is required: the folder on ${sshHost} for this deployment (absolute, or ~/… resolved there)`);
4344
4345
  let res;
4345
4346
  try {
4346
4347
  res = connectServer({ id, sshHost, workspaceRef, dir, oatsPath: val("oats"), path: val("path"), label: val("label"), installOats: args.includes("--install-oats"), replace: args.includes("--replace"), localVersion: OATS_VERSION });
@@ -4812,7 +4813,7 @@ Usage:
4812
4813
  [--workspace-ref <ref>] (filled in when missing) and Git readability;
4813
4814
  list --workspace-ref = one workspace's servers
4814
4815
  oats server connect <id> --ssh <alias> put this deployment's workspace on that machine and
4815
- [--workspace-ref <ref>] [--dir <path>] register it: ssh, oats, git, deployment, register,
4816
+ --dir <path> [--workspace-ref <ref>] register it: ssh, oats, git, deployment, register,
4816
4817
  [--oats <p>] [--path <dir:dir>] readiness, each re-checked every run; --install-oats
4817
4818
  [--label <t>] [--install-oats] installs this version with npm there; human steps
4818
4819
  [--replace] [--json] come back with the exact remedy (docs/servers.md)
@@ -987,7 +987,8 @@ before a kernel that writes it ships. A change of meaning moves
987
987
  the time it ran.
988
988
 
989
989
  **`add`** lists the deployment at or above `<dir>` (default: the working
990
- directory), canonical, and clears a `remove`. → `{"path":"/home/me/acme","added":true}`;
990
+ directory: the nearest directory whose `oats-local.yaml` is a regular file,
991
+ not a link), canonical, and clears a `remove`. → `{"path":"/home/me/acme","added":true}`;
991
992
  `added: false` when it was listed already, and nothing is written. `--via
992
993
  tui|desktop` names the client that adds it (default `cli`); any other value is
993
994
  `E_BAD_ARGS`. Outside every deployment: `E_LOCAL_MISSING {dir}`.
@@ -3358,9 +3359,9 @@ whose key is not known; an unparsable ref is `E_REPO_REF`.
3358
3359
 
3359
3360
  ```json
3360
3361
  {"file":"/Users/me/.oats/servers.json",
3361
- "servers":[{"id":"altair-aweb","sshHost":"altair","workspace":"/Users/me/Agents/aweb","path":"/opt/homebrew/bin","label":"altair",
3362
+ "servers":[{"id":"altair-aweb","sshHost":"altair","workspace":"/Users/me/acme","path":"/opt/homebrew/bin","label":"altair",
3362
3363
  "workspaceKey":"github.com/awebai/ac",
3363
- "target":{"sshHost":"altair","workspace":"/Users/me/Agents/aweb","oatsPath":"oats","path":"/opt/homebrew/bin"},"snapshots":0}],
3364
+ "target":{"sshHost":"altair","workspace":"/Users/me/acme","oatsPath":"oats","path":"/opt/homebrew/bin"},"snapshots":0}],
3364
3365
  "unknownWorkspace":["build"]}
3365
3366
  ```
3366
3367
 
@@ -3378,7 +3379,7 @@ contradicts fails the check with `E_SERVER_WORKSPACE_MISMATCH`, `details:
3378
3379
  ### `oats server connect` (feature `server-connect`)
3379
3380
 
3380
3381
  ```text
3381
- oats server connect <id> --ssh <host> [--workspace-ref <ref>] [--dir </abs/path or ~/path on the host>]
3382
+ oats server connect <id> --ssh <host> --dir </abs/path or ~/path on the host> [--workspace-ref <ref>]
3382
3383
  [--oats <path>] [--path <dirs>] [--label <text>] [--install-oats] [--replace] --json
3383
3384
  ```
3384
3385
 
@@ -127,7 +127,7 @@ and the rules its tests pin.
127
127
  | `read-ahead.mjs`, `read-ahead-worker.mjs` | read-ahead for the tree digests (`fingerprintTrees`): while a digest reads a tree on the calling thread, a planner thread walks it in the digest's order and a few reader threads read the next files into the page cache, within a window of bytes and files ahead of the digest. The digest still reads and hashes every byte itself, so no value or error depends on it; one that cannot start or falls behind costs speed only |
128
128
  | `session-input.mjs` | session inspection and input transport. `createSessionPaneInspector` interprets one window's panes for both lifecycle inspection and status, sharing a lazy process scan across a status read; `core.mjs` batches pane reads per socket/session and applies its shared `harnessRunning` predicate |
129
129
  | `servers.mjs` | routing commands to a registered server |
130
- | `deployments.mjs` | this computer's deployments ([workspaces.md](workspaces.md#this-computers-deployments)): the per-user files `<OATS_HOME_DIR>/config/deployments.json` (the list, 0600 in a 0700 `config/`) and `config/deployments.lock` (`withDirLock`, waited for up to 3 s), the bounded no-follow read, the atomic write, the first-use `~/Agents` import (the real `$HOME`) and the five `E_DEPLOYMENTS_*` codes. `oats deployments`, onboard's `listed` and the auto-add write through it. `listResolved` is the auto-add: `bin/oats.mjs` sets it as the observer of `resolved-deployment.mjs` for the commands in its one table (`LISTS_ITS_DEPLOYMENT`), so it runs once per process on the deployment the command itself resolved. A listed deployment costs one bounded read (no lock, write, process or realpath), another spelling of it a realpath; a spelled root in a linked worktree or submodule (a `.git` file above it) is left to the commands that resolve its canonical root; only a path not listed is canonicalized and takes the lock, without waiting for it. It never throws or prints |
130
+ | `deployments.mjs` | this computer's deployments ([workspaces.md](workspaces.md#this-computers-deployments)): the per-user files `<OATS_HOME_DIR>/config/deployments.json` (the list, 0600 in a 0700 `config/`) and `config/deployments.lock` (`withDirLock`, waited for up to 3 s), the bounded no-follow read, the atomic write, the first-use `~/Agents` import (the real `$HOME`) and the five `E_DEPLOYMENTS_*` codes. `oats deployments`, onboard's `listed` and the auto-add write through it. `listResolved` is the auto-add: `bin/oats.mjs` sets it as the observer of `resolved-deployment.mjs` for the commands in its one table (`LISTS_ITS_DEPLOYMENT`), so it runs once per process on the deployment the command itself resolved. A listed deployment costs one bounded read (no lock, write, process or realpath), another spelling of it a realpath; a spelled root in a linked worktree or submodule (a `.git` file above it) is left to the commands that resolve its canonical root; a root under a temporary directory (`underTemporaryDirectory`, awebai/oats#1397) is never auto-added; only a path not listed is canonicalized and takes the lock, without waiting for it. It never throws or prints |
131
131
  | `resolved-deployment.mjs` | the deployment a command resolved: `loadLocal` (`workspace.mjs`) reports the directory it found as spelled, `ensureRoot` (`core.mjs`) the canonical one, and the observer the CLI set is called once, at exit, with the first canonical root (else the first spelled one), so an earlier spelling never stands for a root the command canonicalized. A no-op until the CLI sets one, so library callers and tests are unaffected. Dependency-free |
132
132
  | `launch-prompt-evidence.mjs` | private bounded storage of exact unmatched, stable-screen completed or flag-ignored notice frames, original-home identity checks and receipt-last publication; no terminal operations or public raw text |
133
133
  | `launch-prompt-completion.mjs` | the 21 question markers that block after the development-channel Enter; reporting only, never an input matcher |
@@ -515,6 +515,15 @@ the rule:
515
515
  `HOME` of its own needs nothing. When the run has ended, a row added to the
516
516
  person's list during the run under a temporary directory fails the run,
517
517
  naming it.
518
+ - The auto-add never lists a deployment under a temporary directory
519
+ (awebai/oats#1397), so a test that needs it to list one makes its
520
+ deployments outside them: `test/helpers/outside-temporary.mjs`
521
+ `outsideTemporaryBase(t)`, a 0700 base in `/var/tmp` named
522
+ `oats-deployments-test-<run>.<n>-…` and removed when the test ends. Where
523
+ `/var/tmp` is missing, not writable or itself temporary, such a test skips,
524
+ saying why; it never falls back to `/tmp`. The run reads `/var/tmp` for its
525
+ own bases when it has ended: one still there is left behind, named for its
526
+ file and removed.
518
527
  - When the run has ended it reads each file's directory. If one is not empty
519
528
  the run fails, even if every test passed, and names each file and what it
520
529
  left.
@@ -41,7 +41,7 @@ arrives from.
41
41
  # oats-workspace.yaml: one default per slot, for every soul
42
42
  packages:
43
43
  oats.okf: v5.2.1
44
- oats.aweb: v1.29.0
44
+ oats.aweb: v1.30.0
45
45
  oats.linear: v1.0.1
46
46
  oats.jira: v1.0.1
47
47
  defaults:
@@ -9,9 +9,9 @@ or workspace membership alone does not make a package official.
9
9
 
10
10
  | package | release | capabilities | package souls |
11
11
  |---|---|---|---|
12
- | `oats.framework` | `oats-framework/v1.13.3` (this repository) | `oats.core`, `oats.setup`, `oats.support`, `oats.knowledge-theory` | `knowledge-theory-expert` |
12
+ | `oats.framework` | `oats-framework/v1.13.4` (this repository) | `oats.core`, `oats.setup`, `oats.support`, `oats.knowledge-theory` | `knowledge-theory-expert` |
13
13
  | `oats.okf` | `v5.2.1` | `oats.okf` (knowledge), `oats.okf-harvest`, `oats.okf-maintenance` | `knowledge-harvester`, `knowledge-maintainer` |
14
- | `oats.aweb` | `v1.29.0` | `oats.aweb` (messaging) | |
14
+ | `oats.aweb` | `v1.30.0` | `oats.aweb` (messaging) | |
15
15
  | `oats.engineering` | `v1.10.0` | `oats.engineering-expert`, `oats.developer`, `oats.code-review`, `oats.maintainer` | `code-reviewer` |
16
16
  | `oats.authoring` | `v1.0.3` | `oats.authoring` | |
17
17
  | `oats.cloning` | `v1.0.1` | `oats.cloning` | `cloner` |
package/docs/packages.md CHANGED
@@ -51,7 +51,7 @@ packages:
51
51
  - **Bare version** (`v5.2.1`, `5.2.1`, `1.0.0-rc.1`): the id is looked up in
52
52
  the official catalog — `package-catalog.json` in the `oats` repo, or the file
53
53
  named by `OATS_PACKAGE_CATALOG` — which supplies the repo url, the tag
54
- convention (`v5.2.1` or `oats-framework/v1.13.3`) and the payload path. An id
54
+ convention (`v5.2.1` or `oats-framework/v1.13.4`) and the payload path. An id
55
55
  the catalog does not know is `E_PACKAGE_MISSING` ("use `git:<repo>@<ref>` for
56
56
  a package outside the catalog"). The catalog is the reviewed official list
57
57
  ([official-catalog.md](official-catalog.md)) and the only way a
@@ -74,9 +74,9 @@ members:
74
74
  - git:github.com/acme/agents
75
75
  - git:github.com/acme/platform
76
76
  packages:
77
- oats.framework: v1.13.3
77
+ oats.framework: v1.13.4
78
78
  oats.okf: v5.2.1
79
- oats.aweb: v1.29.0
79
+ oats.aweb: v1.30.0
80
80
  teams:
81
81
  platform: { team: "platform:acme.aweb.ai", description: Platform engineering }
82
82
  defaults:
@@ -134,7 +134,7 @@ Declaring a package in the workspace's `packages:` is the trust decision
134
134
  ## `oats package add | remove`
135
135
 
136
136
  ```bash
137
- oats package add oats.aweb v1.29.0 # a catalog version
137
+ oats package add oats.aweb v1.30.0 # a catalog version
138
138
  oats package add acme.tools git:github.com/acme/tools@v0.4.0
139
139
  oats package remove acme.tools
140
140
  ```
@@ -353,11 +353,11 @@ A soul that names one of the package's capabilities with
353
353
  "policy": "docs/official-catalog.md",
354
354
  "packages": {
355
355
  "oats.okf": { "url": "https://github.com/awebai/oats-okf.git", "ref": "v5.2.1", "path": "oats-package" },
356
- "oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.13.3", "path": "oats-package" }
356
+ "oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.13.4", "path": "oats-package" }
357
357
  }
358
358
  }
359
359
  ```
360
360
 
361
- `ref` carries the tag convention: a workspace's `oats.framework: v1.13.3`
362
- resolves to tag `oats-framework/v1.13.3`. Resolving through the catalog never
361
+ `ref` carries the tag convention: a workspace's `oats.framework: v1.13.4`
362
+ resolves to tag `oats-framework/v1.13.4`. Resolving through the catalog never
363
363
  advances a lock by itself: `oats sync` does, and says so.
@@ -0,0 +1,183 @@
1
+ # OATS 0.66.0
2
+
3
+ Unreleased
4
+
5
+ ## Upgrade
6
+
7
+ - **Install the Desktop first and the CLI second,** as
8
+ [Upgrading](../upgrading.md) says: a 0.65 Desktop refuses a 0.66.0 CLI. The
9
+ 0.66.0 Desktop accepts OATS CLIs `>=0.26.0 <0.67.0`.
10
+
11
+ - **Two package moves:** the official catalog pins oats.framework 1.13.4 and
12
+ oats.aweb 1.30.0 (Provider updates, below). A deployment that pins them
13
+ takes them with `oats sync`, and only new spawns use them. Neither floor
14
+ changes.
15
+
16
+ - **`oats tui` moves its key file** to `~/.oats/config/tui.json` the first
17
+ time it starts (Changed, below). If you keep the file in a dotfiles
18
+ manager, point it at the new path first.
19
+
20
+ - **Coming from 0.61 or earlier:** do 0.62.0's Upgrade steps too (the capture
21
+ service's `oats setup`, once per user on each host, from that user's shell).
22
+
23
+ - **`oats server connect` needs `--dir`, inside a deployment too**
24
+ ([#1390](https://github.com/awebai/oats/issues/1390);
25
+ [Connect a machine](../servers.md#connect-a-machine)). The folder on the
26
+ host no longer defaults to `~/Agents/<this deployment's directory name>`:
27
+ only you know where the deployment goes there. A script that ran `connect`
28
+ without it now gets `E_BAD_ARGS` "--dir <path on the host> is required:
29
+ the folder on `<host>` for this deployment (absolute, or ~/… resolved
30
+ there)" before anything runs; add `--dir`. `--workspace-ref` still
31
+ defaults from the deployment, and existing registrations are unchanged.
32
+
33
+ ## Added
34
+
35
+ - **`oats tui` takes the OATS Desktop's Ctrl+Shift chords, where your
36
+ terminal lets them through** ([Chords](../tui.md#chords)): `Ctrl+Shift+K`
37
+ the palette, `Ctrl+Shift+P` a spawn, `Ctrl+Tab` and `Ctrl+Shift+Tab` the
38
+ next and previous tab, `Ctrl+Shift+W` close the terminal, `Ctrl+Shift+F`
39
+ the filter, `Ctrl+Shift+E` and `Ctrl+Shift+O` the splits. Each does what
40
+ the leader then a key does, from every focus, an agent's terminal too,
41
+ and never reaches the agent. They are extras: the leader stays the key
42
+ that always works, and the cheat sheet does not name them.
43
+ - **Only where the terminal says it can.** At start the TUI asks for the
44
+ kitty keyboard protocol (flags 1 and 4) and asks the terminal which flags
45
+ it has. Only when the terminal answers does it take the chords and list
46
+ them in the help, with the keys your terminal may take first (foot's
47
+ Ctrl+Shift+C, V, R, N, O, U, Z, X and Q). Without an answer everything
48
+ is as before. foot, Ghostty, kitty, Alacritty and WezTerm answer; VTE
49
+ terminals and Terminal.app do not. On macOS only `Ctrl+Tab` and
50
+ `Ctrl+Shift+Tab` are chords: the Desktop's hold ⌘, which a terminal
51
+ never passes on.
52
+ - **`Alt+O` and `Esc` then `o` are told apart exactly** under the
53
+ protocol, with no timing.
54
+ - **An agent gets the same bytes as before:** every key typed into its
55
+ terminal is turned back into the bytes it sends without the protocol,
56
+ and no tmux setting is changed. With a terminal that confirms flag 1
57
+ but not flag 4, Shift with Alt or Ctrl on a key that is not a letter
58
+ is typed as the US layout makes it.
59
+ - **The protocol is popped on every way out** and at a suspend, beside the
60
+ terminal modes the TUI already restores.
61
+
62
+ ## Changed
63
+
64
+ - **OATS Desktop's Add a machine dialog no longer suggests a folder**
65
+ ([#1390](https://github.com/awebai/oats/issues/1390)). **Folder on that
66
+ machine** starts empty and you have to fill it in. Its hint reads "A path on
67
+ that machine, starting with / or ~/". If you click **Add machine** with the
68
+ folder empty, the dialog says so beside the field and runs nothing. It used
69
+ to fill in `~/Agents/<deployment folder name>`. The Name default
70
+ (`<host>-<deployment folder name>`) is unchanged.
71
+
72
+ - **`oats deployments add` walks up to a regular `oats-local.yaml` only**
73
+ ([#1397](https://github.com/awebai/oats/issues/1397);
74
+ [This computer's deployments](../workspaces.md#this-computers-deployments)).
75
+ A directory or a link of that name is passed over, as a client passes it
76
+ over when it admits a deployment, instead of being listed and then shown
77
+ as `not-a-deployment`.
78
+ - **A deployment under a temporary directory is no longer listed
79
+ automatically** ([#1397](https://github.com/awebai/oats/issues/1397)). A
80
+ kernel command run in one (`os.tmpdir()`, `/tmp`, `/private/tmp` or
81
+ `/var/folders`, compared after realpath) leaves the list alone, so test
82
+ fixtures no longer fill it with rows that turn `missing`. Such a
83
+ deployment stays reachable: `oats deployments add`, `oats onboard` and a
84
+ client opening it still list it.
85
+
86
+ - **`oats tui` reads its key file from `~/.oats/config/tui.json`**
87
+ ([#1390](https://github.com/awebai/oats/issues/1390)), beside the kernel's
88
+ own files: `$OATS_HOME_DIR/config/tui.json` when `OATS_HOME_DIR` is set.
89
+ `XDG_CONFIG_HOME` is no longer read for it.
90
+ - **An existing file is moved for you** the first time the TUI starts: it
91
+ copies `~/.config/oats/tui.json` (or `$XDG_CONFIG_HOME/oats/tui.json`)
92
+ to the new path and renames the old file `tui.json.migrated`, beside
93
+ it. Nothing else changes.
94
+ - **If both files are there, the TUI refuses to start** with
95
+ `E_TUI_CONFIG`, naming both: copy what you need into
96
+ `~/.oats/config/tui.json`, then remove the old file.
97
+ - **If you keep `tui.json` in a dotfiles manager,** point it at
98
+ `~/.oats/config/tui.json`. A manager that puts the old file back makes
99
+ both files present, and the TUI refuses until you remove it.
100
+ - When the move can't be made (the old file is a link to nothing,
101
+ `tui.json.migrated` is already there, the file system has no hard links,
102
+ or a step fails), the TUI says why and stops: move the file yourself.
103
+ See [OATS TUI](../tui.md#the-move-from-configoats).
104
+
105
+ - **OATS Desktop accepts an `oats` CLI 0.66.x.** Its band is now
106
+ `>=0.26.0 <0.67.0`. 0.66 adds no new gate on the band: the Desktop's Add a
107
+ machine already passes the `--dir` that `oats server connect` now requires.
108
+
109
+ - **A new workspace gets messaging, a team and a first developer in its first
110
+ commit, with no pull requests and no API key.** The `oats-getting-started`
111
+ skill asks for an aweb username in its one round of questions, writes the
112
+ workspace with `oats.aweb`, a team `default:<username>.aweb.ai`,
113
+ `defaultTeam` and a developer soul beside the setup expert, then signs up
114
+ the account with `oats aweb setup --username` before the spawn. Later
115
+ changes follow oats.setup's push rule (the next entry). The skill also runs `gh auth setup-git` when gh is
116
+ already logged in, so the first push and `oats onboard` no longer fail with
117
+ "could not read Username". The README's Start here tells a coding agent
118
+ exactly what to download and follow.
119
+
120
+ - **The setup soul that the `oats-getting-started` skill writes leaves when
121
+ to push to `oats.setup`.** Its `AGENTS.md` states no push rule of its own.
122
+ From `oats.setup` 2.8.3 (oats.framework 1.13.4), the setup expert checks
123
+ before each push (`/oats-workspace-config`, "Change a shared file"): it
124
+ pushes straight to the default branch only where nobody else can push and
125
+ nothing guards that branch, and to a member repository only on the
126
+ person's yes; otherwise it opens a pull request. An older `oats.setup`
127
+ always opens one ([#1314](https://github.com/awebai/oats/issues/1314)).
128
+
129
+ ## Fixed
130
+
131
+ - Capture setup now shares one checked publisher for hooks, service definitions
132
+ and pending activation markers: it syncs file contents before rename, then
133
+ the containing directory, and syncs newly created parent entries in order.
134
+ Required sync failures exit nonzero; failures after publication name the
135
+ affected target and stage without claiming rollback or established durability.
136
+
137
+ ## Provider updates
138
+
139
+ - **oats.framework 1.13.4: oats.setup 2.8.3.** Text only: its floor
140
+ (`compatibility.oats`) does not change.
141
+ - **Straight pushes to a repository only the person can push to.** The
142
+ briefing's rule for shared files was "only by pull request".
143
+ `/oats-workspace-config`'s "Change a shared file" now has two routes. A
144
+ commit goes straight to a repository's default branch, the workspace's
145
+ host or a member repository alike, only when checks right before the
146
+ push show that the person alone can push to it and nothing guards the
147
+ branch:
148
+ - they are its admin and its only collaborator with push access; for an
149
+ organization's repository, an active member and its only owner;
150
+ - no deploy key can write;
151
+ - no branch protection or ruleset guards the default branch (a plan
152
+ without rulesets counts as unguarded).
153
+
154
+ For the host, the setup expert then pushes and tells them what changed.
155
+ For a member repository, it first shows them the commit and says that
156
+ the push runs that repository's push-triggered CI and deploys, and it
157
+ pushes only on their yes. Otherwise the change is a pull request, and a
158
+ refused push never takes another route. The briefing,
159
+ `/oats-setup-expert`, `/oats-package-pins`, `/oats-teams`,
160
+ `/oats-automations` and `/oats-setup-model` follow it
161
+ ([#1314](https://github.com/awebai/oats/issues/1314)).
162
+ - **`/oats-setup-model` on a capture setup that failed after
163
+ publication.** When the setup summary says that publication may have
164
+ occurred but durability was not established, inspect the named target
165
+ and stage before rerunning, and keep that evidence. A sync or close
166
+ failure after the rename does not mean that the old file was restored
167
+ ([#1340](https://github.com/awebai/oats/issues/1340)).
168
+
169
+ - **oats.aweb 1.30.0: Codex readiness from the kernel's launch record.** The
170
+ catalog and this workspace pin `oats.aweb: v1.30.0`
171
+ ([#1345](https://github.com/awebai/oats/issues/1345)).
172
+ - Readiness takes a home's runtime from the kernel's recorded
173
+ `instance.json` `launch.harness` (or top-level `harness`), not from
174
+ provider metadata. A home recorded as Codex needs the host wake broker:
175
+ a missing Codex target or primary stream reports `wake-stream-missing`.
176
+ Malformed or inconsistent kernel fields report
177
+ `receive-record-unavailable`.
178
+ - A malformed `status.updated_at` from `aw wake status` reports
179
+ `wake-status-timestamp-unknown`, naming the aw client and daemon
180
+ versions, instead of `wake-status-stale`.
181
+ - The floors are unchanged (OATS >=0.52.0, aw >=1.36.33). A deployment
182
+ gets it by pinning `oats.aweb: v1.30.0` and running `oats sync`; only
183
+ new spawns use it.
package/docs/servers.md CHANGED
@@ -71,7 +71,7 @@ which is where a [macOS keychain](#git-on-a-macos-host) problem shows up.
71
71
  ## Connect a machine
72
72
 
73
73
  ```bash
74
- oats server connect altair-aweb --ssh altair --path /opt/homebrew/bin --install-oats
74
+ oats server connect altair-aweb --ssh altair --dir '~/acme' --path /opt/homebrew/bin --install-oats
75
75
  ```
76
76
 
77
77
  Run from a deployment, `server connect` puts that deployment's workspace on
@@ -81,8 +81,8 @@ missing, so after a human step you run the same command again.
81
81
 
82
82
  | Option | Default |
83
83
  |---|---|
84
+ | `--dir <path>` | none, inside a deployment too: the folder on the host for this deployment, absolute or `~/…` (resolved by the host). Without it: `E_BAD_ARGS` "--dir <path on the host> is required: the folder on `<host>` for this deployment (absolute, or ~/… resolved there)". A registration made before it was required is unchanged |
84
85
  | `--workspace-ref <ref>` | this deployment's `oats-local.yaml` `workspace:` |
85
- | `--dir <path>` | `~/Agents/<this deployment's directory name>`; absolute or `~/…`, resolved by the host |
86
86
  | `--oats <path>`, `--path <dirs>`, `--label <text>` | as for `server add`; `--path` is where the host finds `npm`, `oats` and the harnesses |
87
87
  | `--install-oats` | off: a missing or older OATS is a human step |
88
88
  | `--replace` | off: an id registered for another host or directory is refused |