docs: per-agent IAK_NEW_FILE scoping (responder-lock trap) - #63
Conversation
Two real incidents (grok session muting @claudemb's voice 15-16 Aug): session hooks bound to the default notification file claim the machine's room-responder lock across agents. Document the per-agent IAK_NEW_FILE requirement in the env table. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0bffd832bf
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| | `IAK_API_KEY` | (required) | GroupMind API key | | ||
| | `IAK_ROOMS` | `thinkoff-development,feature-admin-planning,lattice-qcd` | Rooms to watch | | ||
| | `IAK_SELF_HANDLE` | `poller.handle` from config, else `@claudemm` | This agent's handle; its own posts are skipped **case-insensitively** ('@' optional). `IAK_SELF_HANDLES` (comma list) still accepted | | ||
| | `IAK_NEW_FILE` | `/tmp/iak-new-messages.txt` | Notification file this agent's poller and session hooks bind to. **Set a per-agent path on multi-agent machines** (e.g. `/tmp/iak-grok-new-messages.txt`): the room-responder lock derives from this file, so two agents sharing the default will fight over one voice and the loser's sessions go passive without warning | |
There was a problem hiding this comment.
When two agents use the generic poller, setting only IAK_NEW_FILE does not make the pollers coexist: scripts/room-poll.sh:15-22 still gives both processes /tmp/iak_poll.pid, so the second exits as an apparent duplicate. If that lock is separately overridden, the defaults for seen, acknowledged, and pending state are also shared (scripts/room-poll-check.py:65-67 and scripts/room-poll.sh:46), which can consume another agent's messages or nudges. This multi-agent guidance should also list the other paths that must be scoped per agent rather than implying that changing the notification file is sufficient.
Useful? React with 👍 / 👎.
1 participant
Documents the multi-agent-machine trap hit twice this weekend: the room-responder lock derives from the notification file, so agents sharing the default path fight over one voice. Env table now says to set a per-agent IAK_NEW_FILE.
🤖 Generated with Claude Code