copse-agents 0.1.0__tar.gz

copse_agents-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,32 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+  workflow_call:
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        python: ["3.11", "3.12", "3.13"]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v7
+      - name: Install tmux
+        run: |
+          if [ "$RUNNER_OS" = "Linux" ]; then sudo apt-get update -q && sudo apt-get install -yq tmux
+          else brew install tmux; fi
+      - uses: astral-sh/setup-uv@v10.2.0
+        with:
+          python-version: ${{ matrix.python }}
+      - run: uv sync
+      - run: uv run pytest -q
+        env:
+          PYTHONPATH: tests

copse_agents-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,50 @@
+# Publishes to PyPI when a GitHub release is published, via Trusted Publishing
+# (no API token). PyPI must list this repo, workflow file "publish.yml", and
+# environment "pypi" as a trusted publisher for the copse-agents project.
+name: Publish
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    uses: ./.github/workflows/ci.yml
+
+  build:
+    needs: test
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v10.2.0
+      - name: Check the release tag matches the package version
+        run: |
+          version=$(grep -m1 '^version = ' pyproject.toml | cut -d'"' -f2)
+          tag="${GITHUB_REF_NAME#v}"
+          if [ "$version" != "$tag" ]; then
+            echo "::error::release tag $GITHUB_REF_NAME doesn't match pyproject version $version"
+            exit 1
+          fi
+      - run: uv build
+      - uses: actions/upload-artifact@v7
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/copse-agents
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v8
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

copse_agents-0.1.0/.gitignore

@@ -0,0 +1,4 @@
+.venv/
+__pycache__/
+*.egg-info/
+.pytest_cache/

