conning 0.2.0__tar.gz

conning-0.2.0/.github/workflows/ci.yml

@@ -0,0 +1,32 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, windows-latest, macos-latest]
+        python: ["3.11", "3.13"]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+        with:
+          python-version: ${{ matrix.python }}
+      - run: uv sync
+      - run: uv run ruff check
+      - run: uv run ruff format --check
+      - name: pytest (coverage gate on Linux, where the sh-based job tests run)
+        if: matrix.os == 'ubuntu-latest'
+        run: uv run pytest -q --cov=conning --cov-report=term-missing --cov-fail-under=95
+      - name: pytest
+        if: matrix.os != 'ubuntu-latest'
+        run: uv run pytest -q

conning-0.2.0/.github/workflows/release.yml

@@ -0,0 +1,40 @@
+name: Release
+
+# Push a tag like v0.0.1 to publish. PyPI must trust this workflow first (Trusted Publishing):
+# pypi.org > Your projects > Publishing > add a pending publisher for project "conning",
+# owner EranYonai, repository Conning, workflow release.yml, environment pypi.
+
+on:
+  push:
+    tags: ["v*"]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+      - name: Check the tag matches the package version
+        run: |
+          version=$(uv version --short)
+          test "v$version" = "$GITHUB_REF_NAME" || { echo "tag $GITHUB_REF_NAME != version $version"; exit 1; }
+      - run: uv build
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

conning-0.2.0/.gitignore

@@ -0,0 +1,9 @@
+__pycache__/
+*.py[cod]
+.venv/
+dist/
+build/
+*.egg-info/
+.pytest_cache/
+.ruff_cache/
+.coverage

conning-0.2.0/CHANGELOG.md

@@ -0,0 +1,48 @@
+# Changelog
+
+## 0.2.0 (2026-10-15)
+
+- Approve commands where you are: in the agent client (MCP elicitation, both protocol versions; on by
+  default, `conn mcp --no-approve-in-client` turns it off), in `conn watch`, or with `conn approve`. A desktop notification
+  says when a command is waiting (`CONNING_NOTIFY=0` turns it off).
+- `conn run` at a terminal asks right there when a command needs approval, and prints the result; a
+  target name typed where the command starts is caught with a hint to use `a,b`.
+- `conn targets` shows the user each target logs in as; `conn add <name> --like <target> --user <u>` adds the
+  same machine as another user.
+- Jobs on Linux and macOS targets get the PATH of a login shell, so tools in `~/.local/bin` or `/opt` are found.
+- Windows jobs run detached (created through WMI, outside the ssh session), so they survive a dropped
+  connection and support `read --signal` and timeouts like POSIX jobs. Scripts reach PowerShell over stdin.
+- `conn mcp install claude|codex|cursor|opencode|pi` adds the server and denies raw `ssh`/`scp`/`sftp`, the human-only
+  `conn` commands and reads of Conning's config dir (pi has no rules, so only the server); merges with
+  existing files and keeps a backup.
+- `conn watch`: every command, decision and job exit as it happens, new job output, and approval prompts.
+- Audit log in the state dir (`audit.jsonl`), hash-chained; `conn doctor` reports edits.
+- Built-in read-only list: `uname`, `hostname`, `df`, `ps`, `ls`, `ip addr`, `systemctl status`, `journalctl`,
+  `Get-Process` and more run without asking, checked so changing forms still ask (`safe = false` opts out).
+- `conn allow <target> [words]` lists or adds allow rules; `conn deny <target> <words>` removes one.
+- `conn doctor` checks the config and state dirs, ssh tools, keychain, secret sources, pinned keys and leases.
+
+## 0.1.0 (unreleased)
+
+- M1: commands run over OpenSSH with a generated per-target config (pinned host key, no forwarding,
+  connection reuse) and key, ssh-agent or password auth (keychain, `op://` or `env:` references).
+- `run` starts detached jobs on POSIX targets; `read j:<id>` streams new lines, long-polls and sends
+  signals; `read o:<id>` pages saved output; `read <target>:<path>` reads remote files.
+- `transfer` copies files and directories with scp and checks files by sha256.
+- Approvals: commands outside the allowlist wait for `conn approve a:<id>`; leases with `conn lease`.
+- `conn add`, `approve`, `import`, `test`, `rm` and `lease` work. Agent-added targets stay pending.
+- Secrets and their base64, URL and hex forms are redacted from all output.
+- Windows targets run synchronously through PowerShell for now.
+- Unit tests with a fake transport; CI gates coverage at 95%.
+- `conn run <target> uname -a` passes flags through without `--`; `conn approve a:<id>` prints the result.
+- The `max_bytes` ceiling is now 16 KB (was 64 KB).
+- Running commands never writes the config dir: job output, approvals and generated ssh configs go to a
+  state dir (`XDG_STATE_HOME/conning`, or `CONNING_STATE`). Works with a read-only config, as in agent sandboxes.
+- `conn targets` says where it looked when there are none, and why a pending target is pending.
+- File and secret problems print one `error:` line (CLI and MCP) instead of a traceback.
+
+## 0.0.1 (unreleased)
+
+- Scaffold: `conn` CLI surface, MCP server with the four agent tools (`targets` works; `run`, `read`,
+  `transfer` are stubs for M1), fail-closed target file, output cap with handles, two-word allowlist
+  rules, CI, and a PyPI release workflow using Trusted Publishing.

