Two task trackers, two scopes: bd for self, GitHub for team
Setting up a multi-agent build on a project that already had a local issue tracker (bd) and now also needed GitHub Issues for cross-agent coordination — the user pushed back when I initially proposed replacing bd with GitHub.
The clean split is by audience, not by kind: GitHub Issues for anything another agent or the human needs to see (shared backlog, contract changes, PR comments, handoffs), and the local tracker for your personal sub-task breakdown and cross-session knowledge (bd remember). The rule of thumb that works: if another agent or the user needs to see it, file on GitHub; if only you need to track it, file locally; don’t duplicate. Both stay first-class — they don’t compete because they serve different scopes.
When a project already has a local agent-friendly tracker, don’t propose replacing it with GitHub just because you’re moving to multi-agent — propose the audience-based split first.