@awebai/oats 0.66.0 → 0.67.1

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 (65) hide show
  1. package/bin/oats.mjs +66 -13
  2. package/docs/capabilities.md +4 -4
  3. package/docs/capability-manifest.schema.json +1 -1
  4. package/docs/desktop-cli-api.md +217 -6
  5. package/docs/desktop.md +101 -22
  6. package/docs/implementation.md +6 -5
  7. package/docs/official-catalog.md +1 -1
  8. package/docs/packages.md +5 -5
  9. package/docs/release-lane.md +16 -0
  10. package/docs/release-notes/v0.67.0.md +366 -0
  11. package/docs/release-notes/v0.67.1.md +64 -0
  12. package/docs/servers.md +3 -2
  13. package/docs/souls-and-instances.md +20 -3
  14. package/docs/tui.md +570 -176
  15. package/docs/upgrading.md +107 -25
  16. package/docs/workspaces.md +1 -1
  17. package/lib/capability-contract.mjs +2 -2
  18. package/lib/core.mjs +126 -54
  19. package/lib/instance-color.mjs +58 -0
  20. package/lib/instance-inspect.mjs +107 -23
  21. package/lib/instance-lifecycle.mjs +21 -1
  22. package/lib/instance-naming.mjs +187 -0
  23. package/lib/instance-resolution.mjs +5 -1
  24. package/lib/materialize.mjs +62 -11
  25. package/lib/servers.mjs +15 -6
  26. package/lib/soul-composition.mjs +7 -3
  27. package/package-catalog.json +1 -1
  28. package/package.json +1 -1
  29. package/packages/client/cli-adapter.mjs +37 -5
  30. package/packages/client/cli-locator.mjs +2 -2
  31. package/packages/client/composed-gate.mjs +10 -2
  32. package/packages/client/deployment-data.mjs +5 -0
  33. package/packages/client/deployment-identity.mjs +40 -0
  34. package/packages/client/deployment-panel.mjs +3 -1
  35. package/packages/client/inspect-boundary.mjs +11 -7
  36. package/packages/client/inspect-cache.mjs +2 -2
  37. package/packages/client/instance-name.mjs +28 -0
  38. package/packages/client/instance-presentation.mjs +11 -0
  39. package/packages/client/keymap.mjs +85 -24
  40. package/packages/client/keys-file.mjs +122 -0
  41. package/packages/client/own-codes.mjs +4 -2
  42. package/packages/client/panel-views.mjs +62 -9
  43. package/packages/client/spawn-naming.mjs +31 -0
  44. package/packages/client/spawn-preview-cli.mjs +22 -7
  45. package/packages/client/spawn-preview-contract.mjs +24 -0
  46. package/packages/client/spawn-preview-facts.mjs +8 -4
  47. package/packages/client/spawn-preview.mjs +47 -2
  48. package/packages/tui/README.md +3 -3
  49. package/packages/tui/lib/actions.mjs +57 -14
  50. package/packages/tui/lib/client.mjs +8 -4
  51. package/packages/tui/lib/config.mjs +50 -9
  52. package/packages/tui/lib/main.mjs +40 -13
  53. package/packages/tui/lib/model.mjs +167 -63
  54. package/packages/tui/lib/read.mjs +53 -1
  55. package/packages/tui/lib/store.mjs +148 -54
  56. package/packages/tui/lib/term/keys.mjs +19 -5
  57. package/packages/tui/lib/term/kitty.mjs +36 -11
  58. package/packages/tui/lib/term/through.mjs +61 -28
  59. package/packages/tui/lib/views/frame.mjs +158 -79
  60. package/packages/tui/lib/views/help.mjs +109 -26
  61. package/packages/tui/lib/views/instances.mjs +59 -20
  62. package/packages/tui/lib/views/palette.mjs +14 -4
  63. package/packages/tui/lib/views/souls.mjs +2 -2
  64. package/packages/tui/lib/views/switcher.mjs +6 -1
  65. package/skills/oats-getting-started/SKILL.md +13 -8
package/docs/desktop.md CHANGED
@@ -201,28 +201,46 @@ repository at a time; "N of M shown" appears while a pill or the search
201
201
  narrows the list.
202
202
 
203
203
  A soul's page (open a soul from **Workspace › Souls**) ends with
