dotagents-cli 0.3.0__tar.gz → 0.3.2__tar.gz

{dotagents_cli-0.3.0 → dotagents_cli-0.3.2}/.gitignore

@@ -34,3 +34,7 @@ Thumbs.db
 .idea/
 .vscode/
 _staging/
+
+# `overlays` branch, checked out here as a worktree/clone for local editing
+# (D77: example overlays split off this repo's main branch).
+overlays/

{dotagents_cli-0.3.0 → dotagents_cli-0.3.2}/CHANGELOG.md

@@ -7,6 +7,106 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [0.3.2] - 2026-07-25
+
+### Added
+
+- feat: **`AntigravityAgent`** — context injection for Google's Antigravity
+  CLI/IDE (a separate product from Gemini CLI, despite sharing the `~/.gemini/`
+  namespace for some files). Antigravity's hooks have no `SessionStart`
+  equivalent — only `PreToolUse`/`PostToolUse`/`PreInvocation`/`PostInvocation`/
+  `Stop` — so a `PreInvocation` hook gated on `invocationNum == 0` behaves like a
+  one-shot context load instead of resending it every model turn. Wires into
+  `~/.gemini/config/hooks.json`. No detection marker exists for Antigravity, so
+  it's explicit-`--agents antigravity`-only, never auto-detected.
+- feat: **Codex gets a `PreToolUse` env hook**, closing the one gap Codex had
+  versus Claude: Codex has no per-session env-persistence mechanism at any hook
+  event, so a deployed script prepends a guarded env-loader to every `Bash` tool
+  call via `updatedInput.command` — the same rewrite mechanism Claude's own
+  `PreToolUse` hook uses, confirmed directly against Codex's docs.
+- feat: **`init` wires a PowerShell `PreToolUse` env hook on Windows**, closing
+  a real gap: `$CLAUDE_ENV_FILE` only reaches Claude's *Bash* tool
+  (`$env:CLAUDE_ENV_FILE` is empty inside a live PowerShell tool call, confirmed
+  directly) — a fresh PowerShell tool call gets none of the SessionStart env.
+  The hook prepends a guarded env-loader to a PowerShell tool call's own command,
+  shipped as an inline command string (never a `.ps1` file — a script file is
+  subject to PowerShell's execution policy, and dotagents has no code-signing
+  certificate; the inline form runs even under `Restricted`).
+- feat: **`SessionStart`/`CwdChanged` now register two handlers each** — a
+  bash-syntax one and an explicit `shell: "powershell"` one — because Claude's
+  own hooks.md says the shell "defaults to bash, or to powershell on Windows
+  when Git Bash isn't installed": bash syntax fed to `powershell -Command` on
+  such a machine is a hard parse error, silently losing both env and context for
+  the whole session.
+- feat: **`DotAgentsArgs`** (`dotagents.cli`, re-exported for overlay-shipped
+  commands) — one shared `-g/--global` + `--agents-dir` base class. `init` and
+  all four `overlays` subcommands now inherit it instead of independently
+  redeclaring the same fields, so scope resolution can't silently drift between
+  commands (one previously defaulted `agents_dir` eagerly to `Path.home() /
+  ".agents"`; harmless in practice, but needless).
+
+### Fixed
+
+- fix: **`dotagents env --format powershell`/`cmd` left an already-POSIX `PATH`
+  unconverted**, the mirror of the export/dotenv/fish fix below going the other
+  direction. Found live: run from a genuine Windows PowerShell terminal whose
+  own inherited `PATH` already held WSL/MSYS-mount-style entries
+  (`/mnt/c/Program Files/...`), the emitted `${env:PATH} = '...'` was
+  syntactically valid PowerShell but a single opaque colon-joined string, not
+  the `;`-split list PowerShell's own PATH lookup needs — every subsequent
+  bare-command lookup broke for that session. Also handles the MIXED case
+  (dotagents' own native bin dirs prepended onto an already-POSIX inherited
+  PATH, one string with both separators at once), caught by sourcing real
+  output into a live PowerShell session and watching `git.exe` fail to
+  resolve before the second fix. A WSL-only segment with no Windows equivalent
+  (`/usr/bin`) is dropped rather than mangled into a broken relative path.
+- fix: **the built `.pyz` degraded `-g` on any discovered command inheriting a
+  dotagents-defined base class** (first hit by `DotAgentsArgs` above) — duho's
+  AST introspection walks the full MRO for a command's flags, but the zipapp
+  source-repoint shim only ever covered built-in command modules, not a base
+  class's own module (`dotagents.cli._common`). `--global` degraded to the
+  name-derived `--global-scope` and `-g` vanished silently. Fixed, with new CI
+  coverage asserting the exact short flag survives a real built pyz.
+- fix: **`harness_loads` relative entries matched by bare filename, not full
+  path** — a relative entry like Codex's `"AGENTS.md"` wrongly suppressed ANY
+  file sharing that basename anywhere on disk, including the unrelated
+  `~/.agents/AGENTS.md` user-store file Codex's harness never reads.
+  `dotagents context --agents codex` emitted an empty `sources: []` even with
+  real content present. Now resolved against `project_root` and compared by
+  full path, like the absolute (`~/`, `/`) forms already were.
+- fix: `dotagents context --format json` crashed with `UnicodeEncodeError` on
+  any character outside Latin-1 (a bare `print()` encoding with the console's
+  codepage) — the same class of bug already fixed for the markdown path, just
+  never covered for JSON.
+- fix: PowerShell format uses `${env:NAME}` (curly-brace form), not the bare
+  `$env:NAME` sigil — a handful of real Windows env vars have parens in their
+  names (`ProgramFiles(x86)`), and `$env:FOO(X86) = ...` is a PowerShell parse
+  error; the curly-brace form is valid for every name.
+
+## [0.3.1] - 2026-07-24
+
+### Fixed
+
+- fix: **`dotagents env --format export`/`dotenv`/`fish` now emit a POSIX PATH on
+  Windows**, instead of the OS-native `C:\...;C:\...` form. This is the exact
+  command the Claude `SessionStart` hook appends into `$CLAUDE_ENV_FILE`, which
+  Claude sources before *every* subsequent Bash tool call in the session — an
+  unconverted PATH broke command lookup (`git`, `grep`, `head`, `python`, ...) for
+  the rest of the session once poisoned, not just once. PATH-shaped values are
+  now converted per segment: backslash to forward-slash, `;` to `:`, and a drive
+  letter to its MSYS mount point (`C:/...` -> `/c/...` — required for PATH
+  *lookups* specifically; slash direction alone does not work in MSYS2/Cygwin
+  bash). `PATHEXT` is dropped (no POSIX meaning). A handful of real Windows env
+  vars with parentheses in their names (`ProgramFiles(x86)`) are also dropped for
+  these formats — `export FOO(X86)=...` is a bash syntax error, not a bad value,
+  and aborts sourcing the rest of the file. `powershell`/`cmd`/`json`/`ini`/`yaml`
+  are unaffected.
+- fix: a UNC PATH segment (`\\server\share\...`) no longer collapses to a single
+  leading slash (`/server/share/...`) during the POSIX conversion above — MSYS
+  requires the double-slash UNC root (`//server/share/...`) to resolve it.
+
+Patch release: the PATH/POSIX-conversion fix above (the only change since 0.3.0).
+
 ## [0.3.0] - 2026-07-24
 
 ### Changed

