Node-based terminal manager for AI coding agents — tmux-backed terminals and parallel agent sessions as draggable nodes on an infinite pan/zoom canvas. macOS, Linux, and a browser Server Edition.
TypeScript adhdagent-orchestrationai-agentscanvasclaude-codecodexcoding-agentsdeveloper-toolselectrongeminilinuxmacosmultiplexeropencodeparallel-agentsterminalterminal-emulatorterminal-multiplexertmuxworkspace-manager
docs: say where nodeWritesFor lives in the node-action note
Mina Sameh0df8780ac5fa
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdindex c15dde7c5..01728f76d 100644--- a/CONTRIBUTING.md+++ b/CONTRIBUTING.md@@ -144,8 +144,8 @@ menu, the sessions-sidebar row menu and both kanban card menus (through`components/kanban/cardMenu.tsx`) build from it. Decide in the same change whether a card offersthe new row: a card takes only `BOARD_NODE_ACTION_IDS`, and a row that acts on canvas position goesin `BOARD_SPATIAL_ROW_IDS` instead. Remember the board acts on nodes of projects that are NOT on the-canvas (the Omni board): write through `nodeWritesFor(projectId)` (`lib/nodeWriteRouter.ts`), never-a live-canvas callback, and report a failure with a `nodeterm:toast`.+canvas (the Omni board): write through Canvas's `nodeWritesFor(projectId)` (built on+`createNodeWriteRouter`, `lib/nodeWriteRouter.ts`), never a live-canvas callback, and report a failure with a `nodeterm:toast`.`lib/nodeActionItems.guard.test.ts` fails on a second copy of the rows.A board card's **source** is a registry entry, not a branch you add at a call site