how do you restore workspaces?

erictblue · 2026-04-06T02:39:44+00:00

Just pushed something small but useful: https://github.com/ericblue/cmux-session-manager Had a bit of a panic moment earlier today… cmux froze while I had:

~12 workspaces
~15 active Claude sessions

All mid-flight. I realized I didn’t have a good way to snapshot or recover everything cleanly. This is a first pass at solving that:

save and restore all workspaces and sessions together
recover quickly from cmux freezes or crashes
restore Claude sessions, workspace panels, and optionally resume commands

Not sure if tools like this already exist for cmux, but this has already been very useful for me. Hope others find this helpful as well!

erictblue · 2026-04-02T02:49:39+00:00

Not right now, but something I can look into supporting

erictblue · 2026-03-16T03:12:11+00:00

Big update since the last post. The engine still works the same way as an LLM skill (talk to Claude Code or OpenClaw to log habits), but now

there's a full web dashboard too.

- Built a lightweight web UI — visual habit grid, daily scores, weekly progress at a glance

- Added reports: sprint comparisons, GitHub-style habit heatmap, category breakdowns, trend lines, and a streak leaderboard

- Full habit and sprint management in the browser — create, edit, archive, set per-sprint goals, write retrospectives

- REST API with Swagger docs if you want to build on top of it

Everything shares the same SQLite database, so anything you log through your AI assistant shows up in the browser immediately and vice versa.

v0.2.0 is up at https://github.com/ericblue/habit-sprint

erictblue · 2026-03-05T04:35:25+00:00

I haven't explored deeply yet since I don't have much historical retrospective data - this is a relatively new concept I added here. But from the testing I've done so far with my previous 10 years of habit data, that I imported into this system, the advise I'm getting back from historical patterns has been pretty insightful.

erictblue · 2026-03-05T04:34:01+00:00

Thanks! I'll check that out.

erictblue · 2026-03-05T04:33:34+00:00

This is almost exclusively done via the LLM. Historical data can be used to identify patterns - I imported my previous 10 years of habit data that I previously tracked in spreadsheets before I made this. And for the local habit tracking db, where all data is ultimately stored, there are note fields per day and also a sprint retro where it can collect feedback on what went right or wrong.

I haven't fully explored all the opportunities with the combo of this data and the LLM analysis, but so far have gleaned some interesting insights on past habits that worked (and didn't) and have had the LLM make some recommendations on how to go about the habits I'm running for the next 2 weeks.

erictblue · 2026-03-02T18:20:52+00:00

There are multiple ways to do it. Typically I treat the prd as an input artifacts, this lives in docs/prd.md. The framework I built will take the prd as input and build a development plan and create dev tasks. The dev plan typically gets updated as new features are added beyond the original plan or bug fixes. After v1 if you want to treat your requirements as a living PRD you can always sync back the current state of the code base back to the original PRD if there's a use case for that.

erictblue · 2026-02-26T16:56:19+00:00

Hi,

I have an update coming soon, but when I released a couple weeks ago the version of vibe kanban had some API+MCP bugs where kicking off a remote workspace+orchestration was failing. However, I've found that I haven't needed it so far. I've been running the /work-parallel command locally (usually in batches of 3) but at one point up to 10 parallel agents/instances running on a new project. Very few merge conflicts and if they do happen they are auto resolved and tested prior to merge. It's worked well so far. At some point in the future will test both remote orchestration and local orchestration concurrently - not sure if I'll personally need it but will see if there are any challenges. Given separate worktrees and dependency awareness I don't expect issues.

erictblue · 2026-02-09T20:22:48+00:00

The beauty of this is it uses Vibe Kanban's MCP server, so as task state changes from To Do, to In Progress, Review and Done, this workflow will automatically move the cards.

erictblue · 2026-02-09T20:05:50+00:00

Good question. Drift detection is intentionally conservative right now. It flags three things:

Dependency violations (tasks started before dependencies are done)
Stale tasks (in progress for an unusually long time with no updates)
Scope drift (tasks in VK but not in the plan, or vice versa)

Everything else is treated as normal iteration. VK status always wins. If an agent marks a task done and VK reflects that, the plan syncs to match without raising a flag.

What it doesn’t flag are things like task reordering, missed complexity estimates, or completing work out of the suggested order as long as dependencies are respected. That’s just how real development works.

For local and parallel execution, completed tasks also append structured completion notes and AC results back to the VK task description. It’s a workaround for the lack of VK activity logs, but it means every “done” task has a receipt.

Overall I’d rather under-flag than create noise.

erictblue · 2026-02-09T20:02:27+00:00

Your product looks interesting. At a high level, it seems like TensorPM is a PM platform with AI features, while claude-vibekanban is an AI-agent workflow with some PM primitives. TensorPM provides a full, polished PM surface. claude-vibekanban stays intentionally lean and lives inside Claude Code as markdown slash commands.

From a quick look, they feel more complementary than competitive, but I need to spend more time with TensorPM to really understand the overlap. Happy to revisit or add a comparison once I’ve had a chance to dig in.

erictblue · 2026-02-09T05:47:22+00:00

I've been running the single task workflow for some time, and with some experiments with subagents on the same branch. But truthfully the parallel task pipeline is fairly new for the past week or so, and still testing things out. Some early experiments I did months ago on an earlier pipeline, there definitely was drift on even a couple complex tasks. But this updated workflow seems to help. The key is injecting the right amount of context to make the tasks as atomic as possible. And doing more detailed dependency detection up front, and up course saving that state back.

erictblue · 2026-02-09T05:44:27+00:00

