spanreed-bus 0.0.1__tar.gz

spanreed_bus-0.0.1/.claude/settings.local.json

@@ -0,0 +1,8 @@
+{
+  "permissions": {
+    "allow": [
+      "mcp__plugin_spanreed_spanreed__list_agents",
+      "mcp__plugin_spanreed_spanreed__send_message"
+    ]
+  }
+}

spanreed_bus-0.0.1/.claude-plugin/marketplace.json

@@ -0,0 +1,18 @@
+{
+  "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
+  "name": "spanreed",
+  "description": "Spanreed inter-agent message bus for local Claude Code sessions",
+  "owner": {
+    "name": "Jason Monk",
+    "email": "monkopedia@gmail.com"
+  },
+  "plugins": [
+    {
+      "name": "spanreed",
+      "description": "Inter-agent message bus: register sessions, exchange messages, escalate to user when needed.",
+      "source": "./plugins/spanreed",
+      "category": "productivity",
+      "homepage": "https://github.com/Monkopedia/spanreed"
+    }
+  ]
+}

spanreed_bus-0.0.1/.github/workflows/ci.yml

@@ -0,0 +1,33 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  check:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+        with:
+          enable-cache: true
+
+      - name: Sync dependencies
+        run: uv sync --frozen
+
+      - name: Format check
+        run: uv run ruff format --check
+
+      - name: Lint
+        run: uv run ruff check
+
+      - name: Type check
+        run: uv run pyright
+
+      - name: Test
+        run: uv run pytest

spanreed_bus-0.0.1/.gitignore

@@ -0,0 +1,30 @@
+# OS
+.DS_Store
+Thumbs.db
+
+# Editor
+.vscode/
+.idea/
+*.swp
+*~
+
+# Python
+__pycache__/
+*.pyc
+*.pyo
+.venv/
+venv/
+*.egg-info/
+build/
+dist/
+.pytest_cache/
+.ruff_cache/
+.pyright/
+.python-version.local
+
+# Node
+node_modules/
+
+# Spanreed runtime state (when we have it)
+state/
+*.log

spanreed_bus-0.0.1/.pre-commit-config.yaml

@@ -0,0 +1,26 @@
+repos:
+  - repo: local
+    hooks:
+      - id: ruff-format
+        name: ruff format
+        entry: uv run ruff format
+        language: system
+        types: [python]
+      - id: ruff-check
+        name: ruff check
+        entry: uv run ruff check --fix
+        language: system
+        types: [python]
+      - id: pyright
+        name: pyright
+        entry: uv run pyright
+        language: system
+        types: [python]
+        pass_filenames: false
+      - id: pytest
+        name: pytest
+        entry: uv run pytest -q
+        language: system
+        types: [python]
+        pass_filenames: false
+        stages: [pre-push]

spanreed_bus-0.0.1/.python-version

@@ -0,0 +1 @@
+3.12

spanreed_bus-0.0.1/CLAUDE.md

