pulse-coding-agent 0.1.0__tar.gz → 0.1.2__tar.gz

{pulse_coding_agent-0.1.0 → pulse_coding_agent-0.1.2}/.gitignore

@@ -1,7 +1,6 @@
 # Secrets and machine-specific configuration
 .env
 .env.*
-!.env.example
 *.pem
 *.key
 *.p12

{pulse_coding_agent-0.1.0 → pulse_coding_agent-0.1.2}/CHANGELOG.md

@@ -1,52 +1,82 @@
-# Changelog
-
-All notable changes are recorded here. Pulse follows Semantic Versioning while
-pre-1.0 APIs may change with release notes and migration guidance.
-
-## [Unreleased]
-
-### Added
-
-- Post-login BYOK onboarding now guides provider and model selection before
-  collecting the selected provider key through hidden terminal input.
-- Provider keys are stored in workspace-scoped native OS credential-vault
-  entries, with safe status, rotation, and removal through `pulse keys`.
-
-### Changed
-
-- Successful key set or rotation migrates that provider away from a legacy
-  plaintext workspace `.env` entry without ever displaying the secret.
-
-## [0.1.0] - 2026-08-29
-
-### Added
-
-- Permissioned local coding-agent CLI with repository intelligence, durable
-  tasks, conversations, mutation tracking, provider routing, and loopback RPC.
-- Docker and authenticated remote sandbox implementations with policy,
-  resource, filesystem, network, secret-redaction, and recovery tests.
-- Configured remote execution is preferred on client machines, with local
-  Docker/Podman used as the secure fallback and no implicit host execution.
-- Production doctor, correlation IDs, remote health/readiness endpoints,
-  operations/security documentation, and explicit deployment boundaries.
-- Reproducible wheel/source builds, artifact-content verification, clean-install
-  smoke tests, cross-platform CI, coverage gate, dependency audit, secret scan,
-  OIDC trusted-publishing workflow, release checksums, source manifest, and
-  CycloneDX SBOM.
-- Direct application dependencies pinned to the versions exercised by the
-  release suite, preventing unreviewed major-version drift at installation.
-- Explicit live-Docker test markers, a single no-skip Docker security gate, and
-  stable Windows pytest teardown behavior in hosted CI.
-- Public `version` and secure provider-key rotation commands, simplified OAuth
-  login/logout UX, authenticated Google userinfo verification, and literal-safe
-  terminal rendering for untrusted text.
-- Non-root Docker overlay export that avoids archive metadata preservation on
-  bind mounts, preventing successful sandbox commands from exiting with 125.
-
-### Known limitations
-
-- The supported release boundary is local and single-user.
-- Hosted tenancy, centralized observability, and independent multi-tenant
-  security validation are outside the supported beta boundary.
-- The VS Code extension is not included in the Python release; it remains
-  source-only and evaluation-only, and its legacy stdio transport is unsupported.
+# Changelog
+
+All notable changes are recorded here. Pulse follows Semantic Versioning while
+pre-1.0 APIs may change with release notes and migration guidance.
+
+## [Unreleased]
+
+## [0.1.2] - 2026-09-05
+
+### Fixed
+
+- Google authorization-code exchange and token refresh now send the Desktop
+  client credential required by Google's token endpoint. Google documents that
+  installed applications cannot keep this value confidential; PKCE remains the
+  authorization-code interception protection.
+- Packaging now fails before creating a wheel or source distribution when the
+  product Google Desktop OAuth credentials are missing or malformed, preventing
+  the placeholder configuration shipped by the invalid 0.1.1 PyPI artifacts.
+- The release workflow validates the configured credential pair against
+  Google's token endpoint before building.
+
+### Security
+
+- Release operators must publish only through the protected trusted-publisher
+  workflow; direct uploads bypass provenance and release verification.
+
+## [0.1.1] - 2026-09-04
+
+### Added
+
+- Product-owned Google Desktop OAuth configuration is embedded in official
+  builds, so installed users can sign in without creating a `.env` file.
+- Release verification now rejects missing/placeholder OAuth configuration,
+  confidential client secrets, developer-only source content, and local home
+  directory paths in published artifacts.
+- Post-login BYOK onboarding now guides provider and model selection before
+  collecting the selected provider key through hidden terminal input.
+- Provider keys are stored in workspace-scoped native OS credential-vault
+  entries, with safe status, rotation, and removal through `pulse keys`.
+
+### Changed
+
+- Google login uses PKCE with a dynamically allocated `127.0.0.1` callback port
+  and no confidential client secret in the distributed application.
+- Source distributions contain only the files needed to build and understand
+  the product, rather than repository tests, scripts, evals, and local templates.
+- Successful key set or rotation migrates that provider away from a legacy
+  plaintext workspace `.env` entry without ever displaying the secret.
+
+## [0.1.0] - 2026-08-29
+
+### Added
+
+- Permissioned local coding-agent CLI with repository intelligence, durable
+  tasks, conversations, mutation tracking, provider routing, and loopback RPC.
+- Docker and authenticated remote sandbox implementations with policy,
+  resource, filesystem, network, secret-redaction, and recovery tests.
+- Configured remote execution is preferred on client machines, with local
+  Docker/Podman used as the secure fallback and no implicit host execution.
+- Production doctor, correlation IDs, remote health/readiness endpoints,
+  operations/security documentation, and explicit deployment boundaries.
+- Reproducible wheel/source builds, artifact-content verification, clean-install
+  smoke tests, cross-platform CI, coverage gate, dependency audit, secret scan,
+  OIDC trusted-publishing workflow, release checksums, source manifest, and
+  CycloneDX SBOM.
+- Direct application dependencies pinned to the versions exercised by the
+  release suite, preventing unreviewed major-version drift at installation.
+- Explicit live-Docker test markers, a single no-skip Docker security gate, and
+  stable Windows pytest teardown behavior in hosted CI.
+- Public `version` and secure provider-key rotation commands, simplified OAuth
+  login/logout UX, authenticated Google userinfo verification, and literal-safe
+  terminal rendering for untrusted text.
+- Non-root Docker overlay export that avoids archive metadata preservation on
+  bind mounts, preventing successful sandbox commands from exiting with 125.
+
+### Known limitations
+
+- The supported release boundary is local and single-user.
+- Hosted tenancy, centralized observability, and independent multi-tenant
+  security validation are outside the supported beta boundary.
+- The VS Code extension is not included in the Python release; it remains
+  source-only and evaluation-only, and its legacy stdio transport is unsupported.