conning-0.2.0/CLAUDE.md

@@ -0,0 +1,29 @@
+# Working on Conning
+
+Conning is an MCP server and CLI that let a developer's own agent run commands on remote test
+machines ("targets") without seeing their secrets. Read [docs/design.md](docs/design.md) before
+changing behavior; every decision there has a number (D1...) and a status.
+
+## Principles
+
+- Prompt text is advice; the toolset is a wall. Guardrails live in code, and default to deny.
+- Fewer tools beat more tools. The agent gets exactly four: targets, run, read, transfer. Adding a
+  tool or growing a docstring costs context on every turn; `tests/test_cli_and_server.py` caps it.
+- No tool ever returns a secret, adds a live target or changes policy.
+- Lead every result with the fact the agent branches on (exit code or status). Never exceed `max_bytes`.
+- The target file is fail-closed: unknown keys and bad values are errors.
+- Never put real hostnames, IPs or credentials in code, tests or docs. Placeholders only.
+
+## Commands
+
+```sh
+uv sync
+uv run pytest --cov=conning   # keep coverage at 95%+; mock SSH with the fake transport in tests/conftest.py
+uv run ruff check && uv run ruff format --check
+uv run conn help --markdown   # paste into README.md between the conn-help markers after CLI changes
+```
+
+## Docs
+
+When a decision changes, update the table in `docs/design.md` (supersede rows rather than deleting
+them) and add a dated entry to `docs/build-log.html`.

conning-0.2.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

conning-0.2.0/PKG-INFO

