xdog-coding 2.4.4__tar.gz → 2.4.6__tar.gz

{xdog_coding-2.4.4 → xdog_coding-2.4.6}/.gitignore

@@ -57,3 +57,6 @@ plan.txt
 /cli_agent_workflow.json
 /cli_agent_workflow.py
 /essay_writer.py
+
+# Goal workspaces contain local plans, task evidence and routing; never publish.
+.xdog/

{xdog_coding-2.4.4 → xdog_coding-2.4.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: xdog-coding
-Version: 2.4.4
+Version: 2.4.6
 Summary: Interactive coding agent CLI
 Project-URL: Homepage, https://xdog.942295.xyz
 Project-URL: Repository, https://github.com/litterzhang/xdog
@@ -23,11 +23,12 @@ Requires-Dist: agent-client-protocol<0.13,>=0.12.1; python_version < '3.15'
 Requires-Dist: click>=8.1.0
 Requires-Dist: pydantic>=2.0
 Requires-Dist: pyyaml>=6.0
-Requires-Dist: xdog-agent>=2.4.4
-Requires-Dist: xdog-ai[openai]>=2.4.4
-Requires-Dist: xdog-tui>=2.4.4
+Requires-Dist: xdog-agent>=2.4.6
+Requires-Dist: xdog-ai[openai]>=2.4.6
+Requires-Dist: xdog-skills>=2.4.6
+Requires-Dist: xdog-tui>=2.4.6
 Provides-Extra: skills
-Requires-Dist: xdog-skills>=2.4.4; extra == 'skills'
+Requires-Dist: xdog-skills>=2.4.6; extra == 'skills'
 Description-Content-Type: text/markdown
 
 # xdog-coding
@@ -59,6 +60,15 @@ saved model, messages and usage are preserved.
 
 ## Interactive terminal
 
+Auxiliary browsers use the main UI's existing semantic colors: warm accent
+headings and current selection, muted metadata/hints, and green/red status cues.
+This covers session/history, transcript/tool inventory, details, child/draft,
+MCP/OAuth, export review and attachment chrome, including existing nested/fullscreen
+viewers. Coding's pre-start resume picker follows the same theme. Plain mode and
+`NO_COLOR` keep these panels unstyled. Colors do not change row budgets,
+keybindings, visible-confirmation requirements, original source or exported data.
+See [panel theming](../../docs/panel-theming.md).
+
 The interface uses native scrollback, one status row, and a shared multiline
 editor. Enter submits or queues; Ctrl+Enter inserts a newline. Ctrl+O opens
 recent tool/reasoning details: Left/Right chooses an entry and Page Up/Page Down
@@ -145,6 +155,7 @@ the timer. Worker locks and cancellation signals remain separate from UI state.
 
 Potentially mutating tool calls are gated immediately before execution. By
 default, read-only filesystem operations and `current_time` run automatically;
+the exact host-bound `ext_coding_session` inspection also needs no approval;
 `bash`, filesystem writes/edits/deletes, and unknown extension tools ask first.
 
 ```bash
@@ -464,6 +475,30 @@ fallback files persist until you delete them. Kernel-blocked filesystem operatio
 cannot be forcibly interrupted; helper success may transfer clipboard ownership
 to the platform's normal persistent clipboard process.
 
+### Read-only session inspection
+
+`/session` and the built-in host extension tool `ext_coding_session` share the
+same current-session query. The tool takes `{}` and returns structured JSON:
+current session/branch/name/workspace, selected model and known capabilities,
+thinking, effective permission/read-only state, and measured context usage.
+Unknown capabilities/usage remain explicitly unavailable; selected provider/model
+configuration is not proof of a server's underlying model identity. No credentials,
+conversation bodies, file reads or settings dump are included.
+
+The instruction prefix points to this query instead of embedding mutable model,
+thinking, permission or session-ID values. Explicit tool selection still applies:
+an empty/narrowed selection does not silently re-enable inspection, and prompts
+state when the tool is unavailable. This is a Coding-owned tool, not a new Python
+plugin worker or a generic slash-command execution bridge. Its actual bound tool
+may read without frontend approval even in ask-all/deny/read-only mode; arbitrary
+extension tools and same-name replacements gain no exemption. Existing extension
+validation/vetoes remain active. Navigation/close retire old handles, and children
+do not inherit their parent's inspection callback. Neither ACP nor a TUI is needed.
+
+Session navigation normalizes title/summary/detail/error whitespace for display
+only, so embedded newlines/tabs cannot desynchronize terminal row tracking. The
+stored original text is not modified.
+
 ### MCP stdio tools (first transport slice)
 
 Global `settings.json` and project `.coding/settings.json` accept `mcp_servers`;
@@ -580,12 +615,12 @@ continuation silently reconnects, replays POSTs or expands configured disclosure
 
 ### Task planning and host read-only scope
 
-The builtin **`xdog-planning`** skill, supplied by `xdog-skills` (install the
+The builtin **`plan`** skill, supplied by `xdog-skills` (install the
 `skills` extra), uses ordinary conversation or task documents
 for objectives, dependencies, acceptance criteria and evidence-backed progress.
 It does not create a separate plan database, inspector, execution mode or model
 loop. The former `/plan`, `PlanPanel` and `update_plan` UI/tool APIs are removed.
-List it with `/skills` and activate it with `/xdog-planning [request]`.
+List it with `/skills` and activate it with `/plan [request]`.
 
 Use the native host control separately:
 
@@ -595,10 +630,11 @@ Use the native host control separately:
 /readonly off
 ```
 
-With host read-only scope on, only local `filesystem` read/ls/grep/find and
-`current_time` tool calls are eligible; shell, workspace writes, MCP/extension
-tools and child-control tools are blocked. Normal permission policy still applies
-to eligible calls. Cached approvals, `allow-all`, skill text, model arguments and
+With host read-only scope on, only local `filesystem` read/ls/grep/find,
+`current_time` calls and the host-bound `ext_coding_session` query are eligible.
+Shell, workspace writes, arbitrary MCP/extension tools and child-control tools
+are blocked. Ordinary eligible calls retain their normal permission policy;
+the exact bound session query needs no approval. Cached approvals, `allow-all`, skill text, model arguments and
 delayed approvals cannot release or bypass this restriction. Keep planning notes
 in the conversation while read-only; writing a task document still needs the
 normal write permission outside that scope.
@@ -782,7 +818,7 @@ none of these interfaces grants tool permission or full Pi API compatibility.
 TASK` inherits the current host policy; it does not copy approval grants or bypass
 read-only. Inspect with `/agents list` or `/agents inspect ID`; use `steer ID TEXT`,
 `follow-up ID TEXT`, `cancel ID`, `wait ID` and `close ID` under `/agents`.
-Parents also receive reserved `agent_spawn`/`agent_control` tools; children cannot
+Parents also receive the reserved unified `agent` tool; children cannot
 recursively delegate through their parent's supervision tools.
 
 Children share the workspace, so coordinate conflicting writes. Context is copied
@@ -2080,7 +2116,7 @@ count and `initial-task`/`crash-snapshot`/`durable-return` uncertainty are visib
 This native view has no editor, reorder/remove/return control, recovery-copy button
 or permission-confirmation action. Paste cannot submit or adopt a draft.
 
-The ordinary main-Agent `agent_control` tool retains `action="queue"` with a typed
+The ordinary main-Agent `agent` tool retains `action="queue"` with a typed
 JSON `text` request. SDK `ChildSupervisor.control("queue", ...)` also remains.
 Their edit/remove/move/text-return and explicit stopped recovery operations use the
 real owner loop and existing identity, revision, selected-input, image-byte and
@@ -2198,7 +2234,7 @@ existing limitations.
 `recover_images` remains an explicit SDK/main-Agent queue operation with exact
 input `id` and queue `revision`. `ChildSupervisor.control` returns the verified
 non-destructive `image_recovery` payload and `queue.image_receipt`; the ordinary
-`agent_control` wrapper returns typed images plus receipt/count metadata. The
+`agent` wrapper returns typed images plus receipt/count metadata. The
 text-only `recover` action refuses image-bearing inputs rather than dropping bytes.
 Running children use the separate owned live-return protocol, not stopped recovery.
 
@@ -2272,7 +2308,7 @@ SDK journaling and same-session transient editor recovery are not removed.
 The native user interface offers neither manual live queue edit/reorder/remove/
 return nor stopped task/input copy controls. Those queue operations remain in the
 permissioned main-Agent/SDK backend; native queue inspection is read-only.
-The main Agent can use its ordinary permissioned `agent_control` tool with
+The main Agent can use its ordinary permissioned `agent` tool with
 `action="queue"` and a JSON `text` request containing `return_prepare`,
 `return_commit` or `return_cancel` plus the required input/revision/receipt fields.
 Preparation returns typed image content and bounded token/receipt metadata; it
@@ -2715,8 +2751,31 @@ exactly-once execution or an OS security sandbox. No existing user data is migra
 or discarded automatically.
 
 Enabled extensions may declare a public slash name. The packaged `goal_ui`
-display exposes `/goals [GOAL_ID | page OFFSET]`; `/goal` remains the skill name.
+display exposes `/goals [GOAL_ID | page OFFSET]`; default native `/goal` manages the current Goal.
 This is generic extension routing, not a Coding-specific Goal command. Public
-names appear in help/completion and cannot shadow builtin or skill commands;
+names appear in help/completion and cannot shadow builtins or other owners; native installed capabilities
+may explicitly overlap only their own skill command entry, without preventing skill loading;
 model tool names and permissions do not change. See
 `docs/extension-public-commands.md` for the shared Coding/Claw contract.
+
+
+### Installed capability code boundaries
+
+Trusted installed native capabilities use generic owner, lifecycle event, ACP
+routing and receipt ports. Coding/Claw default dependencies include xdog-skills:
+`/goal` commands and the model tool are available without a display-worker setting
+or Goal enable flag. The packaged skill remains discoverable/loadable. No Goal is
+created merely by installation or ordinary chat.
+
+Goal owns one current binding/history, task files and ACP reminders. The current
+main Agent plans, executes itself or uses existing child tools, updates tasks and
+judges completion according to the skill. No Goal-owned worker/reviewer scheduler
+or independent acceptance protocol remains. Tasks/*.json are authoritative, not
+projections of duplicate database task state. Pauses and user/host waits cannot be
+released by an automatic message. Existing readonly/permissions/approval checks
+remain in force. Eyes watches only the generated task directory configuration;
+stopping Goal automation does not cancel unrelated observers or accepted work.
+
+See `docs/goal-simple-design.md` and its requirement/verification record. Earlier
+capability-boundary and Goal reviewer lifecycle evidence describes its old frozen
+implementation, not the current Goal contract.

{xdog_coding-2.4.4 → xdog_coding-2.4.6}/README.md

@@ -27,6 +27,15 @@ saved model, messages and usage are preserved.
 
 ## Interactive terminal
 
+Auxiliary browsers use the main UI's existing semantic colors: warm accent
+headings and current selection, muted metadata/hints, and green/red status cues.
+This covers session/history, transcript/tool inventory, details, child/draft,
+MCP/OAuth, export review and attachment chrome, including existing nested/fullscreen
+viewers. Coding's pre-start resume picker follows the same theme. Plain mode and
+`NO_COLOR` keep these panels unstyled. Colors do not change row budgets,
+keybindings, visible-confirmation requirements, original source or exported data.
+See [panel theming](../../docs/panel-theming.md).
+
 The interface uses native scrollback, one status row, and a shared multiline
 editor. Enter submits or queues; Ctrl+Enter inserts a newline. Ctrl+O opens
 recent tool/reasoning details: Left/Right chooses an entry and Page Up/Page Down
@@ -113,6 +122,7 @@ the timer. Worker locks and cancellation signals remain separate from UI state.
 
 Potentially mutating tool calls are gated immediately before execution. By
 default, read-only filesystem operations and `current_time` run automatically;
+the exact host-bound `ext_coding_session` inspection also needs no approval;
 `bash`, filesystem writes/edits/deletes, and unknown extension tools ask first.
 
 ```bash
@@ -432,6 +442,30 @@ fallback files persist until you delete them. Kernel-blocked filesystem operatio
 cannot be forcibly interrupted; helper success may transfer clipboard ownership
 to the platform's normal persistent clipboard process.
 
+### Read-only session inspection
+
+`/session` and the built-in host extension tool `ext_coding_session` share the
+same current-session query. The tool takes `{}` and returns structured JSON:
+current session/branch/name/workspace, selected model and known capabilities,
+thinking, effective permission/read-only state, and measured context usage.
+Unknown capabilities/usage remain explicitly unavailable; selected provider/model
+configuration is not proof of a server's underlying model identity. No credentials,
+conversation bodies, file reads or settings dump are included.
+
+The instruction prefix points to this query instead of embedding mutable model,
+thinking, permission or session-ID values. Explicit tool selection still applies:
+an empty/narrowed selection does not silently re-enable inspection, and prompts
+state when the tool is unavailable. This is a Coding-owned tool, not a new Python
+plugin worker or a generic slash-command execution bridge. Its actual bound tool
+may read without frontend approval even in ask-all/deny/read-only mode; arbitrary
+extension tools and same-name replacements gain no exemption. Existing extension
+validation/vetoes remain active. Navigation/close retire old handles, and children
+do not inherit their parent's inspection callback. Neither ACP nor a TUI is needed.
+
+Session navigation normalizes title/summary/detail/error whitespace for display
+only, so embedded newlines/tabs cannot desynchronize terminal row tracking. The
+stored original text is not modified.
+
 ### MCP stdio tools (first transport slice)
 
 Global `settings.json` and project `.coding/settings.json` accept `mcp_servers`;
@@ -548,12 +582,12 @@ continuation silently reconnects, replays POSTs or expands configured disclosure
 
 ### Task planning and host read-only scope
 
-The builtin **`xdog-planning`** skill, supplied by `xdog-skills` (install the
+The builtin **`plan`** skill, supplied by `xdog-skills` (install the
 `skills` extra), uses ordinary conversation or task documents
 for objectives, dependencies, acceptance criteria and evidence-backed progress.
 It does not create a separate plan database, inspector, execution mode or model
 loop. The former `/plan`, `PlanPanel` and `update_plan` UI/tool APIs are removed.
-List it with `/skills` and activate it with `/xdog-planning [request]`.
+List it with `/skills` and activate it with `/plan [request]`.
 
 Use the native host control separately:
 
@@ -563,10 +597,11 @@ Use the native host control separately:
 /readonly off
 ```
 
-With host read-only scope on, only local `filesystem` read/ls/grep/find and
-`current_time` tool calls are eligible; shell, workspace writes, MCP/extension
-tools and child-control tools are blocked. Normal permission policy still applies
-to eligible calls. Cached approvals, `allow-all`, skill text, model arguments and
+With host read-only scope on, only local `filesystem` read/ls/grep/find,
+`current_time` calls and the host-bound `ext_coding_session` query are eligible.
+Shell, workspace writes, arbitrary MCP/extension tools and child-control tools
+are blocked. Ordinary eligible calls retain their normal permission policy;
+the exact bound session query needs no approval. Cached approvals, `allow-all`, skill text, model arguments and
 delayed approvals cannot release or bypass this restriction. Keep planning notes
 in the conversation while read-only; writing a task document still needs the
 normal write permission outside that scope.
@@ -750,7 +785,7 @@ none of these interfaces grants tool permission or full Pi API compatibility.
 TASK` inherits the current host policy; it does not copy approval grants or bypass
 read-only. Inspect with `/agents list` or `/agents inspect ID`; use `steer ID TEXT`,
 `follow-up ID TEXT`, `cancel ID`, `wait ID` and `close ID` under `/agents`.
-Parents also receive reserved `agent_spawn`/`agent_control` tools; children cannot
+Parents also receive the reserved unified `agent` tool; children cannot
 recursively delegate through their parent's supervision tools.
 
 Children share the workspace, so coordinate conflicting writes. Context is copied
@@ -2048,7 +2083,7 @@ count and `initial-task`/`crash-snapshot`/`durable-return` uncertainty are visib
 This native view has no editor, reorder/remove/return control, recovery-copy button
 or permission-confirmation action. Paste cannot submit or adopt a draft.
 
-The ordinary main-Agent `agent_control` tool retains `action="queue"` with a typed
+The ordinary main-Agent `agent` tool retains `action="queue"` with a typed
 JSON `text` request. SDK `ChildSupervisor.control("queue", ...)` also remains.
 Their edit/remove/move/text-return and explicit stopped recovery operations use the
 real owner loop and existing identity, revision, selected-input, image-byte and
@@ -2166,7 +2201,7 @@ existing limitations.
 `recover_images` remains an explicit SDK/main-Agent queue operation with exact
 input `id` and queue `revision`. `ChildSupervisor.control` returns the verified
 non-destructive `image_recovery` payload and `queue.image_receipt`; the ordinary
-`agent_control` wrapper returns typed images plus receipt/count metadata. The
+`agent` wrapper returns typed images plus receipt/count metadata. The
 text-only `recover` action refuses image-bearing inputs rather than dropping bytes.
 Running children use the separate owned live-return protocol, not stopped recovery.
 
@@ -2240,7 +2275,7 @@ SDK journaling and same-session transient editor recovery are not removed.
 The native user interface offers neither manual live queue edit/reorder/remove/
 return nor stopped task/input copy controls. Those queue operations remain in the
 permissioned main-Agent/SDK backend; native queue inspection is read-only.
-The main Agent can use its ordinary permissioned `agent_control` tool with
+The main Agent can use its ordinary permissioned `agent` tool with
 `action="queue"` and a JSON `text` request containing `return_prepare`,
 `return_commit` or `return_cancel` plus the required input/revision/receipt fields.
 Preparation returns typed image content and bounded token/receipt metadata; it
@@ -2683,8 +2718,31 @@ exactly-once execution or an OS security sandbox. No existing user data is migra
 or discarded automatically.
 
 Enabled extensions may declare a public slash name. The packaged `goal_ui`
-display exposes `/goals [GOAL_ID | page OFFSET]`; `/goal` remains the skill name.
+display exposes `/goals [GOAL_ID | page OFFSET]`; default native `/goal` manages the current Goal.
 This is generic extension routing, not a Coding-specific Goal command. Public
-names appear in help/completion and cannot shadow builtin or skill commands;
+names appear in help/completion and cannot shadow builtins or other owners; native installed capabilities
+may explicitly overlap only their own skill command entry, without preventing skill loading;
 model tool names and permissions do not change. See
 `docs/extension-public-commands.md` for the shared Coding/Claw contract.
+
+
+### Installed capability code boundaries
+
+Trusted installed native capabilities use generic owner, lifecycle event, ACP
+routing and receipt ports. Coding/Claw default dependencies include xdog-skills:
+`/goal` commands and the model tool are available without a display-worker setting
+or Goal enable flag. The packaged skill remains discoverable/loadable. No Goal is
+created merely by installation or ordinary chat.
+
+Goal owns one current binding/history, task files and ACP reminders. The current
+main Agent plans, executes itself or uses existing child tools, updates tasks and
+judges completion according to the skill. No Goal-owned worker/reviewer scheduler
+or independent acceptance protocol remains. Tasks/*.json are authoritative, not
+projections of duplicate database task state. Pauses and user/host waits cannot be
+released by an automatic message. Existing readonly/permissions/approval checks
+remain in force. Eyes watches only the generated task directory configuration;
+stopping Goal automation does not cancel unrelated observers or accepted work.
+
+See `docs/goal-simple-design.md` and its requirement/verification record. Earlier
+capability-boundary and Goal reviewer lifecycle evidence describes its old frozen
+implementation, not the current Goal contract.

{xdog_coding-2.4.4 → xdog_coding-2.4.6}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "xdog-coding"
-version = "2.4.4"
+version = "2.4.6"
 description = "Interactive coding agent CLI"
 requires-python = ">=3.12"
 classifiers = [
@@ -22,17 +22,18 @@ readme = "README.md"
 license = "AGPL-3.0-or-later"
 license-files = ["LICENSE", "LICENSE-EXCEPTION.md"]
 dependencies = [
-    "xdog-ai[openai]>=2.4.4",
-    "xdog-agent>=2.4.4",
+    "xdog-ai[openai]>=2.4.6",
+    "xdog-agent>=2.4.6",
+    "xdog-skills>=2.4.6",
     "agent-client-protocol>=0.12.1,<0.13; python_version < '3.15'",
-    "xdog-tui>=2.4.4",
+    "xdog-tui>=2.4.6",
     "pyyaml>=6.0",
     "click>=8.1.0",
     "pydantic>=2.0",
 ]
 
 [project.optional-dependencies]
-skills = ["xdog-skills>=2.4.4"]
+skills = ["xdog-skills>=2.4.6"]
 
 [project.urls]
 Homepage = "https://xdog.942295.xyz"

{xdog_coding-2.4.4 → xdog_coding-2.4.6}/src/xdog/coding/__init__.py

@@ -1,3 +1,3 @@
 """coding - Interactive coding agent CLI."""
 
-__version__ = "2.4.4"
+__version__ = "2.4.6"

{xdog_coding-2.4.4 → xdog_coding-2.4.6}/src/xdog/coding/cli/session_picker.py

@@ -8,10 +8,11 @@ from pathlib import Path
 
 import click
 from xdog.coding.core.session_manager import SessionManager, SessionMeta
+from xdog.coding.modes.interactive.theme import create_default_theme
 from xdog.tui.components.select_list import SelectItem, SelectList
 from xdog.tui.keys import KeyEvent
 from xdog.tui.tui import TUI
-from xdog.tui.utils import sanitize_terminal_text, truncate_to_width
+from xdog.tui.utils import sanitize_terminal_text
 
 
 def _format_session(meta: SessionMeta, idx: int) -> str:
@@ -30,8 +31,10 @@ class SessionPicker(SelectList[str]):
     def __init__(self, sessions: list[SessionMeta], directory: Path) -> None:
         # Preserve newest-first ordering within each group, without claiming legacy ownership.
         sessions = sorted(sessions, key=lambda meta: not bool(meta.working_dir))
+        self.theme = create_default_theme()
         super().__init__([SelectItem(label=_format_session(meta, idx), value=meta.session_id)
-                          for idx, meta in enumerate(sessions, 1)])
+                          for idx, meta in enumerate(sessions, 1)],
+                         selected_fn=lambda text: text, description_fn=lambda text: text, scroll_fn=lambda text: text)
         self.directory = directory
         self.height = 24
 
@@ -39,11 +42,12 @@ class SessionPicker(SelectList[str]):
         self.height = max(1, height)
 
     def render(self, width: int) -> list[str]:
-        title = [f"Resume session · {sanitize_terminal_text(str(self.directory))}"] if self.height >= 4 else []
+        title = ["Resume session · " + " ".join(
+            sanitize_terminal_text(str(self.directory)).split())] if self.height >= 4 else []
         hints = ["↑/↓ choose · PgUp/PgDn page · Enter resume · Esc cancel"] if self.height >= 3 else []
         self._max_visible = max(1, self.height - len(title) - len(hints) - 1)
         rows = title + super().render(width)[:self.height - len(title) - len(hints)] + hints
-        return [truncate_to_width(row, max(0, width), "…") for row in rows]
+        return self.theme.panel_theme().rows(rows, width, header=bool(title), footer=bool(hints), ellipsis="…")
 
     def handle_input(self, event: KeyEvent) -> bool:
         if event.key in ("pageup", "pagedown", "home", "end"):

{xdog_coding-2.4.4 → xdog_coding-2.4.6}/src/xdog/coding/config.py

@@ -51,7 +51,7 @@ def validate_max_messages_per_turn(value: object) -> int:
 
 MONOREPO_NAME = "xdog"
 APP_NAME = "coding"
-VERSION = "2.4.4"
+VERSION = "2.4.6"
 PROJECT_DIR_NAME = ".coding"
 ENV_OVERRIDE = "CODING_DIR"