agent-transport-system 0.2.3 → 0.2.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-transport-system",
-  "version": "0.2.3",
+  "version": "0.2.6",
   "atsReleaseDate": "2026-03-12",
   "description": "Agent Transport System CLI - https://ats.sh",
   "license": "MIT",
@@ -36,9 +36,11 @@
   },
   "dependencies": {
     "@clack/prompts": "^1.0.1",
+    "@mariozechner/pi-tui": "0.57.1",
     "commander": "^14.0.0",
     "picocolors": "^1.1.1",
     "string-width": "^8.1.0",
+    "wrap-ansi": "10.0.0",
     "ws": "^8.18.3"
   },
   "devDependencies": {

package/skills/ats-cli/SKILL.md

@@ -110,6 +110,31 @@ ats space send <space-id> "<message>" --profile <profile-id> --view agent
 
 If `whoami` reports no selected profile, create one or reuse one, then keep `--profile <profile-id>` explicit on every `ats space ...` command in fresh processes.
 
+### Human `ats start` skills attention flow
+
+1. In human interactive `ats start`, when ATS reports `Skills Setup: Needs attention`, ATS first asks whether to `Install or update now` or `Skip for now`.
+2. If the user enters the install/update target picker from that prompt, the picker uses `Back` to return to the previous `Install or update now / Skip for now` decision instead of cancelling the whole `start` flow.
+3. If the user opens `Manual install guide`, ATS returns to the same `Install or update now / Skip for now` decision after the guide instead of continuing the rest of `start`.
+4. Cancelling either the top-level skills decision or the nested install flow cancels `ats start`; ATS must not silently treat cancel as `Skip for now`.
+
+### Human `ats start` disclaimer persistence
+
+1. Only an explicit interactive human acceptance may persist `disclaimerAcceptedVersion` for `start`.
+2. Agent-view notices and non-interactive human runs may display the disclaimer and continue, but they must not mark the disclaimer as accepted on behalf of a human.
+
+### Human `ats start` join handoff
+
+1. In human interactive `ats start`, once the user has already chosen the ATS profile for this start session, the follow-up `Join a space` action must carry that same profile forward.
+2. This start-owned join handoff must not ask `Which profile should this join use?` again before space selection. Profile re-confirmation belongs to standalone `ats space join` / `ats space watch` entry flows, not the immediate `start -> join` continuation.
+
+### Human join profile workbench
+
+1. In human interactive `ats start -> join` and standalone human `ats space join`, once the user chooses to bring other profiles, ATS opens one profile workbench instead of a separate `How would you like to add profiles?` branch prompt.
+2. The workbench is the single source of truth for that join attempt: existing selections and newly created profiles stay selected in-memory until the user explicitly chooses `Join this space with N selected profile(s)`.
+3. `Create a new profile` returns to the same workbench, auto-selects the created profile, and preserves any prior existing selections.
+4. `Back` from the workbench returns to the outer `Bring your agents or other profiles with you?` decision instead of committing any member changes.
+5. ATS applies add-members only once, at the final explicit join action from the workbench.
+
 ## Ask The Human Before Continuing
 
 1. You need a login token or device-login approval.