copse_agents-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 [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.
+

copse_agents-0.1.0/PKG-INFO

@@ -0,0 +1,183 @@
+Metadata-Version: 2.4
+Name: copse-agents
+Version: 0.1.0
+Summary: Orchestrate CLI coding agents in tmux, each on its own git worktree and branch
+Project-URL: Homepage, https://github.com/hmlerner/copse-agents
+Project-URL: Repository, https://github.com/hmlerner/copse-agents
+Project-URL: Issues, https://github.com/hmlerner/copse-agents/issues
+Author: Hannah Lerner
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agents,ai,claude-code,codex,git,mcp,orchestration,tmux,worktree
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development
+Classifier: Topic :: Software Development :: Version Control :: Git
+Requires-Python: >=3.11
+Requires-Dist: mcp<3,>=2.2
+Requires-Dist: typer>=0.12
+Description-Content-Type: text/markdown
+
+# copse
+
+*Published on PyPI as `copse-agents`; the command is `copse`. This project is
+unrelated to the Copse desktop app at copse.dev.*
+
+Run CLI coding agents (Claude Code, Codex, …) in tmux. Each one works on its own
+git branch in its own worktree, and a supervisor agent can delegate to workers,
+review their branches, and merge them back.
+
+copse combines two ideas:
+
+- **From [CAO](https://github.com/awslabs/cli-agent-orchestrator):** agents in tmux
+  sessions, supervisor→worker delegation over MCP (`handoff`, `assign`,
+  `send_message`), an inbox that delivers messages when an agent goes idle, and
+  markdown agent profiles.
+- **From [Superset](https://github.com/superset-sh/superset):** each workspace is a
+  worktree on its own branch, cut from a freshly fetched base. Each repo can
+  define setup/teardown scripts, local files to copy in, and gets a port block
+  per workspace. You can diff against the base, sync, commit, push, open a PR,
+  and merge back. Removal checks for uncommitted changes and keeps the branch.
+
+## Install
+
+```sh
+brew install tmux
+uv tool install copse-agents                  # once published
+uv tool install --editable ~/Projects/copse   # from a local checkout
+```
+
+## Quick start
+
+```sh
+cd ~/code/myapp
+copse init                                  # optional: writes .copse/config.json
+copse new fix-login -p "Fix the login redirect bug; add a test"
+copse ls                                    # workspaces, agents, ahead/behind
+copse attach fix-login                      # watch or talk to the agent
+copse diff fix-login --stat
+copse pr fix-login                          # push + gh pr create
+copse rm fix-login                          # keeps the branch
+```
+
+Or let a supervisor split up the work:
+
+```sh
+copse start -p "Add CSV export to reports and a settings page; tests for both"
+# a supervisor starts in this checkout. It calls assign(...) once per task, each
+# worker gets branch copse/developer/<task>-xxxx, and the supervisor reviews
+# with workspace_diff and merges with merge_workspace.
+```
+
+## Commands
+
+| | |
+|---|---|
+| `copse new BRANCH [-b BASE] [-a PROFILE] [-p PROMPT]` | worktree + branch + agent |
+| `copse start [-a supervisor]` | agent in the current checkout |
+| `copse ls [--all]` | workspaces and agents |
+| `copse attach / cd / open [WS]` | tmux session / path / editor |
+| `copse status / diff [--stat] [WS]` | compared with the base branch (committed + uncommitted) |
+| `copse sync [--merge] [WS]` | rebase (or merge) the latest base into the branch |
+| `copse commit -m MSG / push / pr [WS]` | ship it |
+| `copse merge [--squash] [WS]` | merge into the base locally |
+| `copse rm WS [-f] [-D]` | remove the worktree; `-D` deletes the branch too, only if merged unless `-f` |
+| `copse send AGENT MSG` | message an agent; waits in its inbox until it's idle |
+| `copse agent spawn/kill/peek/profiles` | manage agents |
+
+With no `WS` argument, commands act on the workspace you're in.
+
+## Repo config: `.copse/config.json`
+
+```json
+{
+  "setup": ["pnpm install", "cp \"$COPSE_ROOT_PATH/.env.local\" ."],
+  "teardown": ["docker compose down"],
+  "copy": [".env", "apps/*/.env"],
+  "base_branch": "main",
+  "branch_prefix": "",
+  "default_agent": "developer",
+  "fetch": true
+}
+```
+
+`.copse/config.local.json` is gitignored and overrides keys for you only. For
+`setup`/`teardown` it can also give `{"before": [...], "after": [...]}` to run
+commands around the team's list.
+
+Setup, teardown, and agents all see these variables: `COPSE_ROOT_PATH`,
+`COPSE_WORKSPACE_PATH`, `COPSE_WORKSPACE_NAME`, `COPSE_WORKSPACE_ID`,
+`COPSE_BRANCH`, `COPSE_BASE_BRANCH`, and `COPSE_PORT_BASE`. Each workspace gets
+ten ports, from `COPSE_PORT_BASE` to `COPSE_PORT_BASE+9`, so parallel dev
+servers don't collide. Agents also get `COPSE_AGENT_ID`.
+
+## Agent profiles
+
+Markdown files with frontmatter. copse looks in `.copse/agents/`, then
+`~/.copse/agents/`, then its built-ins (`supervisor`, `developer`, `reviewer`):
+
+```markdown
+---
+name: frontend
+description: React/TypeScript specialist
+provider: claude          # claude | codex | shell
+model: sonnet             # optional
+permission_mode: acceptEdits   # optional, Claude Code only
+---
+You are a frontend engineer...
+```
+
+**Permissions.** Workers run with Claude Code's normal permission prompts. When a
+worker is waiting on one, `copse ls` shows it as `waiting`, and you attach to
+approve it. The built-in `developer` profile edits files without asking
+(`acceptEdits`) and has an `allowed_tools` list covering git inspect/commit and
+common test/build commands: `pytest`, `uv run`, `npm/pnpm/yarn test|run`,
+`cargo`, `go`, `make`, `swift`, `xcodebuild`. It can't push or run arbitrary
+commands. Note that `npm run`, `make`, and `uv run` execute whatever the repo
+defines, so only point workers at repos you trust. Override the list in
+`.copse/agents/developer.md`.
+
+## How it works
+
+- **State** lives in `~/.copse/copse.db` (SQLite, WAL mode). The CLI, the hooks,
+  and every agent's MCP server share it. Worktrees live in
+  `~/.copse/worktrees/<repo>/<branch>`, and the base branch is recorded in git
+  config as `branch.<b>.copse-base`.
+- **Agent status comes from hooks, not screen-scraping.** CAO works out whether
+  Claude Code is idle by regex-matching the terminal, which breaks whenever the
+  TUI changes. copse launches Claude Code with `--settings` hooks
+  (`SessionStart`, `UserPromptSubmit`, `Stop`, `Notification`) that call
+  `copse _hook <event>`. The `Stop` hook also delivers queued messages: it
+  returns `{"decision": "block", "reason": <message>}`, so Claude continues with
+  the message as its next instruction and nothing is typed into a busy terminal.
+- **Results are explicit.** Workers call the `report_result` MCP tool instead of
+  having their output parsed from the screen. If a worker stops without
+  reporting, the Stop hook reminds it once.
+- **Worker isolation:** `handoff`/`assign` with `isolate=true` (the default)
+  create a worktree whose branch starts from the *supervisor's* current branch,
+  so workers build on the supervisor's committed work. `merge_workspace`
+  brings a worker's branch back.
+
+## Development
+
+```sh
+uv sync
+PYTHONPATH=tests uv run pytest
+```
+
+### Releasing
+
+1. Bump `version` in `pyproject.toml`, commit, and push.
+2. Create a GitHub release tagged `v<version>` (e.g. `gh release create v0.1.1 --generate-notes`).
+3. The Publish workflow tests, builds, and uploads to PyPI via Trusted Publishing.
+
+## License
+
+Apache-2.0

copse_agents-0.1.0/README.md

@@ -0,0 +1,156 @@
+# copse
+
+*Published on PyPI as `copse-agents`; the command is `copse`. This project is
+unrelated to the Copse desktop app at copse.dev.*
+
+Run CLI coding agents (Claude Code, Codex, …) in tmux. Each one works on its own
+git branch in its own worktree, and a supervisor agent can delegate to workers,
+review their branches, and merge them back.
+
+copse combines two ideas:
+
+- **From [CAO](https://github.com/awslabs/cli-agent-orchestrator):** agents in tmux
+  sessions, supervisor→worker delegation over MCP (`handoff`, `assign`,
+  `send_message`), an inbox that delivers messages when an agent goes idle, and
+  markdown agent profiles.
+- **From [Superset](https://github.com/superset-sh/superset):** each workspace is a
+  worktree on its own branch, cut from a freshly fetched base. Each repo can
+  define setup/teardown scripts, local files to copy in, and gets a port block
+  per workspace. You can diff against the base, sync, commit, push, open a PR,
+  and merge back. Removal checks for uncommitted changes and keeps the branch.
+
+## Install
+
+```sh
+brew install tmux
+uv tool install copse-agents                  # once published
+uv tool install --editable ~/Projects/copse   # from a local checkout
+```
+
+## Quick start
+
+```sh
+cd ~/code/myapp
+copse init                                  # optional: writes .copse/config.json
+copse new fix-login -p "Fix the login redirect bug; add a test"
+copse ls                                    # workspaces, agents, ahead/behind
+copse attach fix-login                      # watch or talk to the agent
+copse diff fix-login --stat
+copse pr fix-login                          # push + gh pr create
+copse rm fix-login                          # keeps the branch
+```
+
+Or let a supervisor split up the work:
+
+```sh
+copse start -p "Add CSV export to reports and a settings page; tests for both"
+# a supervisor starts in this checkout. It calls assign(...) once per task, each
+# worker gets branch copse/developer/<task>-xxxx, and the supervisor reviews
+# with workspace_diff and merges with merge_workspace.
+```
+
+## Commands
+
+| | |
+|---|---|
+| `copse new BRANCH [-b BASE] [-a PROFILE] [-p PROMPT]` | worktree + branch + agent |
+| `copse start [-a supervisor]` | agent in the current checkout |
+| `copse ls [--all]` | workspaces and agents |
+| `copse attach / cd / open [WS]` | tmux session / path / editor |
+| `copse status / diff [--stat] [WS]` | compared with the base branch (committed + uncommitted) |
+| `copse sync [--merge] [WS]` | rebase (or merge) the latest base into the branch |
+| `copse commit -m MSG / push / pr [WS]` | ship it |
+| `copse merge [--squash] [WS]` | merge into the base locally |
+| `copse rm WS [-f] [-D]` | remove the worktree; `-D` deletes the branch too, only if merged unless `-f` |
+| `copse send AGENT MSG` | message an agent; waits in its inbox until it's idle |
+| `copse agent spawn/kill/peek/profiles` | manage agents |
+
+With no `WS` argument, commands act on the workspace you're in.
+
+## Repo config: `.copse/config.json`
+
+```json
+{
+  "setup": ["pnpm install", "cp \"$COPSE_ROOT_PATH/.env.local\" ."],
+  "teardown": ["docker compose down"],
+  "copy": [".env", "apps/*/.env"],
+  "base_branch": "main",
+  "branch_prefix": "",
+  "default_agent": "developer",
+  "fetch": true
+}
+```
+
+`.copse/config.local.json` is gitignored and overrides keys for you only. For
+`setup`/`teardown` it can also give `{"before": [...], "after": [...]}` to run
+commands around the team's list.
+
+Setup, teardown, and agents all see these variables: `COPSE_ROOT_PATH`,
+`COPSE_WORKSPACE_PATH`, `COPSE_WORKSPACE_NAME`, `COPSE_WORKSPACE_ID`,
+`COPSE_BRANCH`, `COPSE_BASE_BRANCH`, and `COPSE_PORT_BASE`. Each workspace gets
+ten ports, from `COPSE_PORT_BASE` to `COPSE_PORT_BASE+9`, so parallel dev
+servers don't collide. Agents also get `COPSE_AGENT_ID`.
+
+## Agent profiles
+
+Markdown files with frontmatter. copse looks in `.copse/agents/`, then
+`~/.copse/agents/`, then its built-ins (`supervisor`, `developer`, `reviewer`):
+
+```markdown
+---
+name: frontend
+description: React/TypeScript specialist
+provider: claude          # claude | codex | shell
+model: sonnet             # optional
+permission_mode: acceptEdits   # optional, Claude Code only
+---
+You are a frontend engineer...
+```
+
+**Permissions.** Workers run with Claude Code's normal permission prompts. When a
+worker is waiting on one, `copse ls` shows it as `waiting`, and you attach to
+approve it. The built-in `developer` profile edits files without asking
+(`acceptEdits`) and has an `allowed_tools` list covering git inspect/commit and
+common test/build commands: `pytest`, `uv run`, `npm/pnpm/yarn test|run`,
+`cargo`, `go`, `make`, `swift`, `xcodebuild`. It can't push or run arbitrary
+commands. Note that `npm run`, `make`, and `uv run` execute whatever the repo
+defines, so only point workers at repos you trust. Override the list in
+`.copse/agents/developer.md`.
+
+## How it works
+
+- **State** lives in `~/.copse/copse.db` (SQLite, WAL mode). The CLI, the hooks,
+  and every agent's MCP server share it. Worktrees live in
+  `~/.copse/worktrees/<repo>/<branch>`, and the base branch is recorded in git
+  config as `branch.<b>.copse-base`.
+- **Agent status comes from hooks, not screen-scraping.** CAO works out whether
+  Claude Code is idle by regex-matching the terminal, which breaks whenever the
+  TUI changes. copse launches Claude Code with `--settings` hooks
+  (`SessionStart`, `UserPromptSubmit`, `Stop`, `Notification`) that call
+  `copse _hook <event>`. The `Stop` hook also delivers queued messages: it
+  returns `{"decision": "block", "reason": <message>}`, so Claude continues with
+  the message as its next instruction and nothing is typed into a busy terminal.
+- **Results are explicit.** Workers call the `report_result` MCP tool instead of
+  having their output parsed from the screen. If a worker stops without
+  reporting, the Stop hook reminds it once.
+- **Worker isolation:** `handoff`/`assign` with `isolate=true` (the default)
+  create a worktree whose branch starts from the *supervisor's* current branch,
+  so workers build on the supervisor's committed work. `merge_workspace`
+  brings a worker's branch back.
+
+## Development
+
+```sh
+uv sync
+PYTHONPATH=tests uv run pytest
+```
+
+### Releasing
+
+1. Bump `version` in `pyproject.toml`, commit, and push.
+2. Create a GitHub release tagged `v<version>` (e.g. `gh release create v0.1.1 --generate-notes`).
+3. The Publish workflow tests, builds, and uploads to PyPI via Trusted Publishing.
+
+## License
+
+Apache-2.0

copse_agents-0.1.0/pyproject.toml

@@ -0,0 +1,53 @@
+[project]
+name = "copse-agents"
+version = "0.1.0"
+description = "Orchestrate CLI coding agents in tmux, each on its own git worktree and branch"
+readme = "README.md"
+requires-python = ">=3.11"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+authors = [{ name = "Hannah Lerner" }]
+keywords = ["ai", "agents", "claude-code", "codex", "git", "worktree", "tmux", "mcp", "orchestration"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Environment :: Console",
+    "Intended Audience :: Developers",
+    "Operating System :: MacOS",
+    "Operating System :: POSIX :: Linux",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Software Development",
+    "Topic :: Software Development :: Version Control :: Git",
+]
+dependencies = [
+    "typer>=0.12",
+    "mcp>=2.2,<3",
+]
+
+[project.urls]
+Homepage = "https://github.com/hmlerner/copse-agents"
+Repository = "https://github.com/hmlerner/copse-agents"
+Issues = "https://github.com/hmlerner/copse-agents/issues"
+
+[project.scripts]
+copse = "copse.cli:app"
+
+[dependency-groups]
+dev = ["pytest>=8"]
+
+[build-system]
+requires = ["hatchling>=1.27"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/copse"]
+# Metadata 2.5 is newer than twine/PyPI tooling reliably accepts.
+core-metadata-version = "2.4"
+
+[tool.hatch.build.targets.sdist]
+core-metadata-version = "2.4"
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]