Nimbalyst: organise coding agents around a visible project state

Open the workspace around one project

Thanks to Nimbalyst for sponsoring this video.

The 28 May 2026 description presents Nimbalyst as an open-source visual workspace and agent harness for Claude Code and Codex. It brings sessions, files, tasks, diffs, commits, terminals and diagrams together. The useful starting point is a known project: a single place to inspect the agent’s work instead of reconstructing it across separate apps.

1. Use https://nimbalyst.com for the product and https://github.com/nimbalyst/nimbalyst for the open-source repository.
2. Follow the original walkthrough with one intended project and inspect the session, file and task views before assigning new work.

Keep multiple sessions tied to explicit tasks

The walkthrough covers session imports and multiple models, and describes running several agents inside the same project with an automatic Kanban-style workflow. A shared project view helps track progress; the task still needs a clear owner and expected result.

Before another agent starts, check whether its task overlaps files already being changed. Resolve that overlap in the task brief and retain the current session context so a later review can explain who changed what.

1. Identify the imported session and its current task so older instructions are distinguishable from new work.
2. For parallel work, give each agent a bounded responsibility and compare task status with the files actually changed.

Review changes before committing

The description includes reviewing file changes and committing with AI. Use the diff as the evidence of what changed. A finished chat message or a moved task card is not a substitute for checking whether the implementation matches the intended job.

1. Read the diff and inspect any unexpected files before accepting the change.
2. Check the relevant application behaviour and review the proposed commit’s contents and description.

Use terminals and diagrams to explain the work

Nimbalyst can open terminals in the project folder and create live Excalidraw diagrams. Check the terminal’s directory before running a project command, and compare diagrams with the implementation they describe. The source says team collaboration is coming soon; that announcement is separate from the demonstrated multiple-agent workspace and is not evidence that team sharing was available.

The takeaway

A consolidated workspace is useful when sessions, tasks and diffs agree about what changed. Review the actual project, then preserve the checked result.