Murmurent: development repository

This is where Murmurent is written. To install and use Murmurent, go to hallettmiket/murmurent instead.

▶ Watch the 7-minute getting-started video

📖 Documentation: https://mikehallett.science/murmurent/ (updated at each release). The documentation as it stands in this repository, before release, is previewed at https://mikehallett.science/murmurent_dev/.

You need git, Claude Code and uv.

Set up

git clone [email protected]:hallettmiket/murmurent_dev.git ~/repos/murmurent_dev
cd ~/repos/murmurent_dev
uv tool install --python 3.12 -e .   # install Murmurent from this folder
murmurent install                    # connect it to Claude Code
murmurent doctor                     # check it worked

Murmurent now runs from this folder. An edit to an agent takes effect in the next Claude Code session, with no command to run.

Update

git pull
murmurent install

Making a change

git checkout -b fix/<issue-number>-<short-name>   # 1. work on a branch, not main
# 2. make the change, and add a test in tests/
uv run --python 3.12 --extra dev pytest -q        # 3. check nothing broke
python3 release/check_allowlist.py                #    and that new files are classified
git push -u origin HEAD                           # 4. upload the branch
gh pr create --fill --base main                   #    and ask for review

Each step in full, with the reasons: CONTRIBUTING.md.

More

I want to…	Read
understand how Murmurent fits together	CLAUDE.md
fix an awkward install, or publish a release	DEVELOPING.md
change what users see on GitHub	release/README_public.md, not this file
change the documentation website	the files in docs/; see CONTRIBUTING.md
report a problem or ask for a feature	open an issue

---

Code of Conduct. Apache-2.0 (LICENSE). Mike Hallett, [email protected]