I enjoy reading books, learning new things, and building useful software. Lately, I’ve been working on text-chipper, an open-source text chunker for RAG and LLM projects.
Creator of GithubStarsManager — an open-source, local-first tool that organizes GitHub stars with AI: auto-categorization, semantic search, release tracking, and an MCP server for star library.
The worktree grouping is the detail that sold me — a clean main checkout sitting next to a linked worktree with unfinished edits is exactly where I lose track. Do you find the 'With changes' filter or the pinned section does more of the daily work for you?
I build SaaS products and VS Code extensions. I write about GitHub, Copilot, and the workflows I use to ship software. Microsoft MVP (12x) · GitHub Star (4x).
Creator of GithubStarsManager — an open-source, local-first tool that organizes GitHub stars with AI: auto-categorization, semantic search, release tracking, and an MCP server for star library.
Thanks for answering! That makes total sense — agents leave uncommitted edits behind all the time, so "with changes" is the most direct place to look when you're wondering what the agent actually touched. Pinned feels more like the long-term anchor for the repos you keep coming back to. The split between the two is clear now.
I build SaaS products and VS Code extensions. I write about GitHub, Copilot, and the workflows I use to ship software. Microsoft MVP (12x) · GitHub Star (4x).
Creator of GithubStarsManager — an open-source, local-first tool that organizes GitHub stars with AI: auto-categorization, semantic search, release tracking, and an MCP server for star library.
Makes total sense — the daily-driver repos earn the pin. Do you find the set stays pretty stable, or does it rotate a lot as projects come and go? I keep ending up re-pinning whenever I switch focus, which is half the reason I started thinking about better ways to organize starred repos.
I build SaaS products and VS Code extensions. I write about GitHub, Copilot, and the workflows I use to ship software. Microsoft MVP (12x) · GitHub Star (4x).
I build SaaS products and VS Code extensions. I write about GitHub, Copilot, and the workflows I use to ship software. Microsoft MVP (12x) · GitHub Star (4x).
What I check first is exactly what this answers: uncommitted changes, then unpushed commits, then whether an agent left a worktree behind. I switch between projects a lot building Homeowner HQ for realtors and lenders, launching December 4 on Amazon AWS, and the worst way to start a morning is opening a repo and finding out later that yesterday's work was never pushed — or that an agent's worktree has edits I forgot about. Seeing ahead/behind counts before opening the folder is the part I would use every day. The pinned repos and the quick switcher are a bonus. Installing it today.
I build SaaS products and VS Code extensions. I write about GitHub, Copilot, and the workflows I use to ship software. Microsoft MVP (12x) · GitHub Star (4x).
I build SaaS products and VS Code extensions. I write about GitHub, Copilot, and the workflows I use to ship software. Microsoft MVP (12x) · GitHub Star (4x).
I’m Anshika. Just a curious coder trying to learn, experiment, and grow at my own pace. I like building little projects, exploring new tools, and figuring things out as I go. Not in a rush, just alive
I build SaaS products and VS Code extensions. I write about GitHub, Copilot, and the workflows I use to ship software. Microsoft MVP (12x) · GitHub Star (4x).
That sounds good
Awesome!
The worktree grouping is the detail that sold me — a clean main checkout sitting next to a linked worktree with unfinished edits is exactly where I lose track. Do you find the 'With changes' filter or the pinned section does more of the daily work for you?
Yes, I am using a lot "with changes", especially when I use agents from Claude or GitHub Copilot and sometimes they don't commit the files.
Thanks for answering! That makes total sense — agents leave uncommitted edits behind all the time, so "with changes" is the most direct place to look when you're wondering what the agent actually touched. Pinned feels more like the long-term anchor for the repos you keep coming back to. The split between the two is clear now.
yes, I pinned my top repos that I use more or less every day.
Makes total sense — the daily-driver repos earn the pin. Do you find the set stays pretty stable, or does it rotate a lot as projects come and go? I keep ending up re-pinning whenever I switch focus, which is half the reason I started thinking about better ways to organize starred repos.
I switched the pinned more or less every two weeks.
Wow, how cool is that!!!
Thanks! Of course it's opensource, so if you want to collaborate or just add issues or whatever, you are more than welcome :)
What I check first is exactly what this answers: uncommitted changes, then unpushed commits, then whether an agent left a worktree behind. I switch between projects a lot building Homeowner HQ for realtors and lenders, launching December 4 on Amazon AWS, and the worst way to start a morning is opening a repo and finding out later that yesterday's work was never pushed — or that an agent's worktree has edits I forgot about. Seeing ahead/behind counts before opening the folder is the part I would use every day. The pinned repos and the quick switcher are a bonus. Installing it today.
I also created the standalone version of the extension: github.com/kasuken/repoboard
I think seeing git status before opening a repo would save me a lot of guessing.
this is why I created this extension!
I am also creating a stand alone application.
This is a life saver
Thank you very much.
If you have any feedback, please share with me or use the issues on the repo. 🙂