What happened
Krea announced Multiplayer Nodes on October 22, 2026. Nodes is a graph-based editor in which image, video, and text nodes connect so one node’s output can feed the next. The new feature lets several people open the same project and build or run that graph at once. Krea presents this as a replacement for a handoff cycle in which someone shares a link, waits for feedback, and then makes changes alone.
Changes to node positions, connections, prompts, model selections, and sticky notes sync to collaborators. Each person has a color; teammates can see their cursors, selected nodes, and selection boxes. Runs are shared too: collaborators see a node or chain move from queued to running to done, and finished outputs appear on their screens. Undo and redo are personal, so one person’s undo does not reverse another’s edits. Changes to different fields can proceed concurrently; if two people edit the same field, the last edit wins.
Sharing has three general levels: Private, Workspace, and Public link, with separate view or edit grants for invited workspace members. Workspace editors can edit and run nodes and see outputs and history. A public-link viewer can inspect the graph’s structure and duplicate it, but cannot run it or see generated outputs or run history. If a person has both an individual grant and access through a workspace share, the higher permission applies. Krea says view sharing—including workspace view, person view, and public links—is available on every plan. Edit sharing and live presence, which enable co-editing and shared runs, require Krea Enterprise. If a workspace leaves Enterprise, edit grants become view grants and return if the workspace regains Enterprise.
The person who starts a run pays for it in their active workspace. When someone starts a chain, their tab submits each next step; the chain continues if they switch tabs, while collaborators watch results arrive. Nodes keeps project snapshots at most once every five minutes for five days, and users can preview and restore an earlier version. Krea also says its Agent and MCP clients edit Nodes projects through the same operations as people, with their changes syncing to the shared canvas.
What the archive adds
The supplied archive contains no earlier Field Note that is genuinely about Krea Nodes or its live collaboration model. The listed notes on inference compilation, a Gemini avatar, and GitHub agent workflows share broader AI or workflow terms, but do not establish prior coverage of this event. This is a new event in the supplied archive.
Trend signal
This is a modest fit for agent-ready software exposes capabilities: Krea says its Agent and MCP clients use the same project operations as human collaborators. That gives external agents a defined surface for editing a workflow. The announcement does not detail the permissions, safeguards, or capabilities exposed to those clients, so it offers only limited evidence for the pattern.
Why now
Krea’s announcement frames the change around the friction of sharing a workflow for feedback and then applying changes separately. The new shared canvas makes collaboration part of the editing and execution process. The source gives no further explanation for the timing of the launch.
Connections to other events
The archive’s October 2026 note on GitHub Agentic Workflows describes a project moving from experimental status to general availability with additional safeguards. Krea’s announcement is distinct: it adds live collaboration to a visual workflow editor rather than releasing a coding-oriented agent workflow project. Both make workflow operation more explicit, but the source does not claim a connection between them.
Why it matters
For teams building generative-media pipelines, shared editing changes how creative direction, implementation, and review can happen. An art director can change a prompt while a designer adjusts a separate scene, and the team can see runs and outputs together rather than coordinating through screenshots or exchanged project files. Personal undo reduces one collaboration hazard, while version snapshots offer a limited recovery path.
The commercial boundary matters: a team can share a view on any plan, but real-time editing, live presence, and shared runs require Enterprise. That makes it possible to distribute reusable workflow templates broadly without giving every recipient editing or execution access, but it also means teams need to evaluate Enterprise access before treating Nodes as a shared production environment. Since runs are billed to the person who starts them, teams should also account for who initiates jobs in a shared project.
Limits and uncertainty
The announcement does not state Enterprise pricing, participant limits, or performance limits for large graphs or simultaneous users. It does not specify how conflicts beyond the same-field last-edit-wins rule are handled, or whether the five-day snapshot window can be configured. The source describes Krea Agent and MCP client editing but does not explain their authorization model, audit controls, or exact supported operations. It also provides no measurements of time saved or evidence about how teams use the feature in production.
Skill to build now
If your team uses Nodes, map one existing workflow into a collaboration test: assign separate nodes or fields to two editors, run a short chain, and verify who pays, what viewers can see, and whether personal undo behaves as expected. If you share a template publicly, check that the graph contains no inputs or context you do not intend to expose; Krea says public viewers can see the workflow structure and duplicate it.
Reader takeaway
Krea Nodes now supports a shared, live workflow canvas, including runs and edits by Krea’s Agent and MCP clients. But the collaboration feature that changes team operations is Enterprise-only, and job costs remain attached to the person who starts a run. Treat it as a new workflow surface with explicit access and billing rules, not simply a more convenient share link.