Vincent/work-app
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Make the M1 marker side-aware: M1 is the worker, M5 relays

Browse Source 
The marker is committed, so M1's own agent reads it too. The first version
told whichever side read it to run m1-say — on M1 that meant relaying to
itself. Now each side is told its role by a one-line check for the M1-only
token file.
This commit is contained in:
Vincent
2026-09-03 13:11:37 +02:00
parent b254d3c06e
commit d26b1f7b29
1 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+8 -3
View File
@@ -2,9 +2,14 @@
## This project lives on M1 ## This project lives on M1
All coding, browsing, testing and compiling for this project happens on the All coding, browsing, testing and compiling for this project happens on the
always-on **M1** server, prompted from here. This folder on the M5 is a always-on **M1** server. First find out which side you are on — run once:
**read-only git mirror** — do not edit files here and do not run builds or tests `test -f ~/.config/claude-m1.env && echo "I am M1" || echo "I am the M5"`.
here.
**On M1 — you are the worker.** Work normally in this repo: read, edit, build,
test and commit here. Ignore the relay notes below; they are for the other Mac.
**On the M5 — this folder is a read-only git mirror.** Do not edit files here
and do not run builds or tests here.
- For **every** message about this project, run `m1-say "<the message>"` and - For **every** message about this project, run `m1-say "<the message>"` and
show M1's reply. M1's agent does the work, on M1, and keeps going even when show M1's reply. M1's agent does the work, on M1, and keeps going even when