Nimbalyst Visual Coding Workspace
A desktop workspace for running Codex and Claude Code sessions in parallel while reviewing file changes visually.
- Source repo
- nimbalyst/nimbalyst
- Stars
- ★ 1.8k
- Last updated
- 1d ago
- License
- MIT
- Primary language
- TypeScript
- FA score
- 50/100 · Major gaps
At a glance
- Works with
- Portable with changesCodex · Claude Code
- You'll need
- Typical use
- A developer progressing several Codex or Claude Code tasks at once can use parallel sessions, search/resume, and the Kanban board to keep them coordinated.
- Main limitation
- OpenCode and Copilot are documented as alpha, so those integrations may be incomplete or less stable.
- Source review
- 50/100 · Major gaps
What does this agent do, and when should you use it?
Nimbalyst is a local, open-source visual editor, session manager, and task manager for developers, product managers, designers, and builders. Its monorepo includes an Electron desktop app, a SwiftUI iOS app, cross-platform runtime services, collaboration-protocol types, an extension SDK, and built-in extensions. It supports Codex and Claude Code, with OpenCode and Copilot identified as alpha, and connects parallel sessions with files and task boards. Built-in editors cover Markdown, mockups, Mermaid, Excalidraw, CSV, data models, and Monaco-based code editing, with red/green visual review of coding-agent changes. Content and status can live in Markdown, ordinary files on disk, or Git; the collaboration sync server is a separate project.
Users create or open documents, edit them in a WYSIWYG Markdown editor, and use supported coding agents across their files. The app links sessions to files and files to sessions, groups files touched by a session, runs sessions in parallel, and provides search, resume, and Kanban management. When an agent suggests edits, the user reviews red/green WYSIWYG diffs, accepts or rejects changes, and can edit or annotate the material directly. Its task features let agents and humans add, move, and execute plans, bugs, features, and todos; developer features include Git-state management, AI git commit, an embedded Ghostty terminal, and worktrees. Custom editors plug in through the EditorHost contract; named built-in extensions include an Astro website editor, visual Git log, mindmap, slides, and a 3D object editor.
- A developer progressing several Codex or Claude Code tasks at once can use parallel sessions, search/resume, and the Kanban board to keep them coordinated.
- A technical lead reviewing agent-generated changes can inspect red/green diffs in Markdown, code, or visual-file workflows before accepting each edit.
- A product team working across specifications, mockups, diagrams, CSV files, and code can collaborate with coding agents in the corresponding built-in editors.
- An engineer using isolated Git worktrees can combine Git state, AI git commit, and the embedded Ghostty terminal in one workspace.
- Someone away from their desktop can use the mobile app to see active sessions, answer agent questions, review diffs, and queue follow-up tasks.
How do you install or deploy this agent?
Download the listed installer for macOS Apple Silicon, macOS Intel, Windows, or Linux. The documented minimum requirements are macOS 12+, Windows 10+, and Linux. To run from source, npm 7+ is required:
npm install
cd packages/electron && npm run devThe supplied documentation does not specify credential setup, authorization, or first-connection steps for Codex, Claude Code, OpenCode, or Copilot.
How do you use this agent?
Start by clicking New or pressing Cmd/Ctrl+N, then write or edit in the WYSIWYG Markdown editor. Switch to Agent Manager to run parallel sessions, link them with files, and manage progress through search or the Kanban board. Review each agent change through the red/green diff interface, accepting or rejecting it as appropriate; use the task view for plans, bugs, and todos. For source development, cd packages/electron && npm run dev starts the Electron app in development mode.
What are this agent's strengths and limitations?
- Combines sessions, files, tasks, and Git-oriented workstreams in one desktop application, including bidirectional session-file links.
- Provides visual collaboration surfaces for Markdown, mockups, Mermaid, Excalidraw, CSV, data models, and Monaco code.
- Lets users approve or reject coding-agent edits through red/green WYSIWYG diffs instead of relying only on terminal output.
- Uses a common
EditorHostcontract for built-in and custom editors, with several named extension types already included. - Offers listed desktop downloads for macOS, Windows, and Linux, alongside an iOS mobile-app workspace.
- OpenCode and Copilot are documented as alpha, so those integrations may be incomplete or less stable.
- The collaboration sync server is outside this repository; this codebase supplies the client and wire-format types in
packages/collab-protocol. - Source use requires npm 7+ plus dependency installation and Electron-monorepo development setup.
- The supplied documentation does not explain how to authorize or configure any supported coding-agent provider.
- Anonymous PostHog analytics are enabled by default for fresh installs, although users can opt out in Settings → Advanced → Analytics.
How does this agent compare with similar options?
Nimbalyst is positioned as a visual collaboration and session-management layer for Codex, Claude Code, OpenCode (alpha), and Copilot (alpha), rather than as a replacement for those coding agents. Compared with working directly in those agents' terminal sessions, it adds file linking, Kanban management, task tracking, visual editors, and diff approval.
Key facts side by side with the most closely related agents.
| Agent | Source review | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|
| Nimbalyst Visual Coding Workspace This agent | 50 · Major gaps | ★ 1.8k | 1d ago | TypeScript | Codex · Claude Code |
| Tessera | 74 · Some gaps | ★ 309 | 8d ago | TypeScript | Codex · Claude Code |
| Ateam Agent Workbench | 70 · Some gaps | ★ 12 | 8d ago | TypeScript | Codex · Claude Code |
| Superagent | 58 · Major gaps | ★ 26 | 1d ago | TypeScript | Codex · Claude Code |
How does FollowAgents rate this agent?
Why each dimension lost points
Evidence shows: README explicitly states telemetry is anonymized, no PII, file contents, or API keys collected, with opt-out; SECURITY.md provides vulnerability reporting process; CI workflows use secrets but decode only when needed, with checks for signed builds. However, least privilege details are lacking, user confirmation (e.g., AI change approval) is mentioned but not detailed, data flow transparency has docs (POSTHOG_EVENTS.md) but full event list not provided, sensitive data handling (e.g., API keys) not specified, dependency security has overrides and allowScripts but no vulnerability scanning evidence, external effects (e.g., auto-updates) lack rollback mechanism, source attribution (e.g., DCO) mentioned in CONTRIBUTING.md but not detailed. Deductions made.
Evidence shows: CI workflow (ci.yml) runs unit tests and type checks, multiple test scripts (test:unit, test:prepush), but no test results or coverage provided; dependencies locked in package-lock.json (not provided), but CI uses npm ci for reproducible installs; failure messages: CI has explicit error checks (e.g., verifying APK signature), but in-app error handling not evident in provided files. Deductions made.
Evidence shows: README clearly identifies target users (developers, product managers, designers) and use cases (running multiple coding agents in parallel, visual editing), supports multiple platforms (macOS, Windows, Linux, iOS, Android), has extension system. But capability boundaries (e.g., supported agent types) not detailed, trigger precision (e.g., AI commands) not provided, environment fit (e.g., Node version requirements) in package.json engines field, but no detailed configuration guide. Deductions made.
Evidence shows: README well-structured with sections for features, download, getting started, building, community, license; install notes provide download links and build steps; naming stability: package name and version in package.json, but no naming conventions; examples (getting started steps) and FAQ (not provided); known limitations not explicitly listed; license is MIT with LICENSE file; versioning has package.json version, but no CHANGELOG; maintenance responsibility mentioned in CONTRIBUTING.md, but no maintainer info. Deductions made.
Evidence shows: Output usability: README describes visual editors, session management, task tracking, but no actual output examples; marginal value: project offers unique features (visual collaboration, multi-agent management), but no comparison with existing tools; cost-benefit: free and open-source, but no performance or resource consumption data. Deductions made.
Evidence shows: README feature claims lack specific implementation details or test evidence; cross-source verification: CI and test scripts exist, but no test results; fact-inference separation: README claims are descriptive, not distinguishing facts from inferences. Deductions made.
- Telemetry claims anonymity but full event list not provided; review POSTHOG_EVENTS.md to confirm no sensitive data.
- Dependency security relies on overrides and allowScripts without vulnerability scanning evidence; check dependencies for vulnerabilities.
- Auto-update mechanism lacks rollback options; failed updates may impact usage.
- No CHANGELOG provided; version changes are not transparent.
FAQ
Is Nimbalyst paid software, and what license applies?
Which coding agents are supported?
Is the collaboration backend included in this repository?
wss://sync.nimbalyst.com, but the Cloudflare Worker that powers that sync service is a separate project.