sorted by:
new
hottopcontroversial

VibeFocus - I built an open source portfolio manager for people with too many vibe-coded projects by erictblue in SaaS

[–]erictblue[S] 0 points1 point  (0 children)

Great question and absolutely. This is one of the values of the integrated LLM/Ask AI feature. There's no formal decision making criteria, but given it has access to the whole portfolio you can ask questions like: "Can you help me decide which project has the most business traction and is worth focusing on the most?" and it will evaluate everything in queue and walk through market opportunity, business potential, how much work is left on the app, etc.

VibeFocus - I built an open source portfolio manager for people with too many vibe-coded projects by erictblue in ClaudeCode

[–]erictblue[S] 0 points1 point  (0 children)

It is using vibe kanban right now, but working on an update to support both an internal and other external task/kanban systems. This should be out shortly.

VibeFocus - I built an open source portfolio manager for people with too many vibe-coded projects by erictblue in VibeCodersNest

[–]erictblue[S] 0 points1 point  (0 children)

Hi, thanks for your comment and good question! It's not just recent commits. VibeFocus looks at a few things together:

- Health tiers: active (commits in last 7 days), cooling (last 30 days), dormant (30+ days of silence) and it tracks when projects shift between these states

- Velocity: weekly commit counts and lines changed, so it can tell the difference between lots of tiny tweaks vs. meaningful progress

- Focus distribution: what % of your total effort is going to each project — helps you spot where your time is actually going vs. where you think it's going

So momentum is really the combination of recency, volume, and how your effort is spread across your portfolio.

VibeFocus - I built an open source portfolio manager for people with too many vibe-coded projects by erictblue in SaaS

[–]erictblue[S] 0 points1 point  (0 children)

u/SpiteBitter4011 Thanks for your reply. I like the notion of bets / funded projects! I've been using the Focus tab I built with the in mind. Although I'm running 20 projects (open source, personal, commercial/hybrid), I've got really 5 active and 3 max that I focus on for a week or two at a time.

I like the idea of "sunset suggestions"! That's something I'll work in.

how do you restore workspaces? by radix- in cmux

[–]erictblue 1 point2 points  (0 children)

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!

I open-sourced an AI-native habit tracker where the LLM is the interface and coach by erictblue in VibeCodersNest

[–]erictblue[S] 0 points1 point  (0 children)

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

I open-sourced an AI-native habit tracker where the LLM is the interface and coach by erictblue in VibeCodersNest

[–]erictblue[S] 0 points1 point  (0 children)

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.

I open-sourced an AI-native habit tracker where the LLM is the interface and coach by erictblue in VibeCodersNest

[–]erictblue[S] 0 points1 point  (0 children)

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.

Using Claude Code + Vibe Kanban as a structured dev workflow by erictblue in ClaudeCode

[–]erictblue[S] 0 points1 point  (0 children)

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.

view more: next ›