diff --git a/work-items/open/20260601-132955-tui-pod-connect-command/item.md b/work-items/open/20260601-132955-tui-pod-connect-command/item.md deleted file mode 100644 index 959bfb5d..00000000 --- a/work-items/open/20260601-132955-tui-pod-connect-command/item.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -id: 20260601-132955-tui-pod-connect-command -slug: tui-pod-connect-command -title: TUI: add command for connecting to another Pod -status: open -kind: task -priority: P2 -labels: [tui, pod, command, orchestration] -created_at: 2026-06-01T13:29:55Z -updated_at: 2026-06-01T13:29:55Z -assignee: null -legacy_ticket: null ---- - -## Background - -When a user is attached to one running Pod in the TUI, there is currently no small command-mode affordance for making another Pod reachable/contactable from that session. Existing Pod discovery/restore mechanisms exist at other layers (`ListPods`/`RestorePod`, resume picker, multi-Pod dashboard), but the single-Pod TUI command surface only exposes local commands such as `:help`, `:compact`, and `:rewind`. - -Add a `:` command that lets a user connect to another visible Pod from within the running TUI. The exact UX can be refined during implementation, but it should be command-mode based and should not make background notifications or transient socket state into durable authority. - -## Requirements - -- Add a TUI command-mode entry point for connecting to another Pod, tentatively `:pod ` or `:connect `. -- The command should use the existing Pod visibility/attach/restore authority rather than inventing a separate registry. -- It should work from a single-Pod TUI session without requiring the user to exit to a dashboard. -- It should handle at least: - - target Pod is live and attachable; - - target Pod is stopped but restorable; - - target Pod is not visible; - - current Pod is busy/streaming and command execution would be unsafe. -- The current Pod's durable history must not be rewritten or polluted merely because the user connects to another Pod. -- The UX should make it clear whether the command switches the active TUI attachment, opens a temporary contact/send operation, or enters a small Pod picker. Choose one behavior and document the rationale. -- Avoid duplicating old tool names or semantics; prefer current `ListPods` / `RestorePod`-style state concepts. -- Add focused tests for command parsing/availability and any pure model logic. If runtime socket/TUI E2E is not feasible, record the manual validation path. - -## Non-goals - -- Do not implement arbitrary Pod-to-Pod autonomous messaging unless explicitly designed. -- Do not replace the multi-Pod dashboard. -- Do not make child completion notifications authoritative. -- Do not add a new persistent relationship graph between Pods unless required by a later design. - -## Acceptance criteria - -- A user can invoke a documented `:` command from a single-Pod TUI to connect to another visible Pod by name or through a small selection flow. -- The command uses existing Pod attach/restore/discovery mechanisms and preserves Pod/session authority boundaries. -- Failure modes produce clear actionbar/command diagnostics. -- Tests cover parser/availability/model behavior, and implementation notes record any manual validation required for live attach behavior. -- Documentation/help text for TUI commands is updated. -- Validation includes relevant TUI/client tests, `./tickets.sh doctor`, `git diff --check`, and `nix build .#yoi` unless explicitly deferred with rationale. diff --git a/work-items/open/20260601-132955-tui-pod-connect-command/thread.md b/work-items/open/20260601-132955-tui-pod-connect-command/thread.md deleted file mode 100644 index 93d88942..00000000 --- a/work-items/open/20260601-132955-tui-pod-connect-command/thread.md +++ /dev/null @@ -1,7 +0,0 @@ - - -## Created - -Created by tickets.sh create. - ---- diff --git a/work-items/open/20260601-132955-tui-pod-connect-command/artifacts/.gitkeep b/work-items/open/20260601-132955-tui-register-known-pod-command/artifacts/.gitkeep similarity index 100% rename from work-items/open/20260601-132955-tui-pod-connect-command/artifacts/.gitkeep rename to work-items/open/20260601-132955-tui-register-known-pod-command/artifacts/.gitkeep diff --git a/work-items/open/20260601-132955-tui-register-known-pod-command/artifacts/clarification.md b/work-items/open/20260601-132955-tui-register-known-pod-command/artifacts/clarification.md new file mode 100644 index 00000000..49eb1067 --- /dev/null +++ b/work-items/open/20260601-132955-tui-register-known-pod-command/artifacts/clarification.md @@ -0,0 +1,5 @@ +# Clarification + +The requested command is not a TUI attach/switch affordance. It should make another existing Pod known to the currently attached Pod so that the current Pod's `ListPods` tool can see it. + +The implementation should therefore focus on Pod-authoritative visibility metadata and `ListPods` semantics, with the TUI `:` command only acting as the human-facing control path that registers that relationship. diff --git a/work-items/open/20260601-132955-tui-register-known-pod-command/item.md b/work-items/open/20260601-132955-tui-register-known-pod-command/item.md new file mode 100644 index 00000000..2302edf6 --- /dev/null +++ b/work-items/open/20260601-132955-tui-register-known-pod-command/item.md @@ -0,0 +1,57 @@ +--- +id: 20260601-132955-tui-register-known-pod-command +slug: tui-register-known-pod-command +title: TUI: add command to register a known Pod +status: open +kind: task +priority: P2 +labels: [tui, pod, command, orchestration] +created_at: 2026-06-01T13:29:55Z +updated_at: 2026-06-01T16:19:25Z +assignee: null +legacy_ticket: null +--- + +## Background + +When a user is attached to one running Pod, there is currently no user-facing way to tell that Pod about another existing Pod. As a result, the current Pod's `ListPods` tool surface only sees Pods that are already visible through its durable parent/child/current visibility state. + +The desired `:` command is not primarily a UI attach/switch command. It should make another Pod known to the currently attached Pod, so that subsequent `ListPods` calls from that Pod include the registered target and existing Pod tools such as `RestorePod` can operate on that visible Pod where appropriate. + +## Requirements + +- Add a TUI command-mode entry point for registering another Pod as known/visible to the current Pod, tentatively `:know-pod `, `:link-pod `, or similar. +- The command should send an explicit Pod/runtime method to the currently attached Pod; it must not be a TUI-only local list mutation. +- The durable effect should live in Pod current-state metadata or an equivalent Pod-authoritative visibility record so it survives reconnect/restore where appropriate. +- `ListPods` from the current Pod should include the registered Pod after the command succeeds. +- The registered relationship must be distinguishable from spawned-child delegation. It must not imply delegated filesystem scope, parent ownership, child completion notifications, or child output cursor authority unless the existing runtime explicitly supports those semantics. +- The command should resolve the target by Pod name using existing Pod metadata/live registry visibility that is available to the controller/human, then record a safe reference for the current Pod. +- Handle at least: + - target Pod is live; + - target Pod is stopped but restorable; + - target Pod name is unknown or ambiguous; + - current TUI is not attached to a Pod; + - current Pod is in a state where the registration method cannot be safely delivered. +- The current Pod's model conversation history must not be polluted merely because the user registers a known Pod. This is Pod metadata/control state, not a user message to the model. +- Provide clear command diagnostics/actionbar feedback. +- Add focused tests for command parsing, runtime method handling, metadata persistence/restore, and `ListPods` visibility behavior. If full live TUI/socket E2E is not feasible, document the manual validation path. + +## Non-goals + +- Do not implement arbitrary autonomous Pod-to-Pod messaging. +- Do not switch the TUI's active attachment as the primary behavior of this command. +- Do not replace the multi-Pod dashboard or Pod picker. +- Do not treat registered known Pods as spawned children. +- Do not make child completion notifications authoritative. +- Do not add delegated scope or reclaim behavior for known Pods unless a later design explicitly requires it. + +## Acceptance criteria + +- A user can invoke a documented `:` command from a single-Pod TUI to register another existing Pod as known to the current Pod. +- After successful registration, the current Pod's `ListPods` tool output includes the target Pod with a state/source label that does not misrepresent it as a spawned child. +- `RestorePod` or other visibility-scoped Pod tools can operate on the registered Pod according to the existing state-aware rules. +- The relationship is persisted in Pod-authoritative current state and survives ordinary TUI reconnect/Pod restore where the target remains visible/restorable. +- Failure modes produce clear diagnostics and do not modify history or create partial misleading visibility records. +- Tests cover parser/model/runtime visibility behavior, and implementation notes record any manual validation required for live TUI behavior. +- Documentation/help text for TUI commands and Pod visibility semantics is updated. +- Validation includes relevant TUI/client/pod-store/pod tests, `./tickets.sh doctor`, `git diff --check`, and `nix build .#yoi` unless explicitly deferred with rationale. diff --git a/work-items/open/20260601-132955-tui-register-known-pod-command/thread.md b/work-items/open/20260601-132955-tui-register-known-pod-command/thread.md new file mode 100644 index 00000000..134d4c42 --- /dev/null +++ b/work-items/open/20260601-132955-tui-register-known-pod-command/thread.md @@ -0,0 +1,20 @@ + + +## Created + +Created by tickets.sh create. + +--- + + + +## Decision + +# Clarification + +The requested command is not a TUI attach/switch affordance. It should make another existing Pod known to the currently attached Pod so that the current Pod's `ListPods` tool can see it. + +The implementation should therefore focus on Pod-authoritative visibility metadata and `ListPods` semantics, with the TUI `:` command only acting as the human-facing control path that registers that relationship. + + +---