{dotagents_cli-0.3.0 → dotagents_cli-0.3.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dotagents-cli
-Version: 0.3.0
+Version: 0.3.2
 Summary: The dotagents CLI: install and manage a portable ~/.agents config for AI coding agents
 Project-URL: Homepage, https://github.com/jose-pr/dotagents/
 Project-URL: Repository, https://github.com/jose-pr/dotagents
@@ -62,6 +62,7 @@ Description-Content-Type: text/markdown
 # dotagents
 
 [![Test](https://img.shields.io/github/actions/workflow/status/jose-pr/dotagents/test.yml?branch=main&label=tests)](https://github.com/jose-pr/dotagents/actions/workflows/test.yml)
+[![PyPI](https://img.shields.io/pypi/v/dotagents-cli.svg)](https://pypi.org/project/dotagents-cli/)
 [![Documentation](https://img.shields.io/badge/docs-online-blue.svg)](https://jose-pr.github.io/dotagents/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://github.com/jose-pr/dotagents/blob/main/LICENSE)
 
@@ -123,8 +124,13 @@ manifest read by the `dotagents overlays` subcommand, which manages overlays by
 
 ## Install
 
-**`dotagents init`** lays down the neutral base config; a self-contained downloadable
-`.pyz` needs no `pip install` at all.
+```bash
+pip install dotagents-cli   # gives you `import dotagents` and the `dotagents` command
+```
+
+Or skip `pip` entirely with the self-contained downloadable `.pyz` (see below).
+
+**`dotagents init`** lays down the neutral base config.
 
 `init` writes the `.agents/` scaffolding — the `AGENTS.md` managed block, the per-agent
 `<CLAUDE|ANTIGRAVITY|...>.md → @AGENTS.md` pattern, the design-log convention — and

{dotagents_cli-0.3.0 → dotagents_cli-0.3.2}/README.md

@@ -1,6 +1,7 @@
 # dotagents
 
 [![Test](https://img.shields.io/github/actions/workflow/status/jose-pr/dotagents/test.yml?branch=main&label=tests)](https://github.com/jose-pr/dotagents/actions/workflows/test.yml)
+[![PyPI](https://img.shields.io/pypi/v/dotagents-cli.svg)](https://pypi.org/project/dotagents-cli/)
 [![Documentation](https://img.shields.io/badge/docs-online-blue.svg)](https://jose-pr.github.io/dotagents/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://github.com/jose-pr/dotagents/blob/main/LICENSE)
 
@@ -62,8 +63,13 @@ manifest read by the `dotagents overlays` subcommand, which manages overlays by
 
 ## Install
 
-**`dotagents init`** lays down the neutral base config; a self-contained downloadable
-`.pyz` needs no `pip install` at all.
+```bash
+pip install dotagents-cli   # gives you `import dotagents` and the `dotagents` command
+```
+
+Or skip `pip` entirely with the self-contained downloadable `.pyz` (see below).
+
+**`dotagents init`** lays down the neutral base config.
 
 `init` writes the `.agents/` scaffolding — the `AGENTS.md` managed block, the per-agent
 `<CLAUDE|ANTIGRAVITY|...>.md → @AGENTS.md` pattern, the design-log convention — and

{dotagents_cli-0.3.0 → dotagents_cli-0.3.2}/pyproject.toml

@@ -9,7 +9,7 @@ build-backend = "hatchling.build"
 # redirect/placeholder before someone else does, but the CLI ships under -cli.
 [project]
 name = "dotagents-cli"
-version = "0.3.0"
+version = "0.3.2"
 authors = [{ name = "Jose A." }]
 description = "The dotagents CLI: install and manage a portable ~/.agents config for AI coding agents"
 readme = "README.md"

{dotagents_cli-0.3.0 → dotagents_cli-0.3.2}/src/dotagents/AGENTS.md

@@ -59,13 +59,86 @@ can read it without the source. Full docs: https://jose-pr.github.io/dotagents/
   `hooks.<Event>` is a **list of matcher-objects** each holding its own `hooks` list,
   not a flat command list. Foreign hooks are preserved verbatim, malformed entries
   are dropped rather than raising, and invalid JSON raises `SystemExit` instead of
-  silently overwriting the user's file. Pure stdlib. Consumed by
+  silently overwriting the user's file. `shell` (Claude: `"bash"`/`"powershell"`,
+  picks the interpreter for the hook's own command) and `command_windows`
+  (Codex: emitted as `commandWindows`, a separate Windows-only command OVERRIDE,
+  not an interpreter choice) are both supported. Pure stdlib. Consumed by
   `ClaudeAgent.wire_hooks` (`~/.claude/settings.json`: env via `$CLAUDE_ENV_FILE`
-  + context via stdout, plus `CwdChanged`) and `CodexAgent.wire_hooks`
-  (`<CODEX_HOME|~/.codex>/hooks.json`: context only — no env-file equivalent — and
-  never `config.toml`). Codex's hook JSON is structurally identical to Claude's, so
-  the same merge serves both. Gemini/Cursor/Copilot keep the base no-op: no
-  published schema to target.
+  + context via stdout, plus `CwdChanged`, plus a `PreToolUse` env-loader for the
+  PowerShell tool) and `CodexAgent.wire_hooks` (`<CODEX_HOME|~/.codex>/hooks.json`,
+  never `config.toml`: `SessionStart` context-only, plus a `PreToolUse` env-loader
+  matched on `matcher: "Bash"`). Codex's hook JSON is structurally identical to
+  Claude's, including the SAME `updatedInput.command` rewrite mechanism on
+  `PreToolUse` — confirmed directly against Codex's own docs
+  (learn.chatgpt.com/docs/hooks), not assumed from Claude parity.
+  Gemini/Cursor/Copilot keep the base no-op — Gemini CLI proper has no hook
+  mechanism documented at all (checked directly). **Antigravity is a separate
+  product** from Gemini CLI (Antigravity CLI/IDE/SDK family, shares only the
+  `~/.gemini/` namespace for some files) and DOES wire a hook: see
+  `AntigravityAgent.wire_hooks` below. `PreToolUse` there is still allow/deny/ask
+  only — no `updatedInput`, so no command-rewrite/env-loader path exists to hang
+  on it, unlike Claude/Codex. Revisit both conclusions if either framework changes.
+- **`AntigravityAgent.wire_hooks`** (`<AGENTS_HOME_ANTIGRAVITY|~/.gemini/config>/hooks.json`,
+  keyed under a `"dotagents"` name per the docs' own example shape — a named-entry
+  object, not Claude/Codex's flat `hooks.<Event>`): wires a single `PreInvocation`
+  entry, context-only, no env mechanism. Antigravity's hooks
+  (antigravity.google/docs/hooks) have exactly five events — `PreToolUse`,
+  `PostToolUse`, `PreInvocation`, `PostInvocation`, `Stop` — no SessionStart
+  equivalent. `PreInvocation` fires every model turn (`invocationNum`, 0-indexed),
+  so the deployed script (`preinvocation_antigravity_context.py`,
+  `_overlay/dotagents/hooks/`) gates on `invocationNum == 0` to behave like a
+  one-shot SessionStart rather than resending context every turn. Output shape is
+  a bare `{"injectSteps": [{"ephemeralMessage": "..."}]}`, no `hookSpecificOutput`
+  wrapper — confirmed against the primary docs after an earlier pass here wrongly
+  concluded no useful injection was possible; `ephemeralMessage` is the one of the
+  three step types meant for free text (`toolCall` executes a tool,
+  `userMessage` impersonates the user). No detection marker exists anywhere in
+  Antigravity's docs, so `detect_env_vars = []` — explicit `--agents antigravity`
+  only, same posture as Codex's env-block precedent (writes touching an agent's
+  own live config are opt-in, never inferred).
+- **`SessionStart`/`CwdChanged` register TWO handlers each**, bash-syntax
+  (default shell) and a PowerShell-native equivalent (`shell: "powershell"`).
+  hooks.md: `shell` "Defaults to bash, or to powershell on Windows when Git Bash
+  isn't installed" — verified directly that bash syntax fed to `powershell
+  -Command` on such a machine is a hard parse error, not a soft failure, so
+  every session there would silently get neither env nor context. Every handler
+  in a matched group fires unconditionally (hooks.md), so both always run; the
+  one whose interpreter is absent fails harmlessly. The PowerShell
+  `SessionStart` variant is context-only (`dotagents context`), not
+  env+context: `$CLAUDE_ENV_FILE`'s documented effect is "subsequent BASH
+  commands" regardless of which shell wrote it, so writing to it from a
+  PowerShell-shelled hook would feed nothing.
+- **Windows only**: `ClaudeAgent._wire_powershell_pretooluse` additionally wires
+  a no-matcher `PreToolUse` hook (fires on every tool call), `shell:
+  "powershell"`, running `PRETOOLUSE_POWERSHELL_COMMAND` INLINE — deliberately
+  not a `.ps1` file, since a script file is subject to PowerShell's execution
+  policy (RemoteSigned/AllSigned/Restricted) and dotagents has no code-signing
+  certificate; verified directly that the inline form runs successfully even
+  under `Restricted`, which blocks every `.ps1` file outright. Closes a real
+  gap: `$CLAUDE_ENV_FILE` is Bash-tool-only (confirmed empirically that
+  `$env:CLAUDE_ENV_FILE` is empty inside a live PowerShell tool call), so the
+  SessionStart env half never reaches the PowerShell tool. Uses `PreToolUse`'s
+  `updatedInput` to prepend a guarded env-loader (`AGENTS_RUNTIME_SET`,
+  matching the precursor's convention) to a `PowerShell` tool call's own
+  command — not by trying to persist state across hook invocations, which are
+  each their own fresh process and cannot. Whether the guard is visible across
+  separate PowerShell tool calls is UNVERIFIED. Every literal `\` in the
+  command constant must be a raw string — a bare `\b` in a normal Python string
+  literal silently becomes a backspace character, corrupting the emitted path;
+  caught once by testing a draft through a real PowerShell spawn.
+- **`CodexAgent._deploy_pretooluse_script`** covers the same env gap for Codex,
+  which has NO env-persistence mechanism at any hook event (not Bash-only like
+  Claude — none). Ships `pretooluse_codex_env.py` (`_overlay/dotagents/hooks/`),
+  deployed to `<codex-home>/hooks/` (create-or-refresh), wired as `PreToolUse`
+  with `matcher: "Bash"` — Codex's one shell tool, so (unlike Claude's
+  no-matcher hook) filtering happens at the settings level, no runtime
+  `tool_name` check needed in the script. A FILE, not inlined like Claude's:
+  Codex's docs show every hook example as `python3 <path>`, and a `.py` file
+  has no execution-policy/signing concern (PowerShell-specific). Sets
+  `commandWindows` to `python "<path>"` (not `python3`) — verified directly
+  that `python3` resolves to the Microsoft Store app-execution-alias stub and
+  fails outright on this dev machine (exit 49), the same trap noted elsewhere
+  for `py`/venv creation.
 - `_sync` — `PathSyncer` wrapper reproducing `install`'s backup/copy/report; requires
   `pathlib_next.Path` instances (not plain `pathlib.Path`) and a pre-created parent dir.
 

{dotagents_cli-0.3.0 → dotagents_cli-0.3.2}/src/dotagents/__init__.py

@@ -1,3 +1,3 @@
 """dotagents: installable CLI for the dotagents agent-config payload."""
 
-__version__ = "0.2.0"
+__version__ = "0.3.2"