@@ -0,0 +1,67 @@
+# Working in this repo
+
+Project ethos: **correctness over speed**. Claude can make development fast; the human's job is to ensure it stays correct and maintainable. These rules exist to keep that property as the codebase grows.
+
+## Architecture summary
+
+Spanreed is an inter-agent message bus for local Claude Code sessions. Each session runs a plugin (`plugins/spanreed/`) that includes:
+
+- A **SessionStart hook** that injects bus topology into Claude's context.
+- A **Monitor** that surfaces inbox notifications as Claude wakes events.
+- An **MCP server** (`src/spanreed/mcp_server.py`) providing typed bus tools.
+
+Sessions coordinate through filesystem state under `~/.claude/spanreed/` (registry, per-agent inboxes, per-session cursors). There is no central daemon; each plugin's MCP server is per-session and reads/writes shared files.
+
+`docs/architecture.md` is the authoritative design doc. `docs/protocol.md` is the bus wire-format spec. Always defer to those over inference from code.
+
+## Rules
+
+1. **Docs are authoritative for design.** Behavior changes (especially anything that touches the wire format, the MCP tool surface, or filesystem layout) require updating `docs/architecture.md` or `docs/protocol.md` in the same commit. Don't infer design from code; if the doc is wrong, fix the doc.
+
+2. **Tests required for new code paths.** If you add a function, add a test. If you change behavior, update the test. Run `make test` before commit. Pre-commit gates this.
+
+3. **Findings ≠ design.** Empirical results from running experiments go in `docs/findings.md`. Decisions about how things *should* work go in `docs/architecture.md` or `docs/protocol.md`. Don't mix them.
+
+4. **Open questions get tracked.** If a design decision was deferred, it goes in `docs/open-questions.md` — don't leave TODO comments in code as a substitute.
+
+5. **No silent scope creep.** Don't add features, refactor adjacent code, or introduce abstractions beyond what the task requires. Cleanups belong in their own commits with a description of why.
+
+6. **The README is tested by being run.** If you change install or usage flow, manually re-run the README commands and update them in the same commit. The README is not aspirational; it is the truth.
+
+7. **Visibility over hiding.** For anything user-facing in bus UX (notification text, status indicators, monitor output), prefer verbose and legible over clean and hidden. The user wants to *see* inter-agent reasoning, not abstract it away.
+
+8. **Surface design calls, don't decide alone.** When implementing reveals a design ambiguity not covered by the docs, ask the user before deciding. Then update the docs with the resolution.
+
+## How to run things
+
+```bash
+make install      # sync dependencies
+make test         # run pytest
+make lint         # ruff check + pyright
+make fmt          # ruff format + ruff check --fix
+make check        # everything (CI parity)
+```
+
+For dev install of the plugin: `make install-plugin` (puts the plugin into Claude Code at user scope from the local dir).
+
+## Commit style
+
+- Subject line ≤ 70 chars, present tense, explains intent.
+- Body explains the **why**, not the what.
+- Co-author trailer for Claude commits (the harness adds this automatically).
+- One concern per commit; mixed-concern commits get split.
+
+## Where things live
+
+```
+src/spanreed/      Python package (MCP server, store, CLI)
+tests/             pytest tests (unit/, integration/)
+plugins/spanreed/  the real Claude Code plugin
+experiments/       validation scaffolds from the design phase (kept for reference)
+docs/              architecture, protocol, findings, open questions
+.claude-plugin/    marketplace manifest (this repo doubles as a single-plugin marketplace)
+```
+
+## Git workflow
+
+For now: **direct commits to main** with discipline (pre-commit must pass). Once v1 is usable, switch to **PR-based workflow** and dogfood spanreed for cross-session PR review (the project's whole motivating use case).

spanreed_bus-0.0.1/LICENSE

@@ -0,0 +1,201 @@
+                                 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 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 or 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 Support. 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 support.
+
+   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 Jason Monk
+
+   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.

spanreed_bus-0.0.1/Makefile

@@ -0,0 +1,61 @@
+.PHONY: install install-dev uninstall test lint fmt fmt-check check clean experiment-monitor experiment-cross-session help
+
+UV := uv
+PYTHON := $(UV) run python
+
+help:
+	@echo "Common targets:"
+	@echo "  make install         - install spanreed-bus + dev deps (editable)"
+	@echo "  make install-plugin  - load the spanreed plugin into Claude Code (user scope)"
+	@echo "  make uninstall       - remove installed spanreed-bus"
+	@echo "  make test            - run pytest"
+	@echo "  make lint            - run ruff check + pyright"
+	@echo "  make fmt             - run ruff format + ruff check --fix"
+	@echo "  make fmt-check       - verify formatting without modifying"
+	@echo "  make check           - fmt-check + lint + test (CI parity)"
+	@echo "  make clean           - remove build/cache artifacts"
+	@echo "  make experiment-monitor          - launch the bus-test plugin"
+	@echo "  make experiment-cross-session    - print instructions for the cross-session test"
+
+install:
+	$(UV) sync
+
+install-plugin:
+	@echo "Loading plugin from $(CURDIR)/plugins/spanreed into Claude Code (user scope)..."
+	claude /plugin install $(CURDIR)/plugins/spanreed --scope user
+
+uninstall:
+	$(UV) tool uninstall spanreed-bus 2>/dev/null || true
+
+test:
+	$(UV) run pytest
+
+lint:
+	$(UV) run ruff check
+	$(UV) run pyright
+
+fmt:
+	$(UV) run ruff format
+	$(UV) run ruff check --fix
+
+fmt-check:
+	$(UV) run ruff format --check
+	$(UV) run ruff check
+
+check: fmt-check lint test
+
+clean:
+	rm -rf build/ dist/ .pytest_cache/ .ruff_cache/ .pyright/ src/*.egg-info/
+	find . -type d -name __pycache__ -prune -exec rm -rf {} +
+
+experiment-monitor:
+	claude --plugin-dir $(CURDIR)/experiments/bus-test
+
+experiment-cross-session:
+	@echo "Cross-session test requires two terminals. In two separate terminals, run:"
+	@echo ""
+	@echo "  rm -rf /tmp/spanreed-test  # reset state once before either session starts"
+	@echo "  claude --plugin-dir $(CURDIR)/experiments/cross-session/spanreed-alice"
+	@echo "  claude --plugin-dir $(CURDIR)/experiments/cross-session/spanreed-bob"
+	@echo ""
+	@echo "Then in alice's terminal, try: 'Send a message to bob asking what TS version they use.'"

spanreed_bus-0.0.1/PKG-INFO

@@ -0,0 +1,91 @@
+Metadata-Version: 2.4
+Name: spanreed-bus
+Version: 0.0.1
+Summary: Inter-agent message bus for local Claude Code sessions
+Project-URL: Repository, https://github.com/Monkopedia/spanreed
+Author-email: Jason Monk <monkopedia@gmail.com>
+License: Apache-2.0
+License-File: LICENSE
+Keywords: agent,bus,claude-code,ipc,mcp
+Classifier: Development Status :: 3 - Alpha
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Requires-Python: >=3.12
+Requires-Dist: anyio>=4.0
+Requires-Dist: mcp>=1.0
+Requires-Dist: pydantic>=2.0
+Description-Content-Type: text/markdown
+
+# Spanreed
+
+An inter-agent message bus for local Claude Code sessions. Run one Claude session per repo; let them coordinate.
+
+> **Status**: alpha. The architecture and primitives are validated (see [`docs/findings.md`](docs/findings.md)) and a working implementation is in place — pending end-to-end manual smoke test in real Claude Code. Not yet published to PyPI or the official marketplace.
+
+Named after the [spanreed](https://stormlightarchive.fandom.com/wiki/Spanreed): a paired magical writing tool from the Stormlight Archive that transmits text across vast distances. One side writes, the other side reads.
+
+## Install
+
+Once published (not yet on PyPI):
+
+```bash
+uv tool install spanreed-bus
+claude /plugin marketplace add Monkopedia/spanreed
+claude /plugin install spanreed@spanreed
+```
+
+For now, from a local clone:
+
+```bash
+git clone git@github.com:Monkopedia/spanreed.git
+cd spanreed
+uv tool install --editable .
+claude /plugin install $(pwd)/plugins/spanreed --scope user
+```
+
+The MCP server (`spanreed-mcp`) and CLI (`spanreed`) need to be on `$PATH` for the plugin to find them — `uv tool install` handles this.
+
+## Quickstart
+
+Open two terminals, each in a different repo:
+
+```bash
+# Terminal A
+cd ~/projects/repo-a && claude
+
+# Terminal B
+cd ~/projects/repo-b && claude
+```
+
+In terminal A, ask Claude to talk to the other session:
+
+> Ask agent at repo-b what version of Node it's using.
+
+Claude in repo-A discovers the peer, sends the question, the peer answers, the answer comes back. The conversation is visible in both transcripts.
+
+## How it works
+
+Two layers on Claude Code primitives:
+
+- **MCP server** (`spanreed-mcp`, per-session) exposes the bus API as typed tools: register, send, recv, list, `wait_for_reply` with timeout.
+- **Plugin** (auto-loaded) wires up a SessionStart hook for bus context, a Monitor for inbound wakeups, and points Claude at the MCP server.
+
+State lives under `~/.claude/spanreed/` (registry + per-agent inboxes + per-session cursors). No central daemon — each session's MCP server is local and coordinates through shared files.
+
+Read the full design in [`docs/architecture.md`](docs/architecture.md). Wire-format spec in [`docs/protocol.md`](docs/protocol.md).
+
+## Update
+
+```bash
+uv tool upgrade spanreed-bus
+claude /plugin update spanreed@spanreed
+```
+
+## Development
+
+See [`docs/development.md`](docs/development.md) for environment setup, running tests, and contribution conventions. The [`CLAUDE.md`](CLAUDE.md) at the root captures the discipline rules — Claude sessions working on this repo should read it.
+
+## License
+
+[Apache-2.0](LICENSE).

spanreed_bus-0.0.1/README.md

@@ -0,0 +1,72 @@
+# Spanreed
+
+An inter-agent message bus for local Claude Code sessions. Run one Claude session per repo; let them coordinate.
+
+> **Status**: alpha. The architecture and primitives are validated (see [`docs/findings.md`](docs/findings.md)) and a working implementation is in place — pending end-to-end manual smoke test in real Claude Code. Not yet published to PyPI or the official marketplace.
+
+Named after the [spanreed](https://stormlightarchive.fandom.com/wiki/Spanreed): a paired magical writing tool from the Stormlight Archive that transmits text across vast distances. One side writes, the other side reads.
+
+## Install
+
+Once published (not yet on PyPI):
+
+```bash
+uv tool install spanreed-bus
+claude /plugin marketplace add Monkopedia/spanreed
+claude /plugin install spanreed@spanreed
+```
+
+For now, from a local clone:
+
+```bash
+git clone git@github.com:Monkopedia/spanreed.git
+cd spanreed
+uv tool install --editable .
+claude /plugin install $(pwd)/plugins/spanreed --scope user
+```
+
+The MCP server (`spanreed-mcp`) and CLI (`spanreed`) need to be on `$PATH` for the plugin to find them — `uv tool install` handles this.
+
+## Quickstart
+
+Open two terminals, each in a different repo:
+
+```bash
+# Terminal A
+cd ~/projects/repo-a && claude
+
+# Terminal B
+cd ~/projects/repo-b && claude
+```
+
+In terminal A, ask Claude to talk to the other session:
+
+> Ask agent at repo-b what version of Node it's using.
+
+Claude in repo-A discovers the peer, sends the question, the peer answers, the answer comes back. The conversation is visible in both transcripts.
+
+## How it works
+
+Two layers on Claude Code primitives:
+
+- **MCP server** (`spanreed-mcp`, per-session) exposes the bus API as typed tools: register, send, recv, list, `wait_for_reply` with timeout.
+- **Plugin** (auto-loaded) wires up a SessionStart hook for bus context, a Monitor for inbound wakeups, and points Claude at the MCP server.
+
+State lives under `~/.claude/spanreed/` (registry + per-agent inboxes + per-session cursors). No central daemon — each session's MCP server is local and coordinates through shared files.
+
+Read the full design in [`docs/architecture.md`](docs/architecture.md). Wire-format spec in [`docs/protocol.md`](docs/protocol.md).
+
+## Update
+
+```bash
+uv tool upgrade spanreed-bus
+claude /plugin update spanreed@spanreed
+```
+
+## Development
+
+See [`docs/development.md`](docs/development.md) for environment setup, running tests, and contribution conventions. The [`CLAUDE.md`](CLAUDE.md) at the root captures the discipline rules — Claude sessions working on this repo should read it.
+
+## License
+
+[Apache-2.0](LICENSE).