204
- **Instructions**, what its instances are told: the soul's own `AGENTS.md`,
205
- read like a capability's injected instructions (a navigation tree on the left,
206
- the file on the right), at its path in the soul's repository. It comes from the
207
- same inspection as the rest of the page, so **Refresh** re-reads it and keeps
208
- what you had open, and your place in it. A file over 200,000 characters is
209
- shown cut, and says so.
210
-
211
- With an OATS that composes a soul's instructions (0.46.0 and later), the tree
212
- also has **Instance**: its **AGENTS.md**, *after spawn, with injects*, is the
213
- file a spawn of this soul on this computer would write, with one entry per part
214
- (the soul's own text, then each block OATS and the soul's capabilities add, in
215
- order). Open it to read the whole document; choose a part to go to it. Each
216
- part's header says where it comes from (**From this soul** or **Injected by …**)
217
- and names its file; a capability's part has **Open capability**, and **Copy
218
- composed AGENTS.md** copies the exact file. When the soul can't be composed
219
- here, the group says so and the problem shows at the top of the page. For a
220
- soul on another machine (a server workspace), the page shows the composed file
221
- when that machine supports it: this computer's OATS must be 0.49.0 or later, to
222
- pass on what each server reports about itself, and the server's OATS must say
223
- it composes a soul's instructions (0.49.0 and later report this). Until a
224
- server reports it (an older server, or one whose last read failed), its soul
225
- pages show only the soul's own `AGENTS.md`, with no **Instance** group.
204
+ **Instructions**, what its instances are told, read like a capability's
205
+ injected instructions (a navigation tree on the left, the file on the right).
206
+ The tree has two sections, a rule between them:
207
+
208
+ - **Defined in this soul**: its own `AGENTS.md`, at its path in the soul's
209
+ repository, and, with an OATS that reports a soul's skills, its **Skills**.
210
+ Open a skill to list its files; a file opens in the reader under its
211
+ repository path.
212
+ - **Composed for an instance**: what an instance of this soul gets. Its
213
+ **AGENTS.md**, *after spawn, with injects*, and its **Skills**, each saying
214
+ where it comes from. With an OATS that lists every skill a spawn gives the
215
+ instance (0.67.0 and later), the Skills are that list: the soul's own, each
216
+ **From this soul**, and the ones its capabilities add, each **From** the
217
+ capability. A capability's skill file opens under its place in the instance
218
+ home (`.oats/modules/<capability>/…`), with **Open capability** above it. With
219
+ an older OATS the skills listed are the soul's own, and a note says that the
220
+ skills capabilities add are listed by a newer OATS. For a soul on another
221
+ machine, the server's OATS must list them too, as for the composed
222
+ AGENTS.md below.
223
+
224
+ Both come from the same inspection as the rest of the page, so **Refresh**
225
+ re-reads them and keeps what you had open, and your place in it. A file over
226
+ 200,000 characters is shown cut, and says so.
227
+
228
+ The composed **AGENTS.md** needs an OATS that composes a soul's instructions
229
+ (0.46.0 and later). It is the file a spawn of this soul on this computer would
230
+ write, with one entry per part (the soul's own text, then each block OATS and
231
+ the soul's capabilities add, in order). Open it to read the whole document;
232
+ choose a part to go to it. Each part's header says where it comes from
233
+ (**From this soul** or **Injected by …**) and names its file; a capability's
234
+ part has **Open capability**, and **Copy composed AGENTS.md** copies the exact
235
+ file. When the soul can't be composed here, the section says so and the problem
236
+ shows at the top of the page. For a soul on another machine (a server
237
+ workspace), the page shows the composed file when that machine supports it:
238
+ this computer's OATS must be 0.49.0 or later, to pass on what each server
239
+ reports about itself, and the server's OATS must say it composes a soul's
240
+ instructions (0.49.0 and later report this). Until a server reports it (an
241
+ older server, or one whose last read failed), its soul pages show no composed
242
+ **AGENTS.md**. A soul's skills follow the same rule, with the server's OATS
243
+ saying it reports them.
226
244
 
227
245
  The **Spawn** dialog's left column, **What will be created**, starts with the
228
246
  new instance's name and its home. Then come where it works, its harness and
@@ -230,6 +248,44 @@ model (with where that choice came from), its default team and the teams it may
230
248
  also join, and its relationship when it has one. Under them are its core
231
249
  capabilities and its other capabilities.
232
250
 
251
+ The dialog's first field is the **Opening instruction**, and the dialog opens
252
+ with the cursor in it (after a restored instruction's text). In a narrow window,
253
+ **What will be created** comes after the form's last field, above **Spawn**:
254
+ scroll down with the fields to read it.
255
+
256
+ The dialog's last field before **Developer settings** is **Name · optional**.
257
+ Left empty, the kernel numbers the new instance (`<soul>-<n>`). A name you type
258
+ is used in lowercase and gets the soul's role, the last word of the soul's
259
+ name, as its suffix:
260
+ `desktop-improvements` for `oats-desktop-expert` becomes
261
+ `desktop-improvements-expert`. A name that already ends in the role, or is
262
+ the role, stays as typed. The line under the field shows the final name, and a
263
+ name that is too long, invalid or already taken is explained there. With an
264
+ OATS older than 0.26.0, which can't take an exact name, and for a spawn on a
265
+ server, what you type is a purpose instead: the instance is named
266
+ `<soul>-<purpose>`, and the field shows that prefix.
267
+
268
+ **Named from its task.** When the installed OATS can suggest names (feature
269
+ `spawn-suggest-name`), the help under an empty Name reads "Left empty, the
270
+ instance is named from its task." Once the Opening instruction holds at
271
+ least three words and you stop typing for about a second and a half, the
272
+ Desktop asks OATS for a name. The soul's own harness reads the instruction
273
+ and replies with a short name for the work, and the role is added as its
274
+ suffix. The name shows as the field's placeholder ("will be named
275
+ release-notes-manager"), on the line under the field ("(from the task)") and
276
+ in **What will be created**. It belongs to the instruction it was made for:
277
+ when you change the instruction it goes, until the next pause. Typing in Name
278
+ replaces it and stops suggestions for the rest of the dialog, even if you
279
+ empty the field again. Press **Spawn** with Name empty and no name yet, and the
280
+ dialog says **Naming…** and asks once, however short the instruction. When OATS
281
+ can't name it, the instance is numbered and a notification says why, for
282
+ example "Named oats-desktop-expert-3: naming took longer than 20 seconds."
283
+ That happens when there is no instruction, when the harness doesn't suggest
284
+ names (Codex), when there is no answer within 20 seconds, when the harness
285
+ couldn't be asked, and when its reply wasn't a name. Each request is a call
286
+ to the harness's model: nothing is asked before you type, nothing runs on a
287
+ timer, and a spawn on a server is not named this way.
288
+
233
289
  When capabilities set up the new worktree (OATS 0.49.0 and later), **Setup**
234
290
  names them, in the order they run, and says this can take several minutes. Such
235
291
  a spawn may run for a long time: its roster row reads **Setting up worktree…**
@@ -545,6 +601,29 @@ right of its parent, and related instances are grouped together. Siblings are
545
601
  joined by a dotted line through their dots. A parent's line to its children
546
602
  runs just to the right of the dotted line, so the two never merge.
547
603
 
604
+ ## An instance's colour
605
+
606
+ An instance can have a colour, one of the soul palette's six (Sand, Sage,
607
+ Slate, Mauve, Clay, Olive). Its dot shows it wherever the instance is listed:
608
+ the sidebar, its terminal tab, the command palette and the overview. A running
609
+ instance's dot is filled with the colour, a stopped one's is a ring in it. An
610
+ instance whose state is unknown keeps the warning dot, and one without a colour
611
+ looks as before. The shape says the state, never the colour alone.
612
+
613
+ To set it, open **Instance: name and colour…** from the command palette, or
614
+ press Ctrl+Alt+R (⌥⌘R on macOS). It acts on the instance of the terminal you
615
+ are in, else the focused sidebar row, else the active terminal tab's instance.
616
+ The dialog shows the instance's name, which can't be changed yet, and the
617
+ colours as buttons: **None** and the six. Arrow keys move between them; Enter,
618
+ Space or a click sets the colour at once, and **Saved.** or OATS's refusal
619
+ appears under the title. The dialog stays open until you close it.
620
+
621
+ The colour is the instance's own, kept in its home by OATS
622
+ (`oats instance color`). Setting one needs OATS 0.67.0 or later on this
623
+ computer, and for an instance on a server, on that server too; until then the
624
+ buttons are disabled and the dialog says which is missing. An instance whose
625
+ home is being spawned or retired can't be given a colour meanwhile.
626
+
548
627
  ## Identity marks and harness badges
549
628
 
550
629
  Souls, capabilities and workspaces carry a coloured two-letter mark beside
@@ -80,7 +80,7 @@ and the rules its tests pin.
80
80
  | `souls/` | this repository's own souls (a workspace member) |
81
81
  | `docs/` | the reference pages, schemas, design records and release notes |
82
82
  | `packages/` | the pi adapter, the Desktop, the terminal client (`tui/`), the readers both clients share (`client/`), the turn-record package and experiments |
83
- | `scripts/` | the test runner (`run-tests.mjs`), its reporter of unasserted warnings and the preload that gives each test file a temporary directory of its own, the session-inheritance check (`test-session-inheritance.mjs`), validators, packaging checks, the release lane, the assembly of release-notes entries, and the hand-started named test runs on macOS and Linux (`named-test-run.mjs`, with `macos-tests.mjs` and `linux-tests.mjs`: [named test runs](named-test-runs.md)) |
83
+ | `scripts/` | the test runner (`run-tests.mjs`), its reporter of unasserted warnings and the preload that gives each test file a temporary directory of its own, the session-inheritance check (`test-session-inheritance.mjs`), validators, packaging checks, the release lane, the assembly of release-notes entries, and the hand-started named test runs on macOS and Linux (`named-test-run.mjs`, with `macos-tests.mjs` and `linux-tests.mjs`: [named test runs](named-test-runs.md)), and the naming call's isolation proof (`naming-isolation-proof.mjs`, run by hand against real harnesses) |
84
84
  | `test/` | the kernel and CLI suites, with their fixtures |
85
85
 
86
86
  ## Kernel modules
@@ -92,11 +92,12 @@ and the rules its tests pin.
92
92
  | `workspace.mjs` | workspace, membership and soul files; discovery |
93
93
  | `resolve.mjs` | a soul's resolution: capabilities, slots, provenance |
94
94
  | `packages.mjs` | `packages:`, the catalog, `oats sync`, `oats-lock.json` |
95
- | `capability-show.mjs` | `oats capabilities show`: one catalog row's inject and skill files, read at its commit. Its text rules (`decodeText`, `skillDocDescription`, the limits) are also the rules of `inspect --soul --skills` (`instance-inspect.mjs` `soulSkills`), which reads a soul copy's own skills locally |
96
- | `materialize.mjs` | copying modules into a home and composing it |
95
+ | `capability-show.mjs` | `oats capabilities show`: one catalog row's inject and skill files, read at its commit. Its text rules (`decodeText`, `skillDocDescription`, the limits) are also the rules of `inspect --soul --skills` (`instance-inspect.mjs` `soulSkills`), which reads a soul copy's own skills locally, and of `--composed-skills` (`composedSkillsIn`), which adds the capability skills of the scratch composition |
96
+ | `materialize.mjs` | copying modules into a home and composing it; `moduleSkills` is the one rule for which skills a module gives, read over the fetched tree, or over a remote listing for the spawn preview (`plannedModuleSkills`) |
97
97
  | `core.mjs` | spawn, retire, sessions, hooks, launch recipes, instance metadata. A home's record (`instance.json`) is read with `readHomeRecord`, which never throws: a record, an absent one, or one that is there and cannot be read, with the reason. Code that walks other homes (the listing, a retire's lineage repair) uses it, so that one home's record decides only for that home; `identifiedHomeRecord` is the one refusal (`E_UNIDENTIFIED_INSTANCE_HOME`) a lifecycle verb makes when it has resolved its home: `resolveRetireHome`, `startInstanceSession`, and `resolveTarget` in `instance-lifecycle.mjs` for the stop and retire plans. A plan reads its own home's record with `targetRecord` (the same refusal) and any other home's with `otherRecord` (absent or unreadable: nobody's parent or child) |
