Pinned Tweet
We just open sourced Nimbalyst.
AI makes it possible to do more work, but that means more to keep organized.
Sessions, prompts, file edits, tasks, and commits all start to blend together at speed.
I thought the tool should help with that and built Nimbalyst to keep everything connected.
Here are 6 examples:
We've been focusing nimbalyst on richer experiences. Agents and people working in rich visual editing experiences. Now collaborative as well.
Rich local editors, live editing with your coding agents... in your project's context. Share to your team for realtime collaboration. With a Canvas for bringing it all together. Docs, mockups, spreadsheets, datamodels, diagrams, calc sheets, mindmaps, and more. Nimbalyst.
Agents do the organizing, file the work, move it through planning, implementation and review, keep an eye on it with transcript peek w/ keyboard navigation.
All your agents report in from the menu bar. Track running, awaiting user input, and completed sessions as they transition state. Hover to see all key state and jump directly to a session. New in nimbalyst.
Anthropic says they're limiting programmatic use, but what they're actually doing is restraining the ecosystem of the builder experience. Is this really the time to push the innovation to other providers?
A list of the innovations that open-source Nimbalyst users will now have to experience with Codex instead of Claude when their tokens run out, because terminals and toy desktop apps are not enough.
- Interactive, WYSIWYG markdown and other extension-based editors with live visual diff showing agent work
- Rich transcript experience, include visual extension rendering like Excalidraw, mindmaps, ERD, mockups
- Proper searchable database history of sessions, prompts, files edited
- Interactive shortcuts like the history of every session that has edited this file
- Parallel sessions kanban, with transcript peek to keep tabs and organizational tags
- Mobile app with real rich transcript, push notifications, synchronized session prompt drafts
- Local orchestration, interactive voice agent control across sessions
And they still have Anthropic personnel claiming this only limits non-interactive tools, continuing the confusion.
Quickly viewing diffs let's you keep an eye on things without changing your entire visual context.
I want to scan a stack of AI edits in seconds, only digging in to the bigger changes.
That’s the direction we’re pushing on with Nimbalyst:
Link the session, the edits, the prompts, the tasks, and the commit so the whole workflow stays navigable.
Focus on organizing the work and supporting the user in managing the agents.
github.com/nimbalyst/nimbaly…
Commit by session, not by whatever happens to be dirty in git.
The agent can prepare the commit with the session context. You still validate and edit the files and message before anything lands.
In a world of software abundance, differentiation will come from taste and ergonomics.
The winners will not be the teams that add the most. They will be the teams that remove the most friction.
That takes product judgment. It means knowing your users deeply and, increasingly, letting them shape the product directly with AI instead of forcing them through fixed workflows. If users can shape the product directly, what happens to settings screens?
One of the weirdest things about current AI tooling: you often need extra tools just to know when the agent is done or blocked on you. There's value in running parallel agents in worktrees, doing exploratory implementations, but it can be hard to keep track of it all.
“Needs attention” should just be part of the workspace. System toasts should be useful and concise to help you keep track without losing focus.
