@awebai/oats 0.69.19 → 0.69.21
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.
- package/bin/oats.mjs +28 -5
- package/docs/capabilities.md +27 -14
- package/docs/capability-manifest.schema.json +1 -1
- package/docs/container.md +218 -18
- package/docs/desktop-cli-api.md +105 -11
- package/docs/desktop.md +122 -65
- package/docs/implementation.md +3 -2
- package/docs/integrations.md +2 -2
- package/docs/knowledge.md +5 -5
- package/docs/official-catalog.md +5 -5
- package/docs/packages.md +13 -13
- package/docs/release-notes/v0.69.20.md +325 -0
- package/docs/release-notes/v0.69.21.md +155 -0
- package/docs/servers.md +9 -3
- package/docs/souls-and-instances.md +15 -2
- package/docs/upgrading.md +17 -5
- package/docs/workspaces.md +13 -7
- package/lib/capability-contract.mjs +2 -2
- package/lib/command-flags.mjs +1 -0
- package/lib/core.mjs +36 -198
- package/lib/hook-outcome.mjs +6 -0
- package/lib/instance-inspect.mjs +3 -0
- package/lib/instance-lifecycle.mjs +19 -1
- package/lib/instance-listing.mjs +11 -6
- package/lib/instance-pin.mjs +59 -0
- package/lib/kernel-features.mjs +1 -1
- package/lib/launch-prompt-fixtures/README.md +6 -0
- package/lib/retire-admission.mjs +215 -0
- package/lib/servers.mjs +11 -3
- package/package-catalog.json +3 -3
- package/package.json +1 -1
- package/packages/client/attributed-human.mjs +13 -0
- package/packages/client/deployment-data.mjs +4 -0
- package/packages/client/deployment-panel.mjs +2 -0
- package/packages/client/instance-lifecycle.mjs +6 -4
- package/packages/client/lifecycle-confirmation.mjs +4 -2
- package/packages/client/lifecycle-contract.mjs +11 -6
- package/packages/client/remote-roster.mjs +4 -0
- package/packages/client/roster-row-facts.mjs +50 -0
- package/packages/record/README.md +15 -2
- package/packages/record/docs/capture-service.md +14 -0
- package/packages/record/lib/canonical.mjs +2 -70
- package/packages/record/lib/capture-aw-unit.mjs +14 -3
- package/packages/record/lib/capture-aw.mjs +11 -5
- package/packages/record/lib/capture-health.mjs +16 -5
- package/skills/oats-getting-started/SKILL.md +211 -28
|
@@ -4,7 +4,8 @@ description: >-
|
|
|
4
4
|
The way into OATS (Open Agent Team Specification) for a person who has only
|
|
5
5
|
a coding agent. Asks about their project, installs OATS, OATS Desktop and
|
|
6
6
|
the messaging CLI, creates the workspace's messaging account and team (with
|
|
7
|
-
no sign-in,
|
|
7
|
+
no sign-in, on the person's own account if they sign in, or on their own
|
|
8
|
+
aweb server), writes a new
|
|
8
9
|
workspace's skeleton (or joins this machine to an existing workspace),
|
|
9
10
|
spawns the workspace's setup expert, which does the rest, and opens the
|
|
10
11
|
Desktop on it. Offers the TUI.
|
|
@@ -82,7 +83,10 @@ costs the person a round. After that yes, nothing more is asked.
|
|
|
82
83
|
- **One yes covers the changes to their computer.** Step 1's message lists
|
|
83
84
|
them in plain words, and their yes covers every one: don't ask again step
|
|
84
85
|
by step. The list, from step 2's checks: the tools you install (on Linux
|
|
85
|
-
per user, under `~/.local`; on macOS with Homebrew),
|
|
86
|
+
per user, under `~/.local`; on macOS with Homebrew), on their own aweb
|
|
87
|
+
server (step 1) `aw` at the version this OATS release was tested with on
|
|
88
|
+
such a server, when none is installed or the installed one is older (a
|
|
89
|
+
newer one is kept), the line that puts
|
|
86
90
|
them on their PATH in their shell's startup file (`~/.local/bin` on Linux;
|
|
87
91
|
on macOS, Homebrew's `brew shellenv` line, only when Homebrew is new), the
|
|
88
92
|
aweb channel plugin in Claude (Claude only) or pi's aweb extension,
|
|
@@ -235,6 +239,30 @@ the final values in one short message before you go on. The rules:
|
|
|
235
239
|
- Tell them they attach themselves to that account later in the setup, with
|
|
236
240
|
the setup expert. Only if they want the team on their own aweb account
|
|
237
241
|
now, they sign in to it in their browser in step 5 instead.
|
|
242
|
+
- **Hosted aweb, or their own aweb server?** The line says "on aweb's
|
|
243
|
+
hosted service, unless you run your own aweb server"; hosted is the
|
|
244
|
+
default. Keep its second half in your own words too: it is how a
|
|
245
|
+
person with their own server learns this branch exists. With their own
|
|
246
|
+
server, the same round asks three things, none of them secret: the
|
|
247
|
+
namespace domain `ND` they control (for example
|
|
248
|
+
`agents.acme.com`, written in lowercase), the server's public address
|
|
249
|
+
`U` (`https://…`, the API URL their server gives its users), and whether
|
|
250
|
+
their server uses the public AWID registry. Answers given in the prompt
|
|
251
|
+
that started you are used without asking. When it uses a private
|
|
252
|
+
registry, the own-server branch stops here, before anything is written:
|
|
253
|
+
tell the person in one sentence that a private registry needs oats.aweb
|
|
254
|
+
with `oats aweb setup --registry`, and that this skill stops here. Offer
|
|
255
|
+
hosted aweb now (the hosted defaults above, `N` among them, shown in one
|
|
256
|
+
short message) or waiting for that release. Otherwise, tell them, in
|
|
257
|
+
plain words, what must already be in place on their side, since you
|
|
258
|
+
make none of it: the namespace's controller key on this computer, for
|
|
259
|
+
this computer account; the `_awid.ND` DNS record published for that
|
|
260
|
+
key; and their server reachable at `U`. Step 9
|
|
261
|
+
checks them, read-only. On their own server there is no account `N` and
|
|
262
|
+
no step 5: the team is `<workspace>:ND`, created in step 9 in their
|
|
263
|
+
namespace, and `A` is `<workspace>-root` as on hosted. Never offer it on
|
|
264
|
+
a machine found-list, or for an existing workspace: its invite carries
|
|
265
|
+
the team and the server.
|
|
238
266
|
- **The harness for the setup expert:** `claude`, `codex` or `pi`. Default:
|
|
239
267
|
the one you are, if it is one of these.
|
|
240
268
|
- **The deployment directory `D`:** where OATS lives on this machine.
|
|
@@ -533,7 +561,7 @@ installed CLI's catalog:
|
|
|
533
561
|
node -e 'const c=require(process.argv[1]);console.log(c.packages["oats.framework"].ref,c.packages["oats.aweb"].ref)' "$(oats root)/package-catalog.json"
|
|
534
562
|
```
|
|
535
563
|
|
|
536
|
-
It prints the two refs, for example `oats-framework/v1.
|
|
564
|
+
It prints the two refs, for example `oats-framework/v1.26.0 v1.43.0`. If the
|
|
537
565
|
framework's version (after the `/`) is below `1.19.0`, or with aweb
|
|
538
566
|
`oats.aweb`'s is below `v1.33.1`, this OATS release is older than this
|
|
539
567
|
skill: stop, and tell the person to wait for the next OATS
|
|
@@ -560,12 +588,64 @@ you can check `"skills":[]`:
|
|
|
560
588
|
node -e 'const fs=require("fs"),path=require("path"),os=require("os");const f=path.join(process.env.PI_CODING_AGENT_DIR||path.join(os.homedir(),".pi","agent"),"settings.json");const s=JSON.parse(fs.readFileSync(f,"utf8"));const ours=(e)=>/^npm:@awebai\/pi(@|$)/.test(typeof e==="string"?e:e&&e.source||"");s.packages=(s.packages||[]).map((e)=>ours(e)?{...(typeof e==="object"?e:{}),source:typeof e==="string"?e:e.source,skills:[]}:e);fs.writeFileSync(f,JSON.stringify(s,null,2)+"\n");console.log(JSON.stringify(s.packages.filter(ours)))'
|
|
561
589
|
```
|
|
562
590
|
|
|
591
|
+
**On hosted aweb** (the default), the latest `aw`:
|
|
592
|
+
|
|
563
593
|
```bash
|
|
564
594
|
npm install -g @awebai/aw && aw version
|
|
565
595
|
```
|
|
566
596
|
|
|
567
597
|
`aw` must be 1.36.33 or later.
|
|
568
598
|
|
|
599
|
+
**On their own aweb server** (step 1), `aw` is the version this OATS
|
|
600
|
+
release's `oats.aweb` was tested with, which `oats.aweb` publishes in its
|
|
601
|
+
`aw-compat.json`: hosted aweb upgrades its server before a new `aw` comes
|
|
602
|
+
out, but their own server has no such order. Read that version at the exact
|
|
603
|
+
`oats.aweb` release the installed CLI's catalog names, never at `main`.
|
|
604
|
+
This prints `TESTED <version>`, or why it can't:
|
|
605
|
+
|
|
606
|
+
```bash
|
|
607
|
+
node -e 'const c=require(process.argv[1]).packages["oats.aweb"],m=/^https:\/\/github\.com\/([A-Za-z0-9_.-]+)\/([A-Za-z0-9_.-]+?)(?:\.git)?$/.exec(c.url),v=/^v(\d+)\.(\d+)\.(\d+)$/.exec(c.ref);if(!m){console.log("NOT_GITHUB "+c.url);process.exit(1)}if(!v||v.slice(1).reduce((d,x,i)=>d||x-[1,42,1][i],0)<0){console.log("TOO_OLD "+c.ref);process.exit(1)}const u="https://raw.githubusercontent.com/"+m[1]+"/"+m[2]+"/"+c.ref+"/"+c.path+"/capabilities/oats-aweb/aw-compat.json";fetch(u).then(r=>{if(!r.ok)throw new Error("HTTP "+r.status+" "+u);return r.json()}).then(j=>{if(Object.keys(j).sort().join()!=="min,tested"||typeof j.tested!=="string"||!/^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(-(0|[1-9]\d*|\d*[A-Za-z-][0-9A-Za-z-]*)(\.(0|[1-9]\d*|\d*[A-Za-z-][0-9A-Za-z-]*))*)?(\+[0-9A-Za-z-]+(\.[0-9A-Za-z-]+)*)?$/.test(j.tested))throw new Error("unexpected "+JSON.stringify(j));console.log("TESTED "+j.tested)}).catch(e=>{console.log("FAILED "+e.message);process.exit(1)})' "$(oats root)/package-catalog.json"
|
|
608
|
+
```
|
|
609
|
+
|
|
610
|
+
- **`TOO_OLD`:** this OATS release's `oats.aweb` is older than `v1.42.1`,
|
|
611
|
+
the first that sets up a team on a person's own server.
|
|
612
|
+
**`NOT_GITHUB` or `FAILED`:** the tested version can't be read. Either
|
|
613
|
+
way, the own-server branch stops here. Tell the person in one sentence,
|
|
614
|
+
and offer hosted aweb now (step 1's hosted defaults, `N` among them,
|
|
615
|
+
shown in one short message) or waiting for the next OATS release.
|
|
616
|
+
- **`TESTED <tested>`:** compare it with the `aw` already installed, in
|
|
617
|
+
`oats.aweb`'s own version order, where a pre-release of a newer version
|
|
618
|
+
counts as newer. With `<tested>` written in:
|
|
619
|
+
|
|
620
|
+
```bash
|
|
621
|
+
node -e 'const P=(s)=>{const m=/^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[A-Za-z-][0-9A-Za-z-]*)(?:\.(?:0|[1-9]\d*|\d*[A-Za-z-][0-9A-Za-z-]*))*))?(?:\+[0-9A-Za-z-]+(?:\.[0-9A-Za-z-]+)*)?$/.exec(s);if(!m)return null;const r=[m[1],m[2],m[3]].map(Number);return r.every(Number.isSafeInteger)?{r,p:m[4]?m[4].split("."):[]}:null};const C=(a,b)=>{for(let i=0;i<3;i++)if(a.r[i]!==b.r[i])return a.r[i]-b.r[i];if(!a.p.length||!b.p.length)return b.p.length-a.p.length;for(let i=0;i<Math.min(a.p.length,b.p.length);i++){const x=a.p[i],y=b.p[i],xn=/^\d+$/.test(x),yn=/^\d+$/.test(y);if(x===y)continue;if(xn&&yn)return x.length!==y.length?x.length-y.length:x<y?-1:1;if(xn!==yn)return xn?-1:1;return x<y?-1:1}return a.p.length-b.p.length};const t=P(process.argv[1]),l=/^aw (\S+)$/.exec(process.argv[2]||""),v=l&&P(l[1]);if(!t){console.log("FAILED tested "+process.argv[1]);process.exit(1)}const d=v?C(v,t):-1;console.log(d<0?"INSTALL":d===0?"EQUAL "+l[1]:"NEWER "+l[1])' "<tested>" "$(aw version 2>/dev/null | head -n 1)"
|
|
622
|
+
```
|
|
623
|
+
|
|
624
|
+
- **`INSTALL`:** no `aw`, a version it can't read, or one below
|
|
625
|
+
`<tested>` (below `oats.aweb`'s floor included). Install exactly
|
|
626
|
+
`<tested>`, then check it:
|
|
627
|
+
|
|
628
|
+
```bash
|
|
629
|
+
npm install -g "@awebai/aw@<tested>" && aw version && file -L "$(command -v aw)" && uname -m
|
|
630
|
+
```
|
|
631
|
+
|
|
632
|
+
`aw version`'s first line must be exactly `aw <tested>`, and the `file`
|
|
633
|
+
line must name this machine's architecture, the one `uname -m` prints
|
|
634
|
+
(`x86-64` for `x86_64`, `aarch64` for `aarch64` on Linux; `x86_64` or
|
|
635
|
+
`arm64` on macOS). A different version, or a program for another
|
|
636
|
+
machine or no program at all (npm put a wrong or missing build in
|
|
637
|
+
place), stops the own-server branch as above. Where `file` itself is
|
|
638
|
+
missing (`command not found`), say so in the hand-over and rely on
|
|
639
|
+
`aw version`: a program that runs and prints its version was built for
|
|
640
|
+
this machine. Keep `aw <tested>` for the hand-over.
|
|
641
|
+
- **`EQUAL <tested>`:** that version is installed already: install
|
|
642
|
+
nothing. Keep `aw <tested>` for the hand-over.
|
|
643
|
+
- **`NEWER <version>`:** a newer `aw` is installed. Keep it, install
|
|
644
|
+
nothing, and go on: another deployment on this computer may need it.
|
|
645
|
+
Keep "aw <version> is newer than the tested <tested>; kept" for the
|
|
646
|
+
hand-over: it is the version this setup ran with.
|
|
647
|
+
- **`FAILED`** stops the own-server branch as above.
|
|
648
|
+
|
|
569
649
|
**Then the Desktop. Every step verifies before it installs.** Wait for step
|
|
570
650
|
3's download, then read its log. Run this once: it waits up to a minute
|
|
571
651
|
for a `DONE` line ("How to work", the time budget):
|
|
@@ -650,8 +730,9 @@ Categories=Development;
|
|
|
650
730
|
|
|
651
731
|
**Only for a new workspace with aweb whose person chose, in step 1, the team
|
|
652
732
|
on their own aweb account now.** Otherwise skip it: step 9 creates the
|
|
653
|
-
workspace's account (the default), joins an existing workspace
|
|
654
|
-
found-list
|
|
733
|
+
workspace's account (the default), joins an existing workspace, signs up a machine
|
|
734
|
+
found-list and creates the team on their own aweb server, which has no
|
|
735
|
+
account to sign in to.
|
|
655
736
|
|
|
656
737
|
The workspace's agents share one team, its **default team**, which the
|
|
657
738
|
person's own aweb account creates here. Say to them, in your words, exactly
|
|
@@ -770,8 +851,8 @@ name: acme
|
|
|
770
851
|
members:
|
|
771
852
|
- git:github.com/acme/acme-oats # the host; the setup expert adds the others
|
|
772
853
|
packages:
|
|
773
|
-
oats.framework: v1.
|
|
774
|
-
oats.aweb: v1.
|
|
854
|
+
oats.framework: v1.26.0 # the installed CLI's catalog versions (below)
|
|
855
|
+
oats.aweb: v1.43.0 # messaging: agent identities, mail and chat
|
|
775
856
|
oats.machine: v0.1.1 # on a machine found-list only: the machine's steward
|
|
776
857
|
defaults:
|
|
777
858
|
capabilities:
|
|
@@ -789,6 +870,11 @@ defaultTeam: acme # every soul starts in this team
|
|
|
789
870
|
9's signup creates, checked there against this line. With step 5's
|
|
790
871
|
sign-in, it is `T` from step 5 instead, written in literally. Its label
|
|
791
872
|
(here `acme`) is the workspace name.
|
|
873
|
+
- **On their own aweb server,** the team is `<workspace>:ND` (here
|
|
874
|
+
`acme:agents.acme.com`), with `ND` from step 1: the team step 9 creates
|
|
875
|
+
in their namespace, checked there against this line. It is the only team
|
|
876
|
+
and the default: no `default:…aweb.ai` team anywhere in the file, and no
|
|
877
|
+
`localTeams`.
|
|
792
878
|
- **The `oats.machine` line,** at the catalog's
|
|
793
879
|
`packages."oats.machine".ref`, only on a machine found-list.
|
|
794
880
|
- **The `tasks` line** is step 1's tasks answer: `oats.aweb-tasks` without
|
|
@@ -957,8 +1043,9 @@ readiness still reports a problem.
|
|
|
957
1043
|
`oats sync --dir D`, then check again.
|
|
958
1044
|
2. **A new workspace without step 5's sign-in, and a machine found-list:
|
|
959
1045
|
sign up the workspace's aweb account and team,** with `N` and `A` from
|
|
960
|
-
step 1: no API key or token, nothing for the person to type.
|
|
961
|
-
|
|
1046
|
+
step 1: no API key or token, nothing for the person to type. On their
|
|
1047
|
+
own aweb server there is no signup: take "Their own aweb server", the
|
|
1048
|
+
last part of this item, instead. Otherwise preview first, then run it:
|
|
962
1049
|
|
|
963
1050
|
```bash
|
|
964
1051
|
cd "D" && oats aweb setup --soul S --username N --name A --label L --plan --json
|
|
@@ -972,11 +1059,20 @@ readiness still reports a problem.
|
|
|
972
1059
|
- **Then tell the person,** in your words: this is the workspace's
|
|
973
1060
|
team, on an aweb account created for it; they attach themselves to it
|
|
974
1061
|
later in the setup, with the setup expert.
|
|
975
|
-
- **`
|
|
976
|
-
|
|
977
|
-
|
|
1062
|
+
- **`E_SETUP_USERNAME_UNAVAILABLE`:** aw refused `N` (its message says
|
|
1063
|
+
why: taken, reserved or its format), and nothing was created. On a
|
|
1064
|
+
machine found-list, ask nothing: tell the person what it says, and
|
|
1065
|
+
stop. Otherwise ask the person for another `N`, change the team line in
|
|
1066
|
+
`D/<repo>/oats-workspace.yaml` to `default:<new N>.aweb.ai`, commit and
|
|
1067
|
+
push it, run `oats sync --dir D`, then run the preview and the signup
|
|
1068
|
+
again with the new `N`.
|
|
1069
|
+
- **`E_SETUP_NATIVE`:** aw failed, and its output is withheld (the
|
|
1070
|
+
preview does not contact aweb). An oats.aweb older than the one that
|
|
1071
|
+
answers `E_SETUP_USERNAME_UNAVAILABLE` (awebai/oats-aweb#286) also
|
|
1072
|
+
fails this way when `N` is taken. The run may also have left a root
|
|
1073
|
+
part-way. Never remove `D/.aw`, and never rerun blindly.
|
|
978
1074
|
On a machine found-list, ask nothing: tell the person that the run
|
|
979
|
-
failed,
|
|
1075
|
+
failed, and that `N` may be taken, and stop.
|
|
980
1076
|
Otherwise look first, read-only: `test -e "D/.aw" && echo RETAINED`.
|
|
981
1077
|
- **Nothing printed:** aw kept nothing, so `N` is free to change. Ask
|
|
982
1078
|
the person for another `N`, change the team line in
|
|
@@ -989,6 +1085,57 @@ readiness still reports a problem.
|
|
|
989
1085
|
unchanged, and it reuses that root. Anything else, the preview
|
|
990
1086
|
failing included: stop, spawn nothing, and tell the person what it
|
|
991
1087
|
shows.
|
|
1088
|
+
- **Their own aweb server (step 1), in place of the signup.** Nothing for
|
|
1089
|
+
the person to type, and no key passes through you. `ND`, `U` and `A`
|
|
1090
|
+
come from step 1, and `L` is step 7's label.
|
|
1091
|
+
- **First, the prerequisites, read-only:**
|
|
1092
|
+
|
|
1093
|
+
```bash
|
|
1094
|
+
cd "D" && aw id namespace check-txt --domain ND --json; echo "exit=$?"
|
|
1095
|
+
```
|
|
1096
|
+
|
|
1097
|
+
It fails when the controller key for `ND` is not on this computer
|
|
1098
|
+
for this account, or when the `_awid.ND` record is missing, not
|
|
1099
|
+
visible yet, or names another key. Its output says which. Then stop
|
|
1100
|
+
and spawn nothing. Tell the person in one plain sentence which one is
|
|
1101
|
+
missing, and that it's theirs to put in place, on their side. Once
|
|
1102
|
+
they say it is, run this part again from here. Never make the key
|
|
1103
|
+
(`aw id namespace prepare-controller`) or touch `~/.awid`.
|
|
1104
|
+
- **Then create the team,** registered with their server. It takes up
|
|
1105
|
+
to a few minutes. There is no preview, and it prints text, not JSON:
|
|
1106
|
+
|
|
1107
|
+
```bash
|
|
1108
|
+
cd "D" && AWEB_URL="U" oats aweb setup --soul S --create L --namespace ND --name A
|
|
1109
|
+
```
|
|
1110
|
+
- **Success** prints `✓ created <T>, accepted it into <root>, recorded
|
|
1111
|
+
roots[<T>]`. `<T>` must be step 7's team line, `L:ND`. Anything else:
|
|
1112
|
+
stop, spawn nothing, and tell the person what it shows. Two more of
|
|
1113
|
+
its lines are expected, and need nothing from you. Since step 7
|
|
1114
|
+
wrote no `localTeams`, it says the workspace "does not allow local
|
|
1115
|
+
teams" and shows `teams:` lines to commit: step 7 committed them
|
|
1116
|
+
already, so when the team they show is step 7's line, nothing is
|
|
1117
|
+
left to do. Its `readiness:` line can say
|
|
1118
|
+
`needs-configuration`: item 5's check decides, not that line.
|
|
1119
|
+
- **`team key: <path>`** is where the key of their agents' group now
|
|
1120
|
+
lives on this computer. Tell the person that, in plain words, and that
|
|
1121
|
+
they keep it backed up and never share it. The path, never the key,
|
|
1122
|
+
goes in the hand-over.
|
|
1123
|
+
- **"already exists in the registry, and its team key is not on this
|
|
1124
|
+
machine":** `L:ND` is taken in their namespace, and nothing was
|
|
1125
|
+
created. Ask the person for another name for the group, in the same
|
|
1126
|
+
form as the workspace name. In `D/<repo>/oats-workspace.yaml`, change
|
|
1127
|
+
the team's label, its `team:` and `defaultTeam` to it, then commit
|
|
1128
|
+
and push it, and run `oats sync --dir D`. Run the create again, with
|
|
1129
|
+
the new label as `L`.
|
|
1130
|
+
- **"re-run the same command to resume",** or a run that was killed or
|
|
1131
|
+
timed out: run the same line again, unchanged. It continues the
|
|
1132
|
+
create, and never makes a second team.
|
|
1133
|
+
- **Anything else** (a refused registration, a team-server record that
|
|
1134
|
+
names another address, a missing controller key): stop, spawn
|
|
1135
|
+
nothing, and tell the person in one sentence what it means. Never
|
|
1136
|
+
rerun it with other values.
|
|
1137
|
+
- **Then tell the person,** in your words: this is the group their
|
|
1138
|
+
agents talk in, on their own server, in their namespace `ND`.
|
|
992
1139
|
3. **Existing workspace: the person gets an invite** from a member of `L`,
|
|
993
1140
|
whose own agent runs
|
|
994
1141
|
`oats aweb invite --soul <their soul> --label L --json` in their
|
|
@@ -1009,7 +1156,15 @@ readiness still reports a problem.
|
|
|
1009
1156
|
owner decides.
|
|
1010
1157
|
4. **Existing workspace: the person joins in their own terminal,** which you
|
|
1011
1158
|
open for them ("How to work"), pasting the token at the hidden prompt,
|
|
1012
|
-
with `D`, `S` and `A` filled in
|
|
1159
|
+
with `D`, `S` and `A` filled in. Before you open it, list the per-team
|
|
1160
|
+
roots `D` already holds, read-only, and keep what it prints (often
|
|
1161
|
+
nothing) for item 5:
|
|
1162
|
+
|
|
1163
|
+
```bash
|
|
1164
|
+
ls -d "D"/.aweb-roots/*/.aw 2>/dev/null
|
|
1165
|
+
```
|
|
1166
|
+
|
|
1167
|
+
Then open the window:
|
|
1013
1168
|
|
|
1014
1169
|
```text
|
|
1015
1170
|
cd "D" && sh -c 'stty -echo; printf "Invite token: "; read -r T; stty echo; echo; printf "%s\n" "$T" | oats aweb setup --soul S --invite-stdin --name A'
|
|
@@ -1032,17 +1187,38 @@ readiness still reports a problem.
|
|
|
1032
1187
|
```
|
|
1033
1188
|
|
|
1034
1189
|
5. **After items 2 to 4, check again** (item 1), and expect `"member": true`.
|
|
1035
|
-
On `"member": false`, stop and spawn nothing
|
|
1036
|
-
item
|
|
1037
|
-
|
|
1038
|
-
|
|
1039
|
-
|
|
1040
|
-
|
|
1041
|
-
|
|
1042
|
-
|
|
1043
|
-
|
|
1044
|
-
|
|
1045
|
-
|
|
1190
|
+
On `"member": false`, stop and spawn nothing, and read why from what ran:
|
|
1191
|
+
- **`"root": null` after item 2's signup:** no root was made in `D/.aw`:
|
|
1192
|
+
the signup didn't finish. Tell the person so, with what the check
|
|
1193
|
+
shows, and don't rerun it.
|
|
1194
|
+
- **`"root": null` after a team create in item 2** (a create line, not
|
|
1195
|
+
the signup): the create recorded no root. Run the same create line
|
|
1196
|
+
again, unchanged, then check again.
|
|
1197
|
+
- **`"root": null` after item 4's invite-only form:** run item 4's
|
|
1198
|
+
listing again, read-only, and compare it with what it printed before
|
|
1199
|
+
the window opened: only a path that is new is this join's. The folder
|
|
1200
|
+
before `/.aw` is the team's label as the provider writes a team name:
|
|
1201
|
+
lowercase, each run of `_` or `.` as one `-`, and no `-` at either end
|
|
1202
|
+
(`My_Team.` is `my-team`). Write `L` that way too before you compare.
|
|
1203
|
+
- **No new path:** the join made no root here. It refused before
|
|
1204
|
+
redeeming anything, or aw's own accept failed and the join removed
|
|
1205
|
+
the empty folder it had made. Ask the person for the `E_SETUP_` code
|
|
1206
|
+
their window shows, if any (a code, no secret); with no code, ask
|
|
1207
|
+
what the window's last line says (no secret). Tell them in plain
|
|
1208
|
+
words what it means, and that a new invite is the inviter's to send.
|
|
1209
|
+
- **A new path under another name:** the invite was for that team,
|
|
1210
|
+
and this machine joined it instead: tell them so, and that an invite
|
|
1211
|
+
for `L` is the inviter's to send.
|
|
1212
|
+
- **A new path under `L`'s name:** the join began in `L`'s folder and
|
|
1213
|
+
didn't finish. Tell the person so, with what the check shows.
|
|
1214
|
+
- **`"root": null` after item 4's labelled form:** the join recorded no
|
|
1215
|
+
root: it stopped at a refusal or a failure, which its window shows.
|
|
1216
|
+
Ask for the `E_SETUP_` code there, if any, or else the window's last
|
|
1217
|
+
line (no secret), and tell the person in plain words what it means.
|
|
1218
|
+
- **With a `root`:** the run left this machine's root outside `L`. Tell
|
|
1219
|
+
the person so, with what the check shows.
|
|
1220
|
+
|
|
1221
|
+
Don't rerun the signup or the join (you can't see the join's output).
|
|
1046
1222
|
When another machine of the same name may already be in the team, say
|
|
1047
1223
|
that a taken name is a likely cause: the person who invited them can ask
|
|
1048
1224
|
their own agent whether that name is in the group (its agent reads
|
|
@@ -1146,8 +1322,10 @@ are cloned, knowledge tools, messaging wanted or not>
|
|
|
1146
1322
|
team T on aweb account N, created for the workspace, not yet attached to
|
|
1147
1323
|
the person (new workspace), or T owned by aweb account <handle>
|
|
1148
1324
|
(signed in at step 5), or new account N signed up (machine found-list),
|
|
1149
|
-
or joined L by invite (existing)
|
|
1150
|
-
|
|
1325
|
+
or joined L by invite (existing), or team T on their own aweb server U,
|
|
1326
|
+
namespace ND, aw <tested> (oats.aweb's tested version) or "aw <version>
|
|
1327
|
+
is newer than the tested <tested>; kept", its key at
|
|
1328
|
+
<team key path> | not set up (the setup expert has no messaging)
|
|
1151
1329
|
- Harness channel mode: development, confirmed by OATS at each start
|
|
1152
1330
|
(Claude with aweb) | none (Codex, pi or no messaging)
|
|
1153
1331
|
- Tasks (new workspace with aweb): oats.aweb-tasks | none: the agents use
|
|
@@ -1311,7 +1489,12 @@ the setup expert, not in this message. You are done.
|
|
|
1311
1489
|
push to a repository other than the new workspace's host they agreed to in
|
|
1312
1490
|
step 1 (step 6 creates or clones it).
|
|
1313
1491
|
- **Guess the team id:** it is the signup's `default:N.aweb.ai`, checked in
|
|
1314
|
-
step 9,
|
|
1492
|
+
step 9, step 5's answer after its sign-in, or `<workspace>:ND` on their own
|
|
1493
|
+
aweb server, checked against step 9's create.
|
|
1494
|
+
- **On their own aweb server:** make or touch the namespace's controller key
|
|
1495
|
+
(`aw id namespace prepare-controller`, `~/.awid`), set or ask for
|
|
1496
|
+
`AWEB_API_KEY`, or write a hosted `default:…aweb.ai` team or
|
|
1497
|
+
`localTeams` into the workspace.
|
|
1315
1498
|
- **Write a setup soul into the workspace:** the setup expert is
|
|
1316
1499
|
`oats.framework`'s.
|
|
1317
1500
|
- **The Desktop:** never download it through a browser, skip a verification
|