@@ -0,0 +1,200 @@
+Metadata-Version: 2.5
+Name: conning
+Version: 0.2.0
+Summary: A control room for your agent's test machines: an MCP server and CLI that run commands on remote targets without the agent ever seeing a secret.
+Project-URL: Homepage, https://github.com/EranYonai/Conning
+Project-URL: Issues, https://github.com/EranYonai/Conning/issues
+Author: Eran Yonai
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agents,mcp,remote-execution,ssh,testing,vault
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Testing
+Classifier: Topic :: System :: Systems Administration
+Requires-Python: >=3.11
+Requires-Dist: keyring>=25.7.0
+Requires-Dist: mcp<3,>=2.3
+Description-Content-Type: text/markdown
+
+# Conning
+
+**A control room for your agent's test machines.** Your agent (Claude Code, Codex, Cursor...) stays on
+your own laptop. Conning holds the keys to your lab VMs and gives the agent four lean tools to run
+commands and move files there. The agent never sees a password, and you approve anything risky.
+
+> **Status: pre-alpha (M2 done).** Running commands, long jobs, remote file reads and transfers
+> work over OpenSSH, with pinned host keys, password or key auth, approvals and leases. You can approve
+> in the agent client, in `conn watch` or with `conn approve`; `conn doctor` checks your setup. Long
+> jobs run detached on Linux, macOS and Windows targets, and `conn mcp install` sets up claude, codex,
+> cursor, opencode or pi. See
+> [docs/design.md](docs/design.md) for every decision so far.
+
+## Why
+
+Putting an agent harness inside every CLI on every remote machine is redundant. Developers already
+have a capable agent on their own machine. What's missing is a safe, token-lean way for that agent to
+reach the machines it tests on:
+
+- **No secrets in context.** Targets hold *references* to the OS keychain, `op://` or ssh-agent.
+  Secrets are resolved inside Conning at the last moment and never returned by any tool.
+- **Lean results.** Exit code first, output capped at 8 KB by default (the agent may ask for more, up
+  to a ceiling), with a handle to page the rest. Fan-out to many targets collapses identical results.
+- **Guardrails in code, not in the prompt.** Each target has a mode (`observe`, `ask`, `lease`).
+  Commands outside the allowlist wait for your approval; "always allow" remembers two words, so
+  `systemctl status` never lets through `systemctl stop`.
+- **Plain OpenSSH underneath.** Linux and Windows (OpenSSH + PowerShell 7), pinned host keys,
+  forwarding forced off.
+
+## Install
+
+```sh
+uv tool install conning        # or: pipx install conning
+conn mcp install claude        # or codex, cursor, opencode, pi: adds the server and denies raw ssh/scp
+```
+
+The MCP server needs no install at all:
+
+```sh
+claude mcp add conning -- uvx conning mcp
+```
+
+## The agent's four tools
+
+| Tool | What it does |
+|---|---|
+| `targets(filter?, check?)` | One line per target: name, OS, shell, user, tags, mode. Never a host or secret. |
+| `run(target, cmd \| argv, wait=30, max_bytes=8192, ...)` | Runs on one target, a list or `tag:<tag>`. Exit code first. Still running after `wait` seconds: returns a job id (`wait=0` is async). |
+| `read(id, wait?, range?, grep?, signal?)` | Long-polls a job for new lines, pages a saved output, or reads a remote file. |
+| `transfer(source, dest)` | Copies files between `local:<path>` and `<target>:<path>`, checked by sha256. |
+
+Agents without MCP can use the same commands through the `conn` CLI; the output is identical.
+
+## For agents: CLI reference
+
+This block is generated by `conn help --markdown`, so you don't need to call `--help`. A test keeps it
+in sync with the code.
+
+<!-- conn-help:start -->
+```
+conn targets [--check] [filter]
+    List targets: name, OS, shell, user, tags, mode. Never hosts or secrets.
+
+conn run [--wait WAIT] [--timeout TIMEOUT] [--cwd CWD] [--shell]
+                [--max-bytes MAX_BYTES] [--grep GREP]
+                target [argv ...]
+    Run a command on one target, a list, or tag:<tag>. Exit code first.
+
+conn read [--wait WAIT] [--range RANGE] [--grep GREP] [--signal {INT,TERM,KILL}]
+                 [--max-bytes MAX_BYTES]
+                 id
+    Page a job (new lines only), a saved output, an approval, or a remote file.
+
+conn transfer source dest
+    Copy files: local:<path> to <target>:<path>, or back. sha256 checked.
+
+conn add [--host HOST] [--user USER] [--like TARGET] [--port PORT]
+                [--auth {ssh-agent,key,password}] [--secret SECRET] [--key KEY]
+                [--os {linux,windows,darwin}] [--mode {observe,ask,lease}] [--tag TAG] [--retry]
+                name
+    Add a target. Without a terminal it is saved as pending until a human approves it.
+
+conn approve [--always] what
+    Human only: make a pending target live, or allow a pending command a:<id>.
+
+conn import [--match MATCH]
+    Import hosts from ~/.ssh/config as pending targets (unsafe options dropped).
+
+conn rm name
+    Remove a target and its pinned host key.
+
+conn test name
+    Probe a target: reachability, OS, shell, pinned host key.
+
+conn lease [--minutes MINUTES] name
+    Human only: give a target a full shell for a time box (1-60 minutes).
+
+conn allow target [words ...]
+    Human only: let a command run without asking (no words: list the rules).
+
+conn deny target words [words ...]
+    Remove an allow rule, so the command asks again.
+
+conn watch [--history HISTORY] [--no-prompt]
+    Live control room: every command on every target, job output, approval prompts.
+
+conn doctor
+    Check this machine's setup: config and state dirs, ssh, keychain, targets.
+
+conn mcp [--approve-in-client | --no-approve-in-client] <serve|install> ...
+    Run the MCP server on stdio, or install it into an agent client.
+
+conn help [--markdown]
+    Show this help; --markdown prints the block cached in README.md.
+```
+<!-- conn-help:end -->
+
+A target is one login on one machine. To use the same machine as another user, add it again:
+`conn add lab-tester --like lab --user tester` copies the host, port, OS and tags and asks for the new
+user's password. `conn targets` shows which user each target uses.
+
+A target you add with `conn add` from an agent session is saved as **pending**. It does nothing until
+the human runs `conn approve <name>`, which shows the host, the pinned host-key fingerprint and where
+the secret comes from.
+
+A command outside a target's allowlist returns `status=pending_approval id=a:<id>`, and a desktop
+notification tells the human. They answer in one of three places (allow once, always allow its first
+two words, or deny), and the agent picks up the result with `read a:<id>`:
+
+- **In the agent client**: any MCP client that supports elicitation shows the question before the
+  command is queued, and an approved command runs in the same call. Clients without it fall back to
+  the two below. If a client would answer such prompts by itself instead of asking you, run the server
+  as `conn mcp --no-approve-in-client`.
+- **In `conn watch`**, which also shows every command and its output as it happens.
+- **With `conn approve a:<id>`** in any terminal. When you run `conn run` yourself at a terminal, it
+  just asks you there and prints the result.
+
+Read-only commands such as `uname`, `hostname`, `df`, `ps`, `ls`, `ip addr`, `systemctl status` and
+`journalctl` run without asking on every target; each is checked so its changing forms (`hostname x`,
+`ip addr add`) still ask, and `safe = false` in a target's entry turns the list off.
+`conn allow <target> make test` lets another command run without asking from then on; `conn deny`
+takes it back. Every command, answer and rule change lands in a hash-chained audit log, and
+`conn doctor` checks your setup when something doesn't work.
+
+## Safety model
+
+| Mode | What the agent can do | Default for |
+|---|---|---|
+| `observe` | The built-in read-only list and allowlisted commands only; everything else is refused. | targets tagged `shared` or `prod` |
+| `ask` | The built-in read-only list and allowlisted commands run; anything else waits for your approval. | new lab targets |
+| `lease` | Any command, for a time box you grant (15 min default, 60 max). | never by default |
+
+- No tool returns a secret, adds a live target or changes policy.
+- Secrets travel over stdin or the SSH channel's env, never argv. Output is redacted before it is saved.
+- Remote output is marked untrusted. Shell wrappers (`sh -c`, `python -c`, `sudo`...) and shell syntax
+  (`;`, `|`, `$(...)`) always ask.
+- `conn mcp install` also denies the agent raw `ssh`/`scp`, so it can't go around Conning (pi has no
+  permission rules, so there it only adds the server).
+- The audit log is hash-chained. It runs as your user, so it is tamper-evident, not tamper-proof.
+
+## Development
+
+```sh
+uv sync
+uv run pytest --cov=conning      # CI requires 95% coverage on Linux
+uv run ruff check && uv run ruff format --check
+```
+
+After changing the CLI, refresh the README block with `uv run conn help --markdown`.
+
+## Docs
+
+- [docs/design.md](docs/design.md): the design and every decision, with its status.
+- [docs/build-log.html](docs/build-log.html): how the design came together, as a blog post.
+
+## License
+
+[Apache-2.0](LICENSE)