agentseam 0.1.0__tar.gz

agentseam-0.1.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 2026 open-coder-ai
+
+   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.

agentseam-0.1.0/PKG-INFO

@@ -0,0 +1,295 @@
+Metadata-Version: 2.4
+Name: agentseam
+Version: 0.1.0
+Summary: The primitives layer for every coding agent — one handler API over per-agent hooks, instruction files, plugin packaging, and config.
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/open-coder-ai/agentseam
+Project-URL: Source, https://github.com/open-coder-ai/agentseam
+Project-URL: Documentation, https://github.com/open-coder-ai/agentseam/blob/main/ARCHITECTURE.md
+Project-URL: Issues, https://github.com/open-coder-ai/agentseam/issues
+Project-URL: Changelog, https://github.com/open-coder-ai/agentseam/blob/main/CHANGELOG.md
+Keywords: ai-agents,hooks,claude-code,cursor,copilot,codex,gemini-cli,windsurf,pretooluse,agents-md,plugin-packaging,guardrails,observability
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: dev
+Requires-Dist: pytest>=7; extra == "dev"
+Dynamic: license-file
+
+<img src="https://raw.githubusercontent.com/open-coder-ai/agentseam/main/docs/assets/logo.svg"
+     alt="agentseam logo: five unevenly spaced vendor lines converging through a stitched seam into five evenly spaced parallel lines"
+     width="104" align="right">
+
+# agentseam
+
+**The primitives layer for every coding agent — one handler API over per-agent hooks,
+instruction files, plugin packaging, and config.**
+
+Write one handler. Run it on every coding agent. Every agent — Claude Code, Cursor, VS Code
+Copilot, Codex, Gemini CLI, Windsurf — invented its own hook system: different event names,
+different payload shapes, different ways to say "no", different config files. So every tool
+built on top gets written once per agent, or targets one agent and stops there.
+
+agentseam is the layer underneath: one normalized event, one decision type, and an explicit
+map of what each agent can *actually* do.
+
+```python
+from agentseam import run, Decision
+
+def handler(event):
+    if event.event == "pre_tool" and "AKIA" in (event.content or ""):
+        return Decision.deny("no AWS keys in memory files")
+    return Decision.allow()
+
+run(handler)
+```
+
+```bash
+agentseam install all "python3 my_handler.py" --events pre_tool
+```
+
+That handler now runs on Claude Code, Cursor, and VS Code Copilot — each getting its native
+protocol, each wired into its own config file.
+
+## It tells you the truth about what it can enforce
+
+Agents are not equally capable, and pretending otherwise is how a "policy" silently fails.
+The capability matrix is data, not marketing:
+
+```
+$ agentseam matrix        # trimmed to five of fifteen columns
+                     aider           claude_code     cursor          vscode_copilot  zed
+prompt_submit        none            enforced        enforceable     detect          none
+pre_tool             none            enforced        enforceable     enforced        none
+post_tool            none            detect          detect          detect          none
+```
+
+- **enforced** — the agent blocks, and fails closed if your hook dies
+- **best-effort** — it blocks, but fails *open* (Cursor's default: a crashed hook allows)
+- **detect** — you see it after the fact; prevention is not available (Cursor file edits
+  fire `afterFileEdit`, after the write already landed)
+- **enforceable** — it blocks and *can* be told to fail closed, but doesn't by default
+  (Cursor's `failClosed: true`). "best-effort" would understate a surface you can make
+  airtight; "enforced" would claim a default that isn't there. agentseam's installer asks
+  for fail-closed on every gate it writes
+- **none** — no hook surface at all (Zed, Aider). Said out loud rather than papered over.
+
+A row is only claimed when a `verified: {version, date, method}` record backs it — the
+version and date something was checked, and how (live run, vendor source, vendor docs).
+No row asserts a capability nobody has verified.
+
+`unadapted` is a fourth, deliberately separate state: agentseam has no hook adapter for
+that agent yet. It is a claim about *us*, not about the agent — those agents still receive
+instruction files, they just cannot have their tool calls gated here. Collapsing the two
+would either slander an agent that does expose hooks or overstate our own coverage.
+
+A `Decision.rewrite(...)` on an agent that cannot rewrite degrades to `ask`, never to a
+silent pass-through. `agentseam doctor` reports what is wired on this machine and flags
+capability rows that have not been re-verified in 90 days.
+
+## What it is for
+
+Not just guardrails. Anything that wants to watch or shape an agent's life:
+
+| | |
+|---|---|
+| **Observability** | one JSONL/OTel stream across every agent in the repo (`examples/event_log.py`) |
+| **Notifications** | desktop notification on stop or prompt (`examples/notify.py`) |
+| **Cost tracking** | token/cost meters that work regardless of which agent ran |
+| **Guardrails** | secrets, memory governance, destructive-command blocks |
+| **Process gates** | TDD enforcement, "tests before push" |
+| **Context injection** | inject memory/instructions at session start |
+
+## One set of instructions, every agent
+
+Multi-agent repos hand-maintain a drawer of near-identical files — CLAUDE.md, AGENTS.md,
+`.cursor/rules/*`, `.github/copilot-instructions.md`, GEMINI.md, `.windsurfrules`,
+`codex.md` — and they drift.
+
+```bash
+agentseam instructions --text "Prefer pnpm. Tests live beside source."
+```
+
+```
+updated   AGENTS.md
+created   CLAUDE.md
+created   .junie/guidelines.md
+...
+covered by AGENTS.md: codex_cli, copilot, cursor, gemini_cli, kimi_code, vscode_copilot, windsurf, zed
+```
+
+16 agents reached with 9 files written, because 8 of them read `AGENTS.md` natively and a
+second copy would only drift. Content is written as a marker-delimited block, so anything a
+human wrote in those files is preserved untouched — and `instructions --list` shows what
+a repo is already telling its agents.
+
+## One policy, four incompatible permission languages
+
+Every agent has a settings file with an allow/deny model, and no two of them are the same
+kind of object. Claude Code evaluates an ordered rule list. Gemini CLI keeps tool-name
+allowlists. Codex runs a Starlark program over command prefixes. VS Code holds a map of
+auto-approve patterns. They do **not** have the same expressive power.
+
+```bash
+agentseam permissions --rule 'deny:shell:curl *' --rule 'allow:shell:npm test'
+```
+
+```
+# claude_code -> .claude/settings.json
+{"permissions": {"allow": ["Bash(npm test)"], "deny": ["Bash(curl *)"]}}
+
+# vscode_copilot -> .vscode/settings.json
+{"chat.tools.terminal.autoApprove": {"npm test": true}}
+# unrepresentable: Rule('deny', 'shell', 'curl *') -- this map has no deny: setting a
+# pattern false withholds auto-approval but still lets a human approve the command
+```
+
+That second block is the point. VS Code's auto-approve map takes `false` for a pattern,
+which reads like a denylist and is not one — the command still runs once a human clicks
+through. (The `github.copilot.chat.agent.terminal.denyList` key it replaced never blocked
+either.) Rendering a "deny" there would hand you a guardrail that stops nothing, so
+agentseam hands back the rule unrendered with the reason instead, and the command exits
+non-zero. Put it in CI and you find out that your policy doesn't survive the trip to an
+agent *before* you rely on it.
+
+The same honesty applies to the gaps we have in ourselves. Every agent the matrix knows
+appears here — either with a recorded model, or named with the reason there isn't one, and
+a test enforces that the two sets add up to the matrix exactly. A silently absent agent
+would read as "nothing to say here" when the truth is "nobody looked".
+
+The reasons distinguish two things that are easy to blur: an agent whose permission system
+*provably exists* but whose schema we haven't read (Antigravity, Devin, Grok, Kimi Code all
+prove it through their own hook events) versus one where nothing is established at all. And
+a missing hook surface is never recorded as a missing permission model — Aider and Zed
+expose no hooks, which says nothing about what their config files can restrict.
+
+## Bundles: mostly the same directory, twice
+
+A Claude Code plugin and a Gemini CLI extension turn out to be nearly the same thing
+underneath two different manifests:
+
+| part | Claude Code plugin | Gemini CLI extension | |
+|---|---|---|---|
+| skill | `skills/<name>/SKILL.md` | `skills/<name>/SKILL.md` | identical |
+| subagent | `agents/<name>.md` | `agents/<name>.md` | identical |
+| hooks | `hooks/hooks.json` | `hooks/hooks.json` | identical |
+| command | `commands/<name>.md` | `commands/<name>.toml` | same folder, different format |
+| manifest | `.claude-plugin/plugin.json` | `gemini-extension.json` | different |
+
+So one directory serves both, and the real work is the second manifest and writing the
+commands twice. VS Code has no bundle format at all — parts are found by location, so
+committing the file *is* the install — and it reads several of Claude Code's own folders
+natively: `.claude/skills`, `.claude/agents`, `.claude/rules`, and hooks straight out of
+`.claude/settings.json`.
+
+```bash
+agentseam packaging
+```
+
+...prints each layout, the templates shared by more than one agent, and which folders an
+agent reads that belong to somebody else. That last line matters in both directions: a
+repo shipping `.claude/skills` is already shipping skills to VS Code, intended or not.
+
+`plan(agent, bundle)` renders a bundle into the exact files an agent expects, and — as
+with permissions — hands back what the format cannot hold, with a reason specific to that
+agent. Gemini can't take a `.mcp.json`, but not because it lacks MCP: it declares servers
+in the manifest instead, and saying "no MCP support" would be as wrong as saying nothing.
+
+## See it per vendor before you install anything
+
+[`examples/generated/`](examples/generated/) has a page for every agent agentseam can hook,
+each showing the **same situation** — an agent about to write a secret into a file it will
+read back later — in that vendor's own dialect: the config `install` writes, the normalized
+event a handler sees, and what `allow` / `deny` / `ask` / `rewrite` each turn into on the
+way back, including the ones that get reduced because the agent cannot express them.
+
+There is a section for **every hook each agent supports**, in lifecycle order. Every block
+is generated by running the library, and CI fails if the pages drift from what it actually
+produces — an example nobody regenerates is a claim nobody checks.
+
+What the pages cannot do is verify the vendors. Each row records what its claims rest on —
+`live-run`, `live-run-partial`, `vendor-source`, `vendor-docs`, `third-party-install`,
+`inherited` — and most are vendor documentation, which is a claim about what a vendor *says*
+rather than an observation of what their build does. Claude Code's row rests on a full live
+run; Codex CLI, Cursor, and VS Code Copilot each rest on a partial one, with the observed
+events listed on the row. Vendors change hook surfaces without notice, so **verify against
+your own installation before relying on any of it**, and open an issue if a page is wrong.
+
+```bash
+python3 examples/generate.py           # rewrite the pages
+python3 examples/generate.py --check   # what CI runs
+```
+
+## Verify a claim against your own agent
+
+Claude Code's row rests on a full live run; Codex CLI, Cursor, and VS Code Copilot each rest
+on a partial one. If you have another of these agents installed, an hour turns its row from
+"the vendor says so" into evidence:
+
+```bash
+python3 tools/capture.py detect
+python3 tools/capture.py install --agent cursor
+# ... use the agent for a minute ...
+python3 tools/capture.py report
+python3 tools/capture.py uninstall --agent cursor
+```
+
+The probe always allows, so it cannot interfere with real work, and payloads are reduced to
+shape before anything touches disk — keys and types survive, values do not. See
+[tools/VERIFY.md](tools/VERIFY.md).
+
+## Install
+
+```bash
+pip install agentseam
+```
+
+## Supported agents
+
+| Agent | Tier | Config |
+|---|---|---|
+| Claude Code | block + rewrite | `.claude/settings.json` |
+| VS Code Copilot | block + rewrite | `.github/hooks/*.json` |
+| Cursor | block + rewrite (all tools, fail-open by default) | `.cursor/hooks.json` |
+| Gemini CLI | block + rewrite (fail-open) | `.gemini/settings.json` |
+| OpenAI Codex CLI | block + rewrite (fail-open) | `.codex/hooks.json` |
+| Windsurf | block via exit code only; **no file-write event** | `.windsurf/hooks.json` |
+| Zed, Aider | no hook surface at all | — |
+| Devin | block + rewrite (fail-open) | `.devin/hooks.v1.json` |
+| Grok CLI | block on PreToolUse only (fail-open) | `.grok/hooks/*.json` |
+| Antigravity | block, and can refuse to let the agent stop (fail-open) | `.agents/hooks.json` |
+| Kimi Code CLI | block on 3 of its 20 events (fail-open) | `config.toml` |
+| Junie CLI | block + ask + rewrite, all native (fail-open) | `~/.junie/config.json` |
+| Tabnine CLI | block on 6 of its 11 events, incl. post-tool (fail-open) | `.tabnine/agent/settings.json` |
+| Replit | no hook surface found in its docs — instruction files work | — |
+
+Goose, Crush, OpenCode: adapters planned; the
+capability research is done and each is a module plus a matrix row.
+
+## Design
+
+- **stdlib only.** No dependencies, ever, in the adapter path — adapters must stay
+  copy-portable into other projects that vendor single files.
+- **Adapters own all vendor knowledge.** Adding an agent is a module plus a matrix row;
+  no consumer changes.
+- **Ownership-marked wiring.** Install is idempotent and uninstall is surgical: your own
+  hooks in the same config are never touched.
+- **The matrix carries provenance.** Every row records the version and date it was
+  verified, and how.
+
+[ARCHITECTURE.md](ARCHITECTURE.md) explains why those choices, what they cost, and the bug
+classes they exist to prevent.
+
+Apache-2.0.