{pulse_coding_agent-0.1.0 → pulse_coding_agent-0.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: pulse-coding-agent
-Version: 0.1.0
+Version: 0.1.2
 Summary: Permissioned coding-agent CLI with durable planning and isolated execution.
 Project-URL: Homepage, https://github.com/Roastedpotato21/pulse
 Project-URL: Repository, https://github.com/Roastedpotato21/pulse
@@ -23,7 +23,6 @@ Requires-Dist: httpx==0.28.1
 Requires-Dist: keyring==25.7.0
 Requires-Dist: openai==2.44.0
 Requires-Dist: prompt-toolkit==3.0.52
-Requires-Dist: python-dotenv==1.2.2
 Requires-Dist: rich==15.0.0
 Requires-Dist: typer==0.26.8
 Requires-Dist: websockets==16.1
@@ -36,7 +35,7 @@ It combines repository-aware planning, durable task state, explicit mutation
 controls, sandboxed command execution, provider routing, audit trails, and cost
 tracking in one Python package.
 
-> **Public beta — 0.1.0:** Pulse is supported for controlled, local,
+> **Public beta — 0.1.1:** Pulse is supported for controlled, local,
 > single-user use. The remote worker and VS Code extension are included for
 > evaluation and development, but they are not supported as multi-tenant or
 > unattended production services.
@@ -50,14 +49,23 @@ tracking in one Python package.
 
 ## Install
 
-Install the first beta from PyPI:
+Install the current beta from PyPI with `pip`:
 
 ```bash
-uv tool install pulse-coding-agent==0.1.0
+python -m pip install pulse-coding-agent==0.1.2
 ```
 
-Alternatively, use `pipx install pulse-coding-agent==0.1.0` or install it in a
-dedicated virtual environment with `pip`.
+The PyPI distribution name is `pulse-coding-agent`; the Python import and
+installed command are both `pulse`. Do not run `pip install pulse`: that name
+belongs to an unrelated WSGI package published in 2009.
+
+For an isolated command-line installation, use `uv` or `pipx`:
+
+```bash
+uv tool install pulse-coding-agent==0.1.2
+```
+
+Alternatively, use `pipx install pulse-coding-agent==0.1.2`.
 
 ## Quick start
 
@@ -71,9 +79,12 @@ pulse ask "Explain this repository and identify the highest-risk missing test"
 
 After Google login, Pulse guides provider selection, model selection, and hidden
 BYOK entry. New provider keys are stored in the native OS credential vault.
-Credentials can also be supplied through environment variables such as `OPENAI_API_KEY`,
-`ANTHROPIC_API_KEY`, `GEMINI_API_KEY`, or `OPENROUTER_API_KEY`. Do not commit a
-populated `.env` file.
+The official distribution already contains Pulse's Google Desktop OAuth client
+credentials; installed users do not create a `.env` file or provide them. As
+with every installed application, these identify the application but cannot be
+kept confidential on end-user machines; PKCE protects authorization-code
+exchange. Provider API keys are collected through hidden terminal input and are
+not written to the project.
 
 To run commands without installing Docker on the client workstation, configure
 a remote worker:
@@ -153,12 +164,13 @@ prompt with hidden input; provider keys are never accepted as command-line
 arguments or printed back to the terminal. New keys are stored in a
 workspace-scoped entry in the native OS credential vault. Existing `.env` keys
 remain readable for compatibility and are removed for that provider after a
-successful vault-backed set or rotation. Environment variables and external
-secret managers remain supported as fallback sources.
+successful vault-backed set or rotation. Pulse never creates a `.env` file.
+Process environment variables and external secret managers remain supported as
+operator-managed fallback sources.
 
 ## Supported boundary
 
-The 0.1.0 beta supports the local CLI and loopback RPC server for one trusted
+The 0.1.2 beta supports the local CLI and loopback RPC server for one trusted
 user on one workstation. Pulse does not claim a security boundary between
 mutually untrusted tenants. Do not expose `pulse-rpc` or `pulse-remote` directly
 to the public internet.
@@ -189,8 +201,9 @@ Run the local quality gates:
 uv run ruff check src tests scripts
 uv run mypy
 uv run pytest tests/ -k "not sandbox" --cov=pulse --cov-report=term-missing --cov-fail-under=54
+PULSE_GOOGLE_CLIENT_ID=<desktop-client-id> PULSE_GOOGLE_CLIENT_SECRET=<desktop-credential> uv run python scripts/configure_product_oauth.py
 uv build
-uv run python scripts/verify_release_artifacts.py dist --expected-version 0.1.0
+uv run python scripts/verify_release_artifacts.py dist --expected-version 0.1.2
 ```
 
 Docker security tests require a working Docker daemon and are enforced by the

{pulse_coding_agent-0.1.0 → pulse_coding_agent-0.1.2}/README.md

@@ -1,180 +1,194 @@
-# Pulse
-
-Pulse is a permissioned coding-agent CLI for working on software repositories.
-It combines repository-aware planning, durable task state, explicit mutation
-controls, sandboxed command execution, provider routing, audit trails, and cost
-tracking in one Python package.
-
-> **Public beta — 0.1.0:** Pulse is supported for controlled, local,
-> single-user use. The remote worker and VS Code extension are included for
-> evaluation and development, but they are not supported as multi-tenant or
-> unattended production services.
-
-## Requirements
-
-- Python 3.11, 3.12, or 3.13
-- An API key for the model provider you choose
-- Docker or Podman for local isolated execution, or access to a configured
-  Pulse remote worker
-
-## Install
-
-Install the first beta from PyPI:
-
-```bash
-uv tool install pulse-coding-agent==0.1.0
-```
-
-Alternatively, use `pipx install pulse-coding-agent==0.1.0` or install it in a
-dedicated virtual environment with `pip`.
-
-## Quick start
-
-Run these commands from the repository you want Pulse to work on:
-
-```bash
-pulse login
-pulse doctor --production --target local
-pulse ask "Explain this repository and identify the highest-risk missing test"
-```
-
-After Google login, Pulse guides provider selection, model selection, and hidden
-BYOK entry. New provider keys are stored in the native OS credential vault.
-Credentials can also be supplied through environment variables such as `OPENAI_API_KEY`,
-`ANTHROPIC_API_KEY`, `GEMINI_API_KEY`, or `OPENROUTER_API_KEY`. Do not commit a
-populated `.env` file.
-
-To run commands without installing Docker on the client workstation, configure
-a remote worker:
-
-```text
-PULSE_REMOTE_URL=wss://sandbox.example.com
-PULSE_REMOTE_TOKEN=<random token of at least 32 characters>
-PULSE_TLS_CERT=/absolute/path/to/client.crt
-PULSE_TLS_KEY=/absolute/path/to/client.key
-PULSE_TLS_CA=/absolute/path/to/ca.crt
-```
-
-When those variables are set, Pulse tries the remote sandbox first and uses a
-local Docker/Podman engine only as a secure fallback. The remote worker host
-still requires Docker or Podman; execution never silently falls back to the
-client host.
-
-Before allowing mutations or shell execution, review the proposed operation and
-its permission prompt. Treat model output, tool arguments, and repository
-content as untrusted input.
-
-## What the beta includes
-
-- Repository indexing and context-aware conversations
-- Durable plans, tasks, sessions, episodic memory, and recovery state
-- Permission-gated file mutations with transactional rollback
-- Host, Docker, Podman, and authenticated remote sandbox backends
-- Filesystem, network, resource, timeout, and secret-redaction policies
-- Multi-provider model routing and usage/cost accounting
-- Loopback JSON-RPC integration through `pulse-rpc` or `pulse serve`
-- Production preflight checks, structured audit events, and correlation IDs
-
-The package installs three entry points:
-
-```text
-pulse          Interactive CLI
-pulse-rpc      Loopback JSON-RPC server
-pulse-remote   Evaluation-only remote sandbox worker
-```
-
-Use `pulse --help` for the current command surface and command-specific help.
-`pulse-rpc` and `pulse serve` require a strong `PULSE_RPC_TOKEN` bearer secret
-and must stay bound to loopback.
-
-### Interactive shell
-
-Run `pulse` without arguments for the responsive project shell. Natural-language
-input goes to the agent; prefix any regular CLI command with `/` to run it in the
-same session, such as `/status`, `/keys list`, or `/chat switch ID`. Completions
-appear as you type and are always generated from the public CLI parser.
-
-- `Tab` or `Ctrl-Space`: open/accept command completion
-- `Up`/`Down`: navigate history; `Ctrl-R`: search history
-- `Alt-Enter`: insert a newline; `Enter`: submit
-- `Ctrl-C`: clear the current input; on an empty prompt, exit
-- `/help`, `/clear`, and `/exit`: shell controls
-
-History is stored locally in the Git-ignored `.pulse/history` file.
-
-### Account and provider keys
-
-```bash
-pulse version
-pulse login
-pulse auth-status
-pulse whoami
-pulse logout
-pulse keys
-pulse keys list
-pulse keys set openai
-pulse keys rotate openai
-pulse keys remove openai
-```
-
-`pulse keys` opens the status and rotation manager. Set and rotate operations
-prompt with hidden input; provider keys are never accepted as command-line
-arguments or printed back to the terminal. New keys are stored in a
-workspace-scoped entry in the native OS credential vault. Existing `.env` keys
-remain readable for compatibility and are removed for that provider after a
-successful vault-backed set or rotation. Environment variables and external
-secret managers remain supported as fallback sources.
-
-## Supported boundary
-
-The 0.1.0 beta supports the local CLI and loopback RPC server for one trusted
-user on one workstation. Pulse does not claim a security boundary between
-mutually untrusted tenants. Do not expose `pulse-rpc` or `pulse-remote` directly
-to the public internet.
-
-The remote worker requires authenticated transport, durable configuration, and
-container isolation. It remains evaluation-only until tenant isolation,
-centralized observability, load testing, disaster-recovery exercises, and an
-independent security review are complete. The VS Code extension is source-only
-and is not part of the Python distribution.
-
-Pulse sends prompts and selected repository context to the configured model
-provider. Data handling therefore also depends on that provider's terms and
-settings. Pulse itself does not include product analytics or telemetry export
-in this beta.
-
-## Development
-
-Clone the repository and create the locked development environment:
-
-```bash
-uv sync --locked
-uv run pulse --help
-```
-
-Run the local quality gates:
-
-```bash
-uv run ruff check src tests scripts
-uv run mypy
-uv run pytest tests/ -k "not sandbox" --cov=pulse --cov-report=term-missing --cov-fail-under=54
-uv build
-uv run python scripts/verify_release_artifacts.py dist --expected-version 0.1.0
-```
-
-Docker security tests require a working Docker daemon and are enforced by the
-hosted release workflow. See [OPERATIONS.md](OPERATIONS.md) for release and
-rollback procedures.
-
-## Documentation
-
-- [Architecture](ARCHITECTURE.md)
-- [Operations and releases](OPERATIONS.md)
-- [Security policy](SECURITY.md)
-- [Sandbox security boundary](src/pulse/sandbox/SECURITY.md)
-- [Privacy policy](PRIVACY.md)
-- [Changelog](CHANGELOG.md)
-
-To report a vulnerability, use GitHub private vulnerability reporting instead
-of a public issue. General defects and beta feedback belong in the
-[issue tracker](https://github.com/Roastedpotato21/pulse/issues).
+# Pulse
+
+Pulse is a permissioned coding-agent CLI for working on software repositories.
+It combines repository-aware planning, durable task state, explicit mutation
+controls, sandboxed command execution, provider routing, audit trails, and cost
+tracking in one Python package.
+
+> **Public beta — 0.1.1:** Pulse is supported for controlled, local,
+> single-user use. The remote worker and VS Code extension are included for
+> evaluation and development, but they are not supported as multi-tenant or
+> unattended production services.
+
+## Requirements
+
+- Python 3.11, 3.12, or 3.13
+- An API key for the model provider you choose
+- Docker or Podman for local isolated execution, or access to a configured
+  Pulse remote worker
+
+## Install
+
+Install the current beta from PyPI with `pip`:
+
+```bash
+python -m pip install pulse-coding-agent==0.1.2
+```
+
+The PyPI distribution name is `pulse-coding-agent`; the Python import and
+installed command are both `pulse`. Do not run `pip install pulse`: that name
+belongs to an unrelated WSGI package published in 2009.
+
+For an isolated command-line installation, use `uv` or `pipx`:
+
+```bash
+uv tool install pulse-coding-agent==0.1.2
+```
+
+Alternatively, use `pipx install pulse-coding-agent==0.1.2`.
+
+## Quick start
+
+Run these commands from the repository you want Pulse to work on:
+
+```bash
+pulse login
+pulse doctor --production --target local
+pulse ask "Explain this repository and identify the highest-risk missing test"
+```
+
+After Google login, Pulse guides provider selection, model selection, and hidden
+BYOK entry. New provider keys are stored in the native OS credential vault.
+The official distribution already contains Pulse's Google Desktop OAuth client
+credentials; installed users do not create a `.env` file or provide them. As
+with every installed application, these identify the application but cannot be
+kept confidential on end-user machines; PKCE protects authorization-code
+exchange. Provider API keys are collected through hidden terminal input and are
+not written to the project.
+
+To run commands without installing Docker on the client workstation, configure
+a remote worker:
+
+```text
+PULSE_REMOTE_URL=wss://sandbox.example.com
+PULSE_REMOTE_TOKEN=<random token of at least 32 characters>
+PULSE_TLS_CERT=/absolute/path/to/client.crt
+PULSE_TLS_KEY=/absolute/path/to/client.key
+PULSE_TLS_CA=/absolute/path/to/ca.crt
+```
+
+When those variables are set, Pulse tries the remote sandbox first and uses a
+local Docker/Podman engine only as a secure fallback. The remote worker host
+still requires Docker or Podman; execution never silently falls back to the
+client host.
+
+Before allowing mutations or shell execution, review the proposed operation and
+its permission prompt. Treat model output, tool arguments, and repository
+content as untrusted input.
+
+## What the beta includes
+
+- Repository indexing and context-aware conversations
+- Durable plans, tasks, sessions, episodic memory, and recovery state
+- Permission-gated file mutations with transactional rollback
+- Host, Docker, Podman, and authenticated remote sandbox backends
+- Filesystem, network, resource, timeout, and secret-redaction policies
+- Multi-provider model routing and usage/cost accounting
+- Loopback JSON-RPC integration through `pulse-rpc` or `pulse serve`
+- Production preflight checks, structured audit events, and correlation IDs
+
+The package installs three entry points:
+
+```text
+pulse          Interactive CLI
+pulse-rpc      Loopback JSON-RPC server
+pulse-remote   Evaluation-only remote sandbox worker
+```
+
+Use `pulse --help` for the current command surface and command-specific help.
+`pulse-rpc` and `pulse serve` require a strong `PULSE_RPC_TOKEN` bearer secret
+and must stay bound to loopback.
+
+### Interactive shell
+
+Run `pulse` without arguments for the responsive project shell. Natural-language
+input goes to the agent; prefix any regular CLI command with `/` to run it in the
+same session, such as `/status`, `/keys list`, or `/chat switch ID`. Completions
+appear as you type and are always generated from the public CLI parser.
+
+- `Tab` or `Ctrl-Space`: open/accept command completion
+- `Up`/`Down`: navigate history; `Ctrl-R`: search history
+- `Alt-Enter`: insert a newline; `Enter`: submit
+- `Ctrl-C`: clear the current input; on an empty prompt, exit
+- `/help`, `/clear`, and `/exit`: shell controls
+
+History is stored locally in the Git-ignored `.pulse/history` file.
+
+### Account and provider keys
+
+```bash
+pulse version
+pulse login
+pulse auth-status
+pulse whoami
+pulse logout
+pulse keys
+pulse keys list
+pulse keys set openai
+pulse keys rotate openai
+pulse keys remove openai
+```
+
+`pulse keys` opens the status and rotation manager. Set and rotate operations
+prompt with hidden input; provider keys are never accepted as command-line
+arguments or printed back to the terminal. New keys are stored in a
+workspace-scoped entry in the native OS credential vault. Existing `.env` keys
+remain readable for compatibility and are removed for that provider after a
+successful vault-backed set or rotation. Pulse never creates a `.env` file.
+Process environment variables and external secret managers remain supported as
+operator-managed fallback sources.
+
+## Supported boundary
+
+The 0.1.2 beta supports the local CLI and loopback RPC server for one trusted
+user on one workstation. Pulse does not claim a security boundary between
+mutually untrusted tenants. Do not expose `pulse-rpc` or `pulse-remote` directly
+to the public internet.
+
+The remote worker requires authenticated transport, durable configuration, and
+container isolation. It remains evaluation-only until tenant isolation,
+centralized observability, load testing, disaster-recovery exercises, and an
+independent security review are complete. The VS Code extension is source-only
+and is not part of the Python distribution.
+
+Pulse sends prompts and selected repository context to the configured model
+provider. Data handling therefore also depends on that provider's terms and
+settings. Pulse itself does not include product analytics or telemetry export
+in this beta.
+
+## Development
+
+Clone the repository and create the locked development environment:
+
+```bash
+uv sync --locked
+uv run pulse --help
+```
+
+Run the local quality gates:
+
+```bash
+uv run ruff check src tests scripts
+uv run mypy
+uv run pytest tests/ -k "not sandbox" --cov=pulse --cov-report=term-missing --cov-fail-under=54
+PULSE_GOOGLE_CLIENT_ID=<desktop-client-id> PULSE_GOOGLE_CLIENT_SECRET=<desktop-credential> uv run python scripts/configure_product_oauth.py
+uv build
+uv run python scripts/verify_release_artifacts.py dist --expected-version 0.1.2
+```
+
+Docker security tests require a working Docker daemon and are enforced by the
+hosted release workflow. See [OPERATIONS.md](OPERATIONS.md) for release and
+rollback procedures.
+
+## Documentation
+
+- [Architecture](ARCHITECTURE.md)
+- [Operations and releases](OPERATIONS.md)
+- [Security policy](SECURITY.md)
+- [Sandbox security boundary](src/pulse/sandbox/SECURITY.md)
+- [Privacy policy](PRIVACY.md)
+- [Changelog](CHANGELOG.md)
+
+To report a vulnerability, use GitHub private vulnerability reporting instead
+of a public issue. General defects and beta feedback belong in the
+[issue tracker](https://github.com/Roastedpotato21/pulse/issues).