xdog-coding
Interactive coding-agent CLI.
A terminal coding agent with session management, built on
xdog-agent and the
xdog-tui rendering layer.
uv run xdog-coding
Interactive terminal
The interface uses native scrollback, one status row, and a shared multiline editor. Enter submits or queues; Shift/Alt+Enter inserts a newline. Ctrl+O opens recent tool/reasoning details: Left/Right chooses an entry and Page Up/Page Down scrolls. Escape closes autocomplete/details first, then cancels active work and restores queued text ahead of the current draft. Ctrl+Z suspends on POSIX.
Permission prompts take priority. Up/Down chooses an action, Enter confirms, Escape denies that call, and Page Up/Page Down scrolls the command summary. The editor draft stays intact when panels open or the terminal resizes. See terminal verification; remote coding and fullscreen application modes are excluded.
Tool permissions
Potentially mutating tool calls are gated immediately before execution. By
default, read-only filesystem operations and current_time run automatically;
bash, filesystem writes/edits/deletes, and unknown extension tools ask first.
xdog-coding --permission-mode ask # default: ask for dangerous calls
xdog-coding --permission-mode ask-all # ask before every tool
xdog-coding --permission-mode allow-all # trusted unattended automation
xdog-coding --permission-mode deny # allow read-only calls only
Interactive approvals offer Allow once, Allow for this session (the exact
same call only), and Deny. Non-interactive runs fail closed when no approver
is available unless allow-all was explicitly selected.
The same setting can be stored in ~/.config/xdog/coding/settings.json:
{"permission_mode": "ask"}
Permission prompts are an execution gate, not an OS sandbox: an approved shell
command still has the permissions of the xdog-coding process.
Part of xdog
This package is one piece of xdog, a
local-first toolkit for building, running and scheduling LLM workflows. The
centrepiece is xdog-flow — a typed
workflow format and compiler.
Documentation: https://xdog.942295.xyz
Licence
Copyright (c) 2026 HugeMan <942295.xyz>
GNU Affero General Public License v3.0 or later — see LICENSE.
Release files for xdog-coding 2.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| xdog_coding-2.2.0.tar.gz | 97.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xdog_coding-2.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 191.9 kB
Release files / xdog_coding-2.2.0.tar.gz
| Download URL | xdog_coding-2.2.0.tar.gz |
|---|---|
| Size | 97.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c24b0dc5e152244ece8dbca8b8afbba6597ba1524722ec3a971e7a0de9f5ebd8
|
|
BLAKE2b-256 checksum How to use checksums |
b000cdd8346e244d3c465e49e41dcd7b83664e1b6b075075e15c5e9f2f4de700
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.
Transparency logRelease files / xdog_coding-2.2.0-py3-none-any.whl
| Download URL | xdog_coding-2.2.0-py3-none-any.whl |
|---|---|
| Size | 94.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
87383ee5a4885bf72e81254761aa8f3117b41eb2312294978e949681ec581887
|
|
BLAKE2b-256 checksum How to use checksums |
de2ebad84ddfe495f29495b006a6cce0c3f13ea7fa597f32d93145c3b02fe718
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.
Transparency log