repomoot 0.2.0__tar.gz

repomoot-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.

repomoot-0.2.0/NOTICE

@@ -0,0 +1,5 @@
+Repomoot (repomoot)
+Copyright 2026 SimeonAr
+
+Licensed under the Apache License, Version 2.0. See LICENSE.
+The protocol description in PROTOCOL.md is licensed CC-BY-4.0.

repomoot-0.2.0/PKG-INFO

@@ -0,0 +1,189 @@
+Metadata-Version: 2.4
+Name: repomoot
+Version: 0.2.0
+Summary: Requests between AI coding agents that own different repositories, with consumer acceptance and owner escalation
+Author: SimeonAr
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/dev-bude/repomoot
+Project-URL: Repository, https://github.com/dev-bude/repomoot
+Project-URL: Issues, https://github.com/dev-bude/repomoot/issues
+Project-URL: Protocol, https://github.com/dev-bude/repomoot/blob/main/PROTOCOL.md
+Project-URL: Security, https://github.com/dev-bude/repomoot/blob/main/SECURITY.md
+Keywords: ai-agents,claude-code,codex,multi-agent,request-lifecycle
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Environment :: Console
+Classifier: Framework :: FastAPI
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Version Control
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: fastapi>=0.110
+Requires-Dist: uvicorn>=0.29
+Requires-Dist: typer>=0.12
+Requires-Dist: httpx>=0.27
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Dynamic: license-file
+
+# Repomoot
+
+**Requests between AI coding agents that own different repositories — with consumer acceptance
+and owner escalation.**
+
+When several coding agents (Claude Code, Codex, Gemini CLI, your own) work on related
+repositories, there is no working channel between them: you become the courier, the product
+owner and the referee, and the history disappears with every `/clear`. Repomoot gives the agents a
+shared lane for *requests* — "I need X from your repository" — with a lifecycle that ends when the
+**consumer** has verified the result in its own context, a **Product Owner** role for the decisions
+owners must not make alone, and a durable, searchable history.
+
+It is not shared memory, not an orchestrator and not a task board. Agents keep their own runtime,
+context and tools. Repomoot owns requests, messages, artifacts, decisions and events.
+
+## How it works
+
+- A local daemon holds the state (SQLite) and serves an HTTP API. The CLI `repomoot` is a thin
+  client and starts the daemon on demand.
+- Agents talk to it through `repomoot` from their own shell tool — nothing else is required from a
+  runtime. The rules an agent follows (the *protocol card*) are owned by Repomoot and handed to the
+  agent at `repomoot connect`; the Claude Code adapter adds a thin skill and hooks that fetch it.
+- The lifecycle: `open → discussion → proposal → implementation → delivery → evaluation → closed`,
+  with `question`, `bug`, `change`, `review`, `notice`, `task` and `decision` variants. See
+  [PROTOCOL.md](https://github.com/dev-bude/repomoot/blob/main/PROTOCOL.md) — the protocol is documented separately from the code (CC-BY-4.0) and
+  maps onto A2A task states and MCP Tasks.
+- If no Product Owner session is present, a product question stays in the chat of the agent
+  that needs it, with the option to hand it over to the PO later.
+
+Status: pre-release. Local mode works end to end — see [WALKTHROUGH.md](https://github.com/dev-bude/repomoot/blob/main/WALKTHROUGH.md) for one real
+request followed from the user's instruction to the consumer's evaluation. No MCP surface, no
+CI/ephemeral mode yet. Code: Apache-2.0.
+
+## Install
+
+Repomoot is a command-line tool, so install it into its own environment:
+
+```
+pipx install repomoot        # or: uv tool install repomoot
+repomoot --version
+```
+
+Either one puts `repomoot` on your PATH and keeps its dependencies away from your projects.
+Plain `pip install repomoot` works too, inside a virtualenv of your own. Python 3.12+.
+
+Then install the Claude Code adapter (it prints what it will write and asks first):
+
+```
+repomoot install --runtime claude-code --hooks
+```
+
+That adds a 3-line pointer to `~/.claude/CLAUDE.md`, a `/repomoot` skill, and four hooks that call
+`repomoot` by its absolute path — so the agents find it whatever their PATH looks like.
+`repomoot uninstall` reverts the adapter.
+
+Other runtimes: `repomoot install --runtime codex --dir <project>` writes the card into `AGENTS.md`
+(`gemini` → `GEMINI.md`, `cursor` → `.cursorrules`); `repomoot protocol` prints it.
+
+<details>
+<summary>From source (for working on Repomoot itself)</summary>
+
+```
+git clone https://github.com/dev-bude/repomoot.git && cd repomoot
+python -m venv .venv
+.venv/bin/pip install -e ".[dev]"   # Windows: .venv\Scripts\python -m pip install -e ".[dev]"
+.venv/bin/python -m pytest -q       # Windows: .venv\Scripts\python -m pytest -q
+```
+
+The `repomoot` command then lives in `.venv/bin` (Windows: `.venv\Scripts`); add it to your PATH to
+type commands yourself. See [CONTRIBUTING.md](https://github.com/dev-bude/repomoot/blob/main/CONTRIBUTING.md).
+
+</details>
+
+## First steps
+
+Open one Claude Code session per repository (VS Code windows or terminals). In the chat:
+
+```
+/repomoot connect      # once per repository: registers this repo's agent (name = folder) and connects the session
+/repomoot po           # once, in the folder with your product notes: the Product Owner (optional)
+/repomoot ui           # opens the live request tree in the browser
+```
+
+These commands run in the hook with **your** authority before the agent sees them — agents cannot
+register themselves. From then on it is automatic: every new session, `/clear` or resume in a
+registered folder reconnects by itself, and the agent gets a short card: who else is in the
+workspace (agents, repositories, online/offline), how to ask them or order work, how to wait and
+how to wake the others. The first thing an agent does after connecting is record its own address
+(`repomoot address "NAME [ref]"`, from its ListAgents tool) so that other agents can wake it with a
+cross-session message; the daemon starts on demand and restarts itself after an upgrade.
+
+Then just work with the agents as usual. The workspace shows up when an agent needs something from
+another repository:
+
+```
+repomoot req new --to gridlib --type capability --blocking --title "..." --goal "..." --body -
+repomoot wait --req req_0001          # the other agent is woken; this one waits for the answer
+repomoot propose / deliver / evaluate / ask-po / decide / handoff   (each reply prints `next:`)
+```
+
+`/repomoot status`, `/repomoot disconnect` work the same way; dependencies between agents are
+inferred from the requests they send. Everything is also available from your terminal
+(`repomoot agents`, `repomoot req show req_0001`, ...). `repomoot --help`, `repomoot <cmd> --help`;
+every command accepts `--json`. Exit codes: 0 ok, 2 bad arguments, 3 not connected,
+4 forbidden or bad transition, 5 not found, 6 daemon unavailable, 7 wait timeout.
+
+## When something looks stuck
+
+- An agent "went quiet": its turn ended before the answer arrived and nothing woke it. Type
+  `/repomoot inbox` in that session — the hook injects what is new and the agent continues. It
+  happens when the other side could not reach it (no address recorded yet, or the sessions are on
+  different machines); after `repomoot address` the wake-up is automatic.
+- `/repomoot status` in any session shows who is online; `repomoot agents` from the terminal too.
+- Two sessions in one folder: give the second one a name, `repomoot connect --session two`.
+- State lives in `~/.repomoot/` (`REPOMOOT_HOME`), port 7771 (`REPOMOOT_PORT`); delete the folder to
+  start from scratch (stop the daemon first: `repomoot status` shows it, `/admin/shutdown` or kill it).
+
+## Principals
+
+- **Daemon token** (`~/.repomoot/token`): every local client. Lets a session act as an *already
+  registered* agent from that agent's own repository directory.
+- **Human token** (`~/.repomoot/human.token`): registering and editing agents, setting the PO policy,
+  speaking as an agent (`--as`), attesting human decisions. The CLI sends it only from an
+  interactive terminal or via `REPOMOOT_HUMAN_TOKEN` (CI). Agents inside a runtime's shell tool
+  have no TTY and therefore cannot register agents or forge human decisions; a human answer they
+  record is stored as *unattested* and listed for the PO.
+
+State lives in `~/.repomoot/` (`REPOMOOT_HOME`); port 7771 (`REPOMOOT_PORT`). Trust model and data
+notes: [SECURITY.md](https://github.com/dev-bude/repomoot/blob/main/SECURITY.md).
+
+## Reading on
+
+- [WALKTHROUGH.md](https://github.com/dev-bude/repomoot/blob/main/WALKTHROUGH.md) — how a request flows, step by step, with real output.
+- [PROTOCOL.md](https://github.com/dev-bude/repomoot/blob/main/PROTOCOL.md) — lifecycle, roles, artifacts, mapping to A2A / MCP Tasks.
+- [SECURITY.md](https://github.com/dev-bude/repomoot/blob/main/SECURITY.md) — trust model, data, what the adapter writes.
+- [CONTRIBUTING.md](https://github.com/dev-bude/repomoot/blob/main/CONTRIBUTING.md) — how to set up, what is worth working on, house rules.
+
+## Layout
+
+```
+repomoot/core      db, lifecycle, cards (instruction texts), service (all rules)
+repomoot/server    FastAPI daemon: HTTP API, async long-poll and SSE events
+repomoot/client    HTTP client, session files, human principal, daemon autostart
+repomoot/cli       typer CLI + text rendering (quotes and sanitizes other agents' text)
+repomoot/adapters  claude_code: install/uninstall, skill, hooks
+tests/            the walkthrough's flow and the rules, through the API
+```
+
+Tests: `python -m pytest -q`.
+
+## Licence
+
+Code: Apache-2.0 ([LICENSE](https://github.com/dev-bude/repomoot/blob/main/LICENSE), [NOTICE](https://github.com/dev-bude/repomoot/blob/main/NOTICE)). The protocol description
+([PROTOCOL.md](https://github.com/dev-bude/repomoot/blob/main/PROTOCOL.md)): CC BY 4.0.
+
+Claude Code, Codex, Gemini CLI and Cursor are products of their respective owners; Repomoot is an
+independent project and is not affiliated with or endorsed by any of them.

repomoot-0.2.0/README.md

@@ -0,0 +1,157 @@
+# Repomoot
+
+**Requests between AI coding agents that own different repositories — with consumer acceptance
+and owner escalation.**
+
+When several coding agents (Claude Code, Codex, Gemini CLI, your own) work on related
+repositories, there is no working channel between them: you become the courier, the product
+owner and the referee, and the history disappears with every `/clear`. Repomoot gives the agents a
+shared lane for *requests* — "I need X from your repository" — with a lifecycle that ends when the
+**consumer** has verified the result in its own context, a **Product Owner** role for the decisions
+owners must not make alone, and a durable, searchable history.
+
+It is not shared memory, not an orchestrator and not a task board. Agents keep their own runtime,
+context and tools. Repomoot owns requests, messages, artifacts, decisions and events.
+
+## How it works
+
+- A local daemon holds the state (SQLite) and serves an HTTP API. The CLI `repomoot` is a thin
+  client and starts the daemon on demand.
+- Agents talk to it through `repomoot` from their own shell tool — nothing else is required from a
+  runtime. The rules an agent follows (the *protocol card*) are owned by Repomoot and handed to the
+  agent at `repomoot connect`; the Claude Code adapter adds a thin skill and hooks that fetch it.
+- The lifecycle: `open → discussion → proposal → implementation → delivery → evaluation → closed`,
+  with `question`, `bug`, `change`, `review`, `notice`, `task` and `decision` variants. See
+  [PROTOCOL.md](https://github.com/dev-bude/repomoot/blob/main/PROTOCOL.md) — the protocol is documented separately from the code (CC-BY-4.0) and
+  maps onto A2A task states and MCP Tasks.
+- If no Product Owner session is present, a product question stays in the chat of the agent
+  that needs it, with the option to hand it over to the PO later.
+
+Status: pre-release. Local mode works end to end — see [WALKTHROUGH.md](https://github.com/dev-bude/repomoot/blob/main/WALKTHROUGH.md) for one real
+request followed from the user's instruction to the consumer's evaluation. No MCP surface, no
+CI/ephemeral mode yet. Code: Apache-2.0.
+
+## Install
+
+Repomoot is a command-line tool, so install it into its own environment:
+
+```
+pipx install repomoot        # or: uv tool install repomoot
+repomoot --version
+```
+
+Either one puts `repomoot` on your PATH and keeps its dependencies away from your projects.
+Plain `pip install repomoot` works too, inside a virtualenv of your own. Python 3.12+.
+
+Then install the Claude Code adapter (it prints what it will write and asks first):
+
+```
+repomoot install --runtime claude-code --hooks
+```
+
+That adds a 3-line pointer to `~/.claude/CLAUDE.md`, a `/repomoot` skill, and four hooks that call
+`repomoot` by its absolute path — so the agents find it whatever their PATH looks like.
+`repomoot uninstall` reverts the adapter.
+
+Other runtimes: `repomoot install --runtime codex --dir <project>` writes the card into `AGENTS.md`
+(`gemini` → `GEMINI.md`, `cursor` → `.cursorrules`); `repomoot protocol` prints it.
+
+<details>
+<summary>From source (for working on Repomoot itself)</summary>
+
+```
+git clone https://github.com/dev-bude/repomoot.git && cd repomoot
+python -m venv .venv
+.venv/bin/pip install -e ".[dev]"   # Windows: .venv\Scripts\python -m pip install -e ".[dev]"
+.venv/bin/python -m pytest -q       # Windows: .venv\Scripts\python -m pytest -q
+```
+
+The `repomoot` command then lives in `.venv/bin` (Windows: `.venv\Scripts`); add it to your PATH to
+type commands yourself. See [CONTRIBUTING.md](https://github.com/dev-bude/repomoot/blob/main/CONTRIBUTING.md).
+
+</details>
+
+## First steps
+
+Open one Claude Code session per repository (VS Code windows or terminals). In the chat:
+
+```
+/repomoot connect      # once per repository: registers this repo's agent (name = folder) and connects the session
+/repomoot po           # once, in the folder with your product notes: the Product Owner (optional)
+/repomoot ui           # opens the live request tree in the browser
+```
+
+These commands run in the hook with **your** authority before the agent sees them — agents cannot
+register themselves. From then on it is automatic: every new session, `/clear` or resume in a
+registered folder reconnects by itself, and the agent gets a short card: who else is in the
+workspace (agents, repositories, online/offline), how to ask them or order work, how to wait and
+how to wake the others. The first thing an agent does after connecting is record its own address
+(`repomoot address "NAME [ref]"`, from its ListAgents tool) so that other agents can wake it with a
+cross-session message; the daemon starts on demand and restarts itself after an upgrade.
+
+Then just work with the agents as usual. The workspace shows up when an agent needs something from
+another repository:
+
+```
+repomoot req new --to gridlib --type capability --blocking --title "..." --goal "..." --body -
+repomoot wait --req req_0001          # the other agent is woken; this one waits for the answer
+repomoot propose / deliver / evaluate / ask-po / decide / handoff   (each reply prints `next:`)
+```
+
+`/repomoot status`, `/repomoot disconnect` work the same way; dependencies between agents are
+inferred from the requests they send. Everything is also available from your terminal
+(`repomoot agents`, `repomoot req show req_0001`, ...). `repomoot --help`, `repomoot <cmd> --help`;
+every command accepts `--json`. Exit codes: 0 ok, 2 bad arguments, 3 not connected,
+4 forbidden or bad transition, 5 not found, 6 daemon unavailable, 7 wait timeout.
+
+## When something looks stuck
+
+- An agent "went quiet": its turn ended before the answer arrived and nothing woke it. Type
+  `/repomoot inbox` in that session — the hook injects what is new and the agent continues. It
+  happens when the other side could not reach it (no address recorded yet, or the sessions are on
+  different machines); after `repomoot address` the wake-up is automatic.
+- `/repomoot status` in any session shows who is online; `repomoot agents` from the terminal too.
+- Two sessions in one folder: give the second one a name, `repomoot connect --session two`.
+- State lives in `~/.repomoot/` (`REPOMOOT_HOME`), port 7771 (`REPOMOOT_PORT`); delete the folder to
+  start from scratch (stop the daemon first: `repomoot status` shows it, `/admin/shutdown` or kill it).
+
+## Principals
+
+- **Daemon token** (`~/.repomoot/token`): every local client. Lets a session act as an *already
+  registered* agent from that agent's own repository directory.
+- **Human token** (`~/.repomoot/human.token`): registering and editing agents, setting the PO policy,
+  speaking as an agent (`--as`), attesting human decisions. The CLI sends it only from an
+  interactive terminal or via `REPOMOOT_HUMAN_TOKEN` (CI). Agents inside a runtime's shell tool
+  have no TTY and therefore cannot register agents or forge human decisions; a human answer they
+  record is stored as *unattested* and listed for the PO.
+
+State lives in `~/.repomoot/` (`REPOMOOT_HOME`); port 7771 (`REPOMOOT_PORT`). Trust model and data
+notes: [SECURITY.md](https://github.com/dev-bude/repomoot/blob/main/SECURITY.md).
+
+## Reading on
+
+- [WALKTHROUGH.md](https://github.com/dev-bude/repomoot/blob/main/WALKTHROUGH.md) — how a request flows, step by step, with real output.
+- [PROTOCOL.md](https://github.com/dev-bude/repomoot/blob/main/PROTOCOL.md) — lifecycle, roles, artifacts, mapping to A2A / MCP Tasks.
+- [SECURITY.md](https://github.com/dev-bude/repomoot/blob/main/SECURITY.md) — trust model, data, what the adapter writes.
+- [CONTRIBUTING.md](https://github.com/dev-bude/repomoot/blob/main/CONTRIBUTING.md) — how to set up, what is worth working on, house rules.
+
+## Layout
+
+```
+repomoot/core      db, lifecycle, cards (instruction texts), service (all rules)
+repomoot/server    FastAPI daemon: HTTP API, async long-poll and SSE events
+repomoot/client    HTTP client, session files, human principal, daemon autostart
+repomoot/cli       typer CLI + text rendering (quotes and sanitizes other agents' text)
+repomoot/adapters  claude_code: install/uninstall, skill, hooks
+tests/            the walkthrough's flow and the rules, through the API
+```
+
+Tests: `python -m pytest -q`.
+
+## Licence
+
+Code: Apache-2.0 ([LICENSE](https://github.com/dev-bude/repomoot/blob/main/LICENSE), [NOTICE](https://github.com/dev-bude/repomoot/blob/main/NOTICE)). The protocol description
+([PROTOCOL.md](https://github.com/dev-bude/repomoot/blob/main/PROTOCOL.md)): CC BY 4.0.
+
+Claude Code, Codex, Gemini CLI and Cursor are products of their respective owners; Repomoot is an
+independent project and is not affiliated with or endorsed by any of them.

repomoot-0.2.0/pyproject.toml

@@ -0,0 +1,50 @@
+[project]
+name = "repomoot"
+dynamic = ["version"]
+description = "Requests between AI coding agents that own different repositories, with consumer acceptance and owner escalation"
+requires-python = ">=3.12"
+dependencies = ["fastapi>=0.110", "uvicorn>=0.29", "typer>=0.12", "httpx>=0.27"]
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+readme = "README.md"
+keywords = ["ai-agents", "claude-code", "codex", "multi-agent", "request-lifecycle"]
+authors = [{ name = "SimeonAr" }]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Developers",
+    "Environment :: Console",
+    "Framework :: FastAPI",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3 :: Only",
+    "Programming Language :: Python :: 3.12",
+    "Topic :: Software Development :: Version Control",
+]
+
+[project.urls]
+Homepage = "https://github.com/dev-bude/repomoot"
+Repository = "https://github.com/dev-bude/repomoot"
+Issues = "https://github.com/dev-bude/repomoot/issues"
+Protocol = "https://github.com/dev-bude/repomoot/blob/main/PROTOCOL.md"
+Security = "https://github.com/dev-bude/repomoot/blob/main/SECURITY.md"
+
+[project.optional-dependencies]
+dev = ["pytest>=8"]
+
+[project.scripts]
+repomoot = "repomoot.cli.main:app"
+
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[tool.setuptools.dynamic]
+version = {attr = "repomoot.__version__"}
+
+[tool.setuptools.packages.find]
+include = ["repomoot*"]
+
+[tool.setuptools.package-data]
+repomoot = ["server/ui.html"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

repomoot-0.2.0/repomoot/__init__.py

@@ -0,0 +1,4 @@
+"""Repomoot."""
+
+__version__ = "0.2.0"
+PROTOCOL_VERSION = 1

repomoot-0.2.0/repomoot/adapters/__init__.py

@@ -0,0 +1 @@
+

repomoot-0.2.0/repomoot/adapters/claude_code/__init__.py

@@ -0,0 +1 @@
+