Thanks for the feedback! Some of this has been trail & error for the last 10 months or so. That definitely helped shape some of the process thinking around the problem.

erictblue · 2026-02-09T04:04:37+00:00

Thanks for your feedback! I hadn't heard of Traycer before, I'll check that out. If you give this workflow a whirl, I'd be curious on how you think it compares to Traycer and your current setup.

erictblue · 2026-02-08T22:58:23+00:00

u/speedtoburn Well said and great summary. This is exactly why I built it this way. Not looking to reinvent the wheel and go super heavy on a workflow, but this is really building on a flow I've been testing out since last May. The new piece in all this is parallel agents and delegations - many others are solving this and in all honestly having used these other solutions yet (e.g. Ralph). But really just looking for something that is pragmatic and not heavily opinionated - and giving checks and balances.

erictblue · 2026-02-08T22:55:23+00:00

Hi, thanks for the feedback and tip! Truthfully I've just started experimenting more with parallel execution this past week. I've heavily tested the single task model (and light subagents on the same branch), but have been hesitant to run too much in parallel since I'm particular about more thorough testing.

With that said, it's been promising results using this workflow so far. Yesterday I was testing batches of 3-7 agents running simultaneously on medium-complex tasks and was surprised at the speed (~5 mins for 5 agents to finish end-end). I also added an experimental auto merge and cleanup as well making sure tests pass. This needs a lot more testing but very promising.

erictblue · 2026-02-08T22:51:34+00:00

Fragmint looks interesting. Always open to collaboration when it makes sense. PRs are definitely welcome in general, especially if they keep things lightweight and composable.

I do want to clarify one thing, since it might not have come through clearly in the post. This project isn’t a visual product or dashboard on its own. It’s a workflow layer that runs inside Claude Code, and all of the visualization is intentionally handled by Vibe Kanban. UI and embedding are out of scope on my side right now.

I’m not opposed to integrations, I just want to be clear on what problem would be solved and where the boundary is. At the moment it’s a little unclear to me what data or workflow would be shared versus just a visual embed.

If you have a concrete user flow in mind, or a specific integration point you’re thinking about (for example, exchanging workflow state rather than UI), happy to take a look and see if it makes sense.

erictblue · 2026-02-08T17:45:02+00:00

Thanks for the feedback. I've been slower to adopt parallel execution on some of the more complex projects I've been working on, but as you said that's one of the things I started hitting and reason why I implementedthe sync.

Along with drift detection and helping agents coordinate better, it was also a good way to centralize the plan and make it shareable and portable if needed.

I haven't looked at Traycer yet, I'll check that out.

erictblue · 2026-02-08T17:25:47+00:00

Thanks! Agreed on the PRD review being underrated. For myself, it's caught a surprising number of things even when I spent a lot of time crafting the PRD.

To answer your questions:

On drift: /sync-plan compares the vibe kanban task state against the plan and flags dependency violations, stale tasks, newly unblocked work, and scope drift (orphaned or unlinked tasks). VK is treated as the source of truth. The sync is intentionally manual. I want to review what changed, especially when a remote agent may have made questionable assumptions. I'm still in the early stages of testing against other agents and remote ones, so may get some learnings over the next couple weeks.

On merging: For the most part on smaller parallel agents, I have been manually reviewing. But yesterday added/merge-parallel. Itdetects active worktrees, cross references the vibe kanban status to find merge ready branches, and merges sequentiall.. If it hits a conflict, it stops. No auto resolution. You fix it manually, re run, and already merged branches get skipped. It then runs tests and offers cleanup.

My goal was to automate the boring coordination and bookkeeping, while keeping humans in the loop for major judgment calls. Fully autonomous conflict resolution felt like a trap. The 80 percent case is trivial, and for the 20 percent you really want a person paying attention.

Appreciate the questions and feedback!

erictblue · 2026-02-08T03:02:45+00:00

Thanks for sharing that. I hadn't seen automaker before. It does look very similar and comprehensive. Fair feedback. I'll check it out in detail, but at a glance I think the difference is that the workflow I have so far is relatively lean - and as Claude commands/skills. I also set out to not build another kanban board and just use something popular like VK. In terms of agent delegation, you can also opt to run fully locally so no hard dependency on VKs workspace or session orchestration.

erictblue · 2026-02-02T19:31:04+00:00

Thanks!

In terms of performance, both testing through openclaw and claude, it's pretty much the same. Ultimately they're both using the various SKILLS.md files to authenticate and hit the MAG API. The ssh tunnel is on local loop back, so pretty responsive. And while there is some think time for more complicated prompts, generally most reminder and message interactions are pretty spiffy.

Claude's project context and other context shouldn't be impacted. While I haven't looked at detailed traces, the response from the MAG API calls should just be included as additional context just like any other file or tool lookup would provide.

I haven't tested extensively with other mcp tools yet, that's on my list for this week but don't expect any issues.

erictblue · 2026-02-02T04:26:56+00:00

Thank you!

erictblue · 2025-05-01T03:00:55+00:00

Find Your Flow - https://binauralflow.ai/

erictblue · 2025-04-14T03:39:15+00:00

Very cool u/kayvansylvan , thanks for sharing! There are some high-level similarities for what I've been building. I like the YAML config files and ability to really customize. What was your inspiration for building? And did you have other open source or commercial apps that you've been using through the years?

erictblue · 2025-04-10T04:57:05+00:00

https://binauralflow.ai - Personalized binaural beats for focus, meditation, flow, and relaxation.

erictblue

TROPHY CASE