98
98
  | `instruction-composition.mjs` | the generated `AGENTS.md`; `renderInstructionParts` is the span-reporting renderer (`renderInstructionText` is its text) |
99
- | `soul-composition.mjs` | the instructions a spawn of a soul would write, composed without a spawn (kernel half + materialize into a scratch home): the one path behind `doctor --soul` and `inspect --soul --instructions` |
99
+ | `soul-composition.mjs` | the instructions a spawn of a soul would write, composed without a spawn (kernel half + materialize into a scratch home): the one path behind `doctor --soul`, `inspect --soul --instructions` and `--composed-skills` (its `inScratch` reads the scratch home before it is removed, so the two flags share one materialization) |
100
+ | `instance-naming.mjs` | the suggested instance name of `spawn --preview --suggest-name`: the prompt, the soul's role (`soulRole`, the clients' rule), the name built from a reply, each harness's proven naming call (`NAMING_CALLS`) and the isolated call itself; driven by `core.mjs` `spawnBody`, after the preview's harness checks, where a suggested name is then placed as `--name` would place it. The test seam `OATS_TEST_NAMING_TIMEOUT_MS` shortens the call's 20 s limit |
100
101
  | `doctor-capture.mjs` | one fixed bounded package health child for deployment doctor, excluded from `--soul`; package-owned envelope validation and existing warning-row mapping. No kernel status/DB/freshness parser. Command failures become `capture-health-unavailable`; see [the package boundary](../packages/record/docs/capture-service.md#kernel-doctor-delegation) |
101
102
  | `teams.mjs`, `teams-verbs.mjs` | the team model and the `oats teams` verbs |
102
103
  | `local-edit.mjs` | the one way a verb rewrites `oats-local.yaml` in place (`editLocal`): the file as it is now, the deployment's local lock, compare-and-swap, the local schema and the caller's check before the rename, and the permission bits of the file it replaces on the new one (a link at that path is replaced by a regular file with its target's bits, and the target is not written). Every kernel command that rewrites that file writes through it (`grep editLocal` lists them; this row does not), and a new writer does too, so that no two drop each other's change. An edit changes the parsed document, which is then rendered, or returns the text to write when the command has a writer of its own for its block (`oats launch-config set\|remove`, whose write leaves every byte outside `launch-configs` as it was) |
@@ -110,7 +111,7 @@ and the rules its tests pin.
110
111
  | `schedule-command.mjs`, `schedule-command-child.mjs` | synchronous scheduler adapter and asynchronous child supervisor: bounded output, TERM/KILL escalation and observed exit; no changes to synchronous tick/lock callbacks |
111
112
  | `operator-dispatch.mjs` | capability commands run from a deployment, and its module store |
112
113
  | `operator-coverage.mjs` | whether a soul the workspace offers composes `oats.setup`, for the workspace and each team (readiness and doctor warnings), and the cache-only remote offline doctor resolves through |
113
- | `instance-*.mjs` | inspection, lifecycle, events and Git views of an instance |
114
+ | `instance-*.mjs` | inspection, lifecycle, events and Git views of an instance; `instance-color.mjs` is an instance's colour, its palette (pinned equal to `packages/client/soul-colors.mjs`) and its home record, which every reader goes through |
114
115
  | `worktree.mjs` | `oats worktree add\|remove`: an instance's extra trees (`.work-<purpose>`), their records (`.oats/trees/`), argument checks before any write, and the rollback of an interrupted add |
115
116
  | `errors.mjs` | `oatsError`, and the door of the lifecycle verbs: `isKernelCode` (the shape of a kernel code, `^E_[A-Z0-9_]+$`, never a list of codes), `kernelCode`, `asKernelError` and `errorCause`. An answer of `oats retire`, `oats instance stop`, `oats session` and `oats worktree` carries a kernel code, or one of the two names every command answers as they are (`OWN_NAME_FAILURES`: `unsafe-config-key`, `unsafe-config-value`), and no other: `isAnswerCode` is what the door and its wrappers keep, `isKernelCode` stays the test of the shape. An error of the system's or of Node's, a refusal written as a plain `Error` without a code, and a defect (`isDefect`: a `TypeError` and its like without a code, or a thrown value that is no `Error`), is wrapped at the boundary (`bin/oats.mjs` `lifecycleFail`; in a retire, `core.mjs` `retireClaimed`, which also says what the retire had done by then) and its own code goes to `details.cause` (a defect's name does; a plain `Error` without a code has no cause, and is answered with the general code and its message alone, which is what an ordinary refusal of `tmux`, `git` or the kernel itself must read as). New code that answers an error tests the shape with these, never `e.code \|\| "E_…"`: a system error has a `code` too. Whoever ends an error's way up prints the stack of a defect with `reportDefect`: the door, and any code that turns a caught error into a row of results (a stop's `results[]`, a retire's `childrenStopped[]`), after which nobody else can. Two more rules of the lifecycle verbs live here. **`lifecycleBusy(holder, said, remedy, details)` is the only way `E_LIFECYCLE_BUSY` is made** (`test/lifecycle-busy-holder.test.mjs` scans `lib/` and `bin/` for any other): it sets `details.holder` (`BUSY_HOLDERS`: `"running"` only where the kernel established that the other command is alive, `"unknown"`, `"none"`) and refuses to build an `"unknown"` or `"none"` answer without the step that ends it. **`BEFORE_EFFECT_CODES` lists, per verb, the codes that verb answers only before any effect**; `afterFirstEffect` turns a listed code raised after a verb's first effect into a defect (`E_LIFECYCLE_FAILED`, `cause.name: "LateRefusal"`), and is called at the one place of each verb that knows how far it got (`core.mjs` `retireFailure`, from `at.phase`; `instance-lifecycle.mjs` `applyStop`, from whether a target's stop began). A code may join the list only when every place that raises it in that verb is before the first effect; a place found after it gets a code of its own, never the net |
116
117
  | `claim.mjs` | the claim: one file naming, by pid and start time, the process doing something that happens once at a time; taken over when its holder is verifiably gone, never when that cannot be read. Synchronous. Held by `oats worktree add\|remove` per purpose (`worktree.mjs`), and per home by `oats retire` and `oats instance stop --apply` (`core.mjs` `claimHomeFor`: the one way a verb takes a home's lifecycle claim; the record names the holder's verb, `action`, from the instant the file exists, through the `facts` option of `acquireClaim`). A verb that only reads the home's claim (`oats worktree add`; a stop plan's `retiring` and `stopPending`) uses `homeClaimHolder` or `refuseBesideRetire`. The refusals of every pair (arriving verb, holder's verb) are built in one place, `core.mjs` `lifecycleClaimRefusals`; the pair table of `docs/desktop-cli-api.md` is walked by `test/lifecycle-pair-table.test.mjs`. A new verb that must not run beside a retire takes the claim through `claimHomeFor`, joins `CLAIM_VERBS` and adds its row and column there. Its loop has one rule: every pass that does not take the claim falls through one check of its time and one pause, so no state of the path makes it spin. Each caller words the refusals (`busy`, `unreadableClaim`, `cannotTakeOver`, `heldAgain`, `ownStartUnreadable`), and is handed with each what the acquisition's takeovers ended before it (`ended`): it writes "nothing else was done" then, and the answer is `E_LIFECYCLE_FAILED`, what was ended first (`errors.mjs` `nothingAfter`, `afterEndedSteps`; `lifecycleBusy` takes `ended`). No message is rewritten after it was made. A claim is read back as whatever is in its file, which others than its writer can write, so no text of it enters an answer: a refusal names the holder through `shownHolder` (its pid, time and start, each only in the shape the kernel writes) and `core.mjs` `claimAction` (one of `CLAIM_VERBS`, the list `claimHomeFor` accepts). A claim that could not be WRITTEN is marked at the write that failed (`claimWrite`: the claim's directory, its private file, its link, and the same of a takeover's own claim) for the system's code as it was thrown there, one of `CLAIM_UNWRITABLE_CODES`; the mark travels on the refusal (`unwritableCode`), and an answer made after a takeover ended something carries none. One caller reads it, `claimHomeFor` with the option `READ_CLAIM_WHEN_UNWRITABLE`, which a stop apply passes and nobody else: it then reads the claim where it would have taken it (`claimUnheld`: nobody, or the refusal the taking would have given, from the same builder) and answers a holding without a claim, whose `look()` makes that read again. No caller tells that failure from another by an answer's code, words or `details.cause`: a defect and a claim that could not be removed are `E_LIFECYCLE_FAILED` too |
@@ -9,7 +9,7 @@ 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.4` (this repository) | `oats.core`, `oats.setup`, `oats.support`, `oats.knowledge-theory` | `knowledge-theory-expert` |
12
+ | `oats.framework` | `oats-framework/v1.13.5` (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
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` |
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.4`) and the payload path. An id
54
+ convention (`v5.2.1` or `oats-framework/v1.13.5`) 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,7 +74,7 @@ members:
74
74
  - git:github.com/acme/agents
75
75
  - git:github.com/acme/platform
76
76
  packages:
77
- oats.framework: v1.13.4
77
+ oats.framework: v1.13.5
78
78
  oats.okf: v5.2.1
79
79
  oats.aweb: v1.30.0
80
80
  teams:
@@ -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.4", "path": "oats-package" }
356
+ "oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.13.5", "path": "oats-package" }
357
357
  }
358
358
  }
359
359
  ```
360
360
 
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
361
+ `ref` carries the tag convention: a workspace's `oats.framework: v1.13.5`
362
+ resolves to tag `oats-framework/v1.13.5`. Resolving through the catalog never
363
363
  advances a lock by itself: `oats sync` does, and says so.
@@ -357,6 +357,22 @@ node scripts/assemble-release-notes.mjs --tag v0.54.0
357
357
 
358
358
  No entry file writes this line: only the tag owner knows the release's
359
359
  version when the notes are assembled.
360
+ - **The same pull request updates "Upgrading to the latest version"**, the
361
+ section [Upgrading](upgrading.md) opens with: the version being tagged in
362
+ each place the section names it (the latest version, its notes, the
363
+ Desktop and the CLI install), and the CLIs that version's Desktop accepts,
364
+ up to its next minor (`ACCEPT_RANGE` in `packages/client/cli-locator.mjs`
365
+ once the release plan has moved it). The page
366
+ states only this band; the earlier ones stay in their notes. When the
367
+ release's Upgrade section asks for more than the page's steps, the order
368
+ of the Desktop and the CLI and an optional package pin, the pull request
369
+ also adds the release's entry at the top of "Coming from an older
370
+ version", one line that links its notes.
371
+ `test/release-packaging.test.mjs` checks that the section names the
372
+ version the manifests carry and no other, and that the page's only band
373
+ is that version's Desktop's. The oats.setup skill `oats-upgrade` reads
374
+ this page at the release's tag, so what the tag carries is what an upgrade
375
+ follows.
360
376
  - **A tag is refused while anything is under `docs/release-notes/next/`:** by
361
377
  the `build-and-test` job of `release.yml` and by `release-lane.mjs build`,
362
378
  each right after its notes-file gate and before anything is built. Each
@@ -0,0 +1,366 @@
1
+ # OATS 0.67.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.66 Desktop refuses a 0.67.0 CLI. The
9
+ 0.67.0 Desktop accepts OATS CLIs `>=0.26.0 <0.68.0`.
10
+
11
+ - **Coming from 0.65 or earlier:** do 0.66.0's Upgrade steps too (`oats
12
+ tui`'s key file moves to `~/.oats/config/tui.json`, and `oats server
13
+ connect` needs `--dir`), and 0.62.0's when coming from 0.61 or earlier.
14
+
15
+ - **One package move:** the official catalog pins oats.framework 1.13.5
16
+ (Provider updates, below). A deployment that pins it takes it with `oats
17
+ sync`, and only new spawns use it. No floor changes.
18
+
19
+ - **The leader moves to Ctrl+X** in OATS Desktop and in `oats tui`, on every
20
+ platform (Changed, below). A Desktop rebind of the leader and an
21
+ `open.detachKey` in `tui.json` are kept. To keep Alt+O or ⌃\, bind it
22
+ again: `"open": {"detachKey": "M-o"}` (or `"C-\\"`) in `tui.json`, the
23
+ shortcuts editor in the Desktop. **A `tui.json` that gives `ctrl+x` to an
24
+ action and names no leader stops `oats tui` from starting:** its line on
25
+ stderr names the action; give that action another key, or name a leader
26
+ in `open.detachKey` ([Change the keys](../tui.md#change-the-keys-tuijson)).
27
+
28
+ - **The shortcuts move on Linux and Windows** (Changed, below): the shared
29
+ chords are Ctrl+Alt now, not Ctrl+Shift, in OATS Desktop as in `oats tui`.
30
+ A shortcut you rebound in 0.66 is kept. If your terminal passes Ctrl+Shift
31
+ apart from Ctrl (foot, Alacritty), choose the Ctrl+Shift option instead
32
+ (Added, below). The Alt+Shift arrows no longer reach an agent in its
33
+ terminal.
34
+
35
+ ## Added
36
+
37
+ - **An instance has a colour** (feature `instance-color`, awebai/oats#1421).
38
+ `oats instance color <instance> (<colour> | --clear)` sets or clears it,
39
+ from the palette `sand`, `sage`, `slate`, `mauve`, `clay`, `olive`; it is
40
+ addressed as `oats instance stop` addresses an instance, and routed with
41
+ `--server`. The colour is presentation only: anyone may change it, and it
42
+ is never an address. It is kept in the home's own record,
43
+ `.oats-color.json`, which a start or restart never rewrites and a retire
44
+ does not count as a change to the home. `oats status --json` rows,
45
+ `oats server roster --json` rows and `oats inspect --home` carry `color`
46
+ ([An instance's colour](../desktop-cli-api.md#an-instances-colour-oats-instance-color)).
47
+
48
+ - **`oats inspect --soul <soul> --composed-skills` lists every skill a spawn
49
+ of the soul gives its instance** (feature `soul-composed-skills`,
50
+ awebai/oats#1421): its own skills and each capability's, each with its
51
+ `source` (`soul` or `module:<capability>`) and each file's text, from the
52
+ same scratch composition as `--instructions`. A collision a spawn would
53
+ refuse makes the field `null` with spawn's own message. It is opt-in, takes
54
+ `--soul` only, and a routed host without the feature refuses it
55
+ ([`oats inspect`](../desktop-cli-api.md#oats-inspect---home-----soul----dir----json--operationsapi-2)).
56
+
57
+ - **`oats spawn <soul> --preview --suggest-name` names the instance from its
58
+ task** (feature `spawn-suggest-name`, awebai/oats#1421). The soul's own
59
+ harness gives a few descriptive words in one call, and the preview answers
60
+ for `--name <descriptive>-<role>`, with the same decision an apply with
61
+ `--expect-decision` matches. The call starts none of the user's MCP
62
+ servers, hooks, plugins or extensions, and no tool on either harness: the
63
+ prompt goes on stdin, from an empty temporary directory, in its own process
64
+ group, within the preview's 20 s preflight budget, after its harness checks.
65
+ - **Supported harnesses: claude (model `haiku`) and pi (the instance's
66
+ model)**, proven on Linux with claude 2.1.288 and pi 1.3.0
67
+ (`scripts/naming-isolation-proof.mjs`).
68
+ - **Three stated exceptions:** Claude Code's own built-in plugins
69
+ (`cc-plugin-*@builtin`) load as they always do, `--bare` included; hooks
70
+ in the host's managed policy still apply; and pi runs its own credential
71
+ commands (`!command` keys and headers in models.json), as every pi launch
72
+ does. A claude login through `apiKeyHelper` is not read, so such a user
73
+ gets `harness-failed` and a numbered name.
74
+ - **codex is not supported yet:** a codex soul's preview is numbered, with
75
+ `naming.reason: "unsupported-harness"`.
76
+ - **A failure is never an error.** The preview numbers the instance as
77
+ before and says why in `naming.reason`: `no-task`, `unsupported-harness`,
78
+ `timeout`, `harness-failed` or `invalid-reply`.
79
+ - Routed with `--server`, the host must advertise the feature
80
+ ([The suggested name](../desktop-cli-api.md#the-suggested-name-feature-spawn-suggest-name)).
81
+
82
+ - **One chord for each everyday action, the same in `oats tui` and OATS
83
+ Desktop, from every focus, an agent's terminal too, with no leader first**
84
+ ([Chords](../tui.md#chords);
85
+ [desktop-keyboard.md](../../packages/desktop/docs/desktop-keyboard.md)).
86
+ On Linux and Windows:
87
+ - `Ctrl+Alt+O` opens the switcher.
88
+ - `Alt+Shift+Up` and `Alt+Shift+Down` open the terminal of the previous
89
+ or next instance.
90
+ - `Ctrl+Alt+1` to `Ctrl+Alt+8` show the first to eighth tab, and
91
+ `Ctrl+Alt+9` the last one.
92
+ - `Ctrl+Alt+Z` zooms the shown terminal.
93
+ - `Ctrl+Alt+A` goes to the other split group.
94
+
95
+ The Desktop's macOS chords are `⌘⌥O`, `⌘⌥↑`, `⌘⌥↓`, `⌘⌥1` to `⌘⌥9`, `⌘⌥Z`
96
+ and `⌘⌥A`. Help, the views, and stop, restart, start and retire stay on
97
+ the leader, which still works everywhere.
98
+ - **In `oats tui` the Ctrl+Alt chords need the kitty keyboard protocol,**
99
+ as the 0.66 chords did. The Alt+Shift arrows work in every terminal on
100
+ Linux and Windows, GNOME Terminal included. On macOS `oats tui` has no
101
+ chords: the leader does it all there.
102
+ - **While the terminal confirms the protocol, the help and the cheat sheet
103
+ lead with the chords,** each with its leader key beside it. The leader
104
+ keeps its own section.
105
+ - **A character typed with AltGr stays a character.** On Windows `AltGr`
106
+ is `Ctrl+Alt`: where it types a character (Spanish `€`, `@` and `#`,
107
+ Polish `ą`, `ę`, `ó` and `ż`), that key types it in both clients, and
108
+ the leader does what the chord would.
109
+ - **Windows Terminal takes `Ctrl+Alt+1` to `Ctrl+Alt+9`** for its own tabs,
110
+ and the Alt+Shift arrows while its panes are split.
111
+ [The matrix](../tui.md#which-terminals-let-the-chords-through) lists
112
+ what each terminal takes.
113
+
114
+ - **A Ctrl+Shift option for the shared chords, in `oats tui` and OATS
115
+ Desktop at once,** on Linux and Windows
116
+ ([Switch to Ctrl+Shift](../tui.md#switch-to-ctrlshift);
117
+ [desktop-keyboard.md](../../packages/desktop/docs/desktop-keyboard.md)).
118
+ It is for a terminal that lets Ctrl+Shift letters through to `oats tui`:
119
+ foot and Alacritty
120
+ ([Which family for my terminal](../tui.md#which-family-for-my-terminal)).
121
+ Ctrl+Alt stays the default.
122
+ - **Seven chords move:** `Ctrl+Shift+K` the palette, `Ctrl+Shift+P` a
123
+ spawn (the Desktop's Quick Open), `Ctrl+Shift+S` the switcher,
124
+ `Ctrl+Shift+M` zoom, `Ctrl+Shift+W` close the tab, `Ctrl+Shift+E` split
125
+ right and `Ctrl+Shift+D` split down.
126
+ - **The others keep their keys:** `Ctrl+Alt+A` the other group,
127
+ `Ctrl+Alt+F` the filter, the Alt+Shift arrows, `Ctrl+Alt+1` to
128
+ `Ctrl+Alt+9`, and in the Desktop `Ctrl+Alt+R`, an instance's name and
129
+ colour.
130
+ - **To switch,** choose **Ctrl+Shift (foot, Alacritty)** under
131
+ **Shortcut family, shared with oats tui** on the Desktop's Shortcuts page, or write
132
+ `{ "chords": "ctrl+shift" }` to `~/.oats/config/keys.json`
133
+ (`$OATS_HOME_DIR/config/keys.json` when that is set). The Desktop
134
+ switches at once; `oats tui` reads the file at its next start. A
135
+ missing or broken file means Ctrl+Alt, and the help says why.
136
+ - **The help names the family in force:** `?` in `oats tui`, the
137
+ Shortcuts page in the Desktop.
138
+ - **Your own keys still win, row by row:** `tui.json`'s `keys`, and the
139
+ Desktop's shortcuts editor, which shows a clash with a key the option
140
+ takes.
141
+ - **In `oats tui` it needs the kitty keyboard protocol;** the leader
142
+ works without it. With the option on, the seven are taken from an
143
+ agent's terminal too: pi's `Ctrl+Shift+P` (previous model) spawns
144
+ instead.
145
+ - macOS has no option.
146
+
147
+ - **Jump to the next or previous group in the palette,** in `oats tui` and
148
+ OATS Desktop ([The palette](../tui.md#the-palette);
149
+ [desktop-keyboard.md](../../packages/desktop/docs/desktop-keyboard.md)).
150
+ While the palette is open, `Alt+Shift+Down` moves the selection to the
151
+ first row of the next group, and `Alt+Shift+Up` to the previous one's;
152
+ both wrap. On macOS the Desktop's keys are `⌘N` and `⌥⌘N` (`⌘⇧N` stays
153
+ File → New Window).
154
+ - **The keys are the palette's while it is open.** There `⌘N` doesn't
155
+ choose a soul, and the Alt+Shift arrows don't open the next or previous
156
+ instance. With the palette closed, they do what they did before.
157
+ - **`oats tui`'s palette now groups its instances** as the sidebar and the
158
+ Desktop's palette do: by relation, with the group last used first. A dim
159
+ label names each group, and the selection skips it. The souls,
160
+ capabilities, views, acts and commands after them are a group each.
161
+ - Both palettes name the keys: the Desktop's in a line under the list,
162
+ `oats tui`'s in its cheat sheet. On macOS `oats tui` has no group key:
163
+ a terminal never passes ⌘.
164
+
165
+ - **Desktop: the soul page lists every skill an instance gets.** With OATS
166
+ 0.67.0 or later, **Composed for an instance › Skills** lists the soul's own
167
+ skills and the ones its capabilities add, each saying where it comes from
168
+ (**From this soul** or **From** the capability), and the "newer OATS" note
169
+ goes. A capability's skill file opens under its place in the instance home,
170
+ with **Open capability** above it. For a soul on a server, the server's OATS
171
+ must list them too. ([Desktop](../desktop.md))
172
+
173
+ - **Desktop: an instance's colour.** Each instance's dot (the sidebar, its
174
+ terminal tab, the command palette, the overview) shows the colour set for
175
+ it: filled while running, a ring while stopped. **Instance: name and
176
+ colour…** in the command palette, or Ctrl+Alt+R (⌥⌘R on macOS), opens a
177
+ small dialog for the focused instance: its name, and **None** plus the six
178
+ palette colours, applied at once through `oats instance color`. Needs OATS
179
+ 0.67.0 or later here, and on a server for its instances. The TUI leaves
180
+ Ctrl+Alt+R to the agent. ([Desktop](../desktop.md))
181
+
182
+ - **Desktop: an instance named from its task.** With an OATS that suggests
183
+ names (`spawn-suggest-name`), the spawn dialog asks for a name once the
184
+ Opening instruction holds three words and you pause typing. The soul's
185
+ harness replies with a short name for the work, and the role is added as
186
+ its suffix. It shows as the empty Name field's placeholder, "will be named
187
+ release-notes-manager", and in **What will be created**, and Spawn uses
188
+ it. Typing a name replaces it and stops suggestions for that dialog.
189
+ Spawning with Name empty and no suggestion yet shows **Naming…** and asks
190
+ once. When the instance can't be named from its task, it is numbered, and
191
+ a notification says why ("Named oats-desktop-expert-3: naming took longer
192
+ than 20 seconds."). Nothing is asked before you type, nor on a timer.
193
+ Spawns on a server keep their purpose. ([Desktop](../desktop.md))
194
+
195
+ - **The TUI draws an instance's mark in its colour**, its shape still saying
196
+ its state ([tui.md](../tui.md#what-it-shows)).
197
+
198
+ ## Changed
199
+
200
+ - **The leader is Ctrl+X in both clients and on every platform**
201
+ (awebai/oats#1433), as Emacs' prefix key: it was Alt+O on Linux and
202
+ Windows and ⌃\ on macOS. The keys after it do not change. Without the
203
+ kitty keyboard protocol Ctrl+X is one byte, 0x18, in every terminal, so it
204
+ needs no protocol and no timing; under the protocol `oats tui` reads it
205
+ too, and Ctrl+Shift+X and Ctrl+Alt+X are not the leader
206
+ ([The leader](../tui.md#the-leader)).
207
+ - **Ctrl+X twice sends Ctrl+X to the program,** as the leader twice
208
+ always has. The shell's Ctrl+X Ctrl+E is now Ctrl+X twice, then Ctrl+E,
209
+ and nano exits with Ctrl+X twice.
210
+ - **In the Desktop, Cut keeps Ctrl+X** in a text field (an input, a text
211
+ area, an editable region) that is not a terminal, on Linux and Windows.
212
+ On macOS Cut is ⌘X, so the leader works there too
213
+ ([desktop-keyboard.md](../../packages/desktop/docs/desktop-keyboard.md#the-leader)).
214
+ - **Alt+O and ⌃\ go back to the programs:** on Linux and Windows an agent
215
+ gets Alt+O as Esc then `o` (on macOS Option+O types its character, `ø`
216
+ on a US layout, unless the terminal sends Option as Meta), and ⌃\ as it
217
+ is typed, unless you bind either as the leader again.
218
+
219
+ - **The shared chords move from Ctrl+Shift to Ctrl+Alt on Linux and
220
+ Windows,** in both clients. kitty, Ghostty, WezTerm, Konsole and Windows
221
+ Terminal take most Ctrl+Shift chords for themselves, so in `oats tui`
222
+ most of 0.66's chords never arrived. Old → new:
223
+
224
+ | Action | Was | Now |
225
+ |---|---|---|
226
+ | the palette | `Ctrl+Shift+K` | `Ctrl+Alt+K` |
227
+ | Quick Open in the Desktop, a spawn in `oats tui` | `Ctrl+Shift+P` | `Ctrl+Alt+P` |
228
+ | close the tab | `Ctrl+Shift+W` | `Ctrl+Alt+W` |
229
+ | the filter | `Ctrl+Shift+F` | `Ctrl+Alt+F` |
230
+ | split right | `Ctrl+Shift+E` | `Ctrl+Alt+E` |
231
+ | split down | `Ctrl+Shift+O` | `Ctrl+Alt+Shift+E` |
232
+ | next and previous tab in `oats tui` | `Ctrl+Tab`, `Ctrl+Shift+Tab` | `Alt+Shift+Right`, `Alt+Shift+Left` |
233
+ | the Desktop's second next and previous tab chords | `Ctrl+PgDn`, `Ctrl+PgUp` (outside a terminal) | `Alt+Shift+Right`, `Alt+Shift+Left` (everywhere) |
234
+ | the Desktop's go to tab 1–9 | `Alt+1` to `Alt+9` (outside a terminal) | `Ctrl+Alt+1` to `Ctrl+Alt+9` (everywhere) |
235
+
236
+ - **The Alt+Shift arrows no longer reach the agent in its terminal:** in
237
+ both clients they are the chords, there as everywhere else.
238
+ - The Desktop keeps `Ctrl+Tab` and `Ctrl+Shift+Tab`, and its other
239
+ Ctrl+Shift chords (sidebar, instance panel, spawn, theme picker, copy).
240
+ - On macOS the Desktop gains `⌘⌥→` and `⌘⌥←` for the next and previous
241
+ tab, beside `⌃Tab`.
242
+ - A binding you set yourself in the Desktop's shortcuts editor is kept,
243
+ a macOS ⌘⌥ one that 0.66 saved by the character ⌥ typed (`⌥⌘Ø`) too.
244
+ When it is a chord a default now takes, the editor shows the clash.
245
+
246
+ - **In OATS Desktop, a key you bound yourself now wins over a default on
247
+ every key two actions share,** not only on the seven keys of the
248
+ Ctrl+Shift option
249
+ ([desktop-keyboard.md](../../packages/desktop/docs/desktop-keyboard.md)).
250
+ Before, a default of a narrower context (the tabs, the sidebar, a stage)
251
+ could win over a global key of yours. The shortcuts editor lists every
252
+ such clash, and now says which of the two runs: "Ctrl+Shift+K runs
253
+ “Sidebar: show or hide” (yours) where both apply; “Command palette” has
254
+ it by default."
255
+
256
+ - **`.oats-color` is a kernel-owned home name**: a capability's
257
+ `retirement.disposable.home` cannot declare it
258
+ ([capabilities.md](../capabilities.md)).
259
+
260
+ - **Desktop: the soul page's Instructions has two sections.** **Defined in
261
+ this soul** holds the soul's own `AGENTS.md` and its skills. **Composed for
262
+ an instance** holds the composed `AGENTS.md` and the skills an instance
263
+ gets, each saying where it comes from (**From this soul**). Until OATS lists
264
+ the skills that capabilities add, a note says a newer OATS lists them. The
265
+ boundary is a named group for assistive technology too, and the tree is
266
+ still one tab stop. ([Desktop](../desktop.md))
267
+
268
+ - **Desktop: the spawn dialog's name is optional and its last field.**
269
+ **Name · optional** now comes last, before **Developer settings**. The soul-name
270
+ prefix and its **Prefix with the soul name** switch are gone. Left empty,
271
+ the kernel numbers the instance. The Desktop's spawn dialog adds the role
272
+ to a typed name (the last word of the soul's name) and uses the name in
273
+ lowercase: `desktop-improvements` for `oats-desktop-expert` spawns as
274
+ `desktop-improvements-expert`, and a name that already ends in the role
275
+ gets no second one. On a CLI without
276
+ `spawn-name`, and for a spawn on a server, a typed name is still a purpose
277
+ named `<soul>-<purpose>`. The dialog opens on the Opening instruction;
278
+ Ctrl+1 / ⌘1 still goes to Name. ([Desktop](../desktop.md),
279
+ [souls and instances](../souls-and-instances.md))
280
+
281
+ - **Desktop: the spawn dialog starts with the Opening instruction.** It is the
282
+ form's first field, and the dialog opens with the cursor in it, after a
283
+ restored instruction's text. In a narrow window, **What will be created** now comes after the form's last
284
+ field instead of above the form. ([Desktop](../desktop.md))
285
+
286
+ - **Desktop: the sidebar's footer no longer has a "commands" button.** The
287
+ leader's chord works as before. The keyboard shortcuts editor lists the
288
+ keys that follow it: open it from the footer's shortcuts button, with
289
+ Ctrl+, / ⌘, or from the palette.
290
+
291
+ - **Desktop: "Needs input" shows on an instance's second line.** The name
292
+ line keeps the whole name. The mark, or "N below" on a collapsed parent,
293
+ replaces the repository, pull request and branch, which stay in the hover
294
+ card. A home that is being retired or set up keeps its state on that line.
295
+
296
+ - **Desktop: the sidebar's dotted sibling links sit a little further from
297
+ the lines to children.**
298
+
299
+ - **`oats tui`'s switcher lists one row per workspace, whichever machines
300
+ it is on.** A deployment on this computer's list that the run has not
301
+ opened is read for its workspace (`oats status --dir <path> --json`, one at
302
+ a time, 30 seconds each and 60 in all, at the start and when the switcher
303
+ opens or is refreshed). It then joins its workspace's row instead of
304
+ standing apart under `On this machine, not opened`. Under each workspace a
305
+ dim line per deployment names its machine and, when it is not live, its
306
+ state (`not opened`, `not observed`, `not reached`, ...). `Enter` on a
307
+ workspace opens its deployments of this machine too, so the view holds
308
+ them and the other machines' at once. A read that fails or times out
309
+ leaves the deployment as its own row, saying why. The cheat sheet of the
310
+ list of instances names `w workspaces`.
311
+ ([The switcher](../tui.md#the-switcher))
312
+
313
+ - **`oats tui`'s terminal panel has a tab bar like a terminal's.** Its top
314
+ row is always the tab bar, with one tab or many. Each tab is the agent's
315
+ name, with `· <machine>` for another machine's agent, and tabs are divided
316
+ by `│` (`|` in ASCII). The shown tab is bracketed, `[name]`, and bold, in
317
+ reverse video while the terminal has the focus. The other tabs are dim.
318
+ ([Tabs](../tui.md#tabs))
319
+
320
+ - **`oats tui` marks a row that needs input with a tag in words.** Where it
321
+ drew a bare `!` at the right of the row, it now draws the Desktop's words
322
+ in reverse video in the waiting colour: `Needs input`, and on a folded row
323
+ with waiting instances under it, `3 below` (`99+ below` past 99). On the
324
+ selected row the tag is the waiting colour not reversed, so it stands
325
+ apart from the selection's bar, and under `NO_COLOR` the reverse video
326
+ alone carries it. On a row too narrow for the whole name beside the
327
+ words, the tag shrinks to `!` or the count alone, still reversed, and the
328
+ name keeps every cell it had. ([What it shows](../tui.md#what-it-shows))
329
+
330
+ - **The `oats-getting-started` skill covers two Linux snags from a rehearsal.**
331
+ With NodeSource's Node under `/usr`, it sets a per-user npm prefix and now
332
+ also puts `~/.local/bin` on PATH for its own later commands and asks the
333
+ person to add it to their shell's startup file. Without FUSE (Ubuntu 22.04
334
+ and later), it names `libfuse2` (`libfuse2t64` on Ubuntu 24.04) as the
335
+ install, beside the `--appimage-extract-and-run` fallback.
336
+
337
+ ## Fixed
338
+
339
+ - **`oats spawn --preview` names each capability skill as the spawn copies
340
+ it.** A manifest whose `skills` entry is a directory of skills (the
341
+ documented `"skills": ["skills"]`) showed as one skill named `skills`, and
342
+ a manifest with no `skills` showed none of the `skills/` directories the
343
+ spawn copies. The preview now lists each of them, as `--composed-skills`
344
+ does ([The preview](../desktop-cli-api.md#the-preview)).
345
+
346
+ ## Provider updates
347
+
348
+ - **oats.framework 1.13.5: oats.core 2.6.6, oats.support 1.0.1.** Text
349
+ only: neither floor (`compatibility.oats`) changes.
350
+ - **Instances are named for their work, with the soul's role last.**
351
+ `/oats-operate` and `/oats-souls` (oats.core) teach
352
+ `--name <descriptive>-<role>`, the role being the last word of the soul's
353
+ name: `--name desktop-improvements-expert` for an `oats-desktop-expert`,
354
+ not `oats-desktop-expert-desktop-improvements`. `--purpose` still derives
355
+ `<soul>-<purpose>`, for automations and scripts that know only the soul.
356
+ [Souls and instances](../souls-and-instances.md) states the convention
357
+ ([#1421](https://github.com/awebai/oats/issues/1421)).
358
+ - **Agents set needs-input whenever they need anything from a human.** The
359
+ oats.core inject and `/oats-operate` make `oats instance attention`
360
+ mandatory, under an IMPORTANT lead, for any question, decision,
361
+ approval, credential or other input an instance waits on, not only when
362
+ it cannot go on without the answer, so the wait shows on `oats status`
363
+ and in the Desktop. It stays out of FYIs and progress reports.
364
+ oats.support's hand-off skill says the same, and `/oats-operate` says
365
+ which questions the Claude Code emitter already reports
366
+ ([oats.core: needs input](../capabilities.md#oatscore-needs-input)).