Launched this week
Fox Issue Tracker 4
Track, plan, and release.
182 followers
Track, plan, and release.
182 followers
Fox helps you organize work that's outgrown todo apps and notes. Built for solo developers and small teams, it organizes everything around the versions you're shipping and the milestones that get you there—turning scattered tasks into a clear path to delivery and helping to ensure nothing is left behind.
Fox Issue Tracker 4
the 'nothing is left behind' promise is the hardest one to deliver on in issue tracking. most tools surface what's in the system but can't help with what you forgot to put in the system in the first place. curious whether Fox has any mechanism for catching things that should be in a release but aren't, like a checklist pattern or a release readiness check, or whether it's purely organizing what you've already decided to track
Fox Issue Tracker 4
@ansari_adin Hi Ansari! Fox's current features are designed to encourage thoughtful self-organization with tags, by segmenting unsorted issues and milestones into a visible space, and providing visibility into progression through status-driven updates (particularly on the Kanban board). Tags and a deep search also help to easily pick out what you need from projects with a lot of data.
But that's really relevant, too! I've been exploring more model-powered tools to help beyond self-organization, especially when putting together new milestones/releases and getting a higher-level overview of a workspace's content. You bringing this up only encourages me to invest more time into it. Thanks!
Congrats on the launch! The version/milestone-first framing is refreshing — most trackers treat releases as an afterthought bolted onto an endless backlog, and for solo devs "what ships in the next version" is really the only question that matters. Also love that it's self-contained and local-first in the Apple ecosystem. Curious: how do you handle quick capture when a bug or idea hits you away from the desk — is there a fast path to get it into Fox from iPhone without breaking flow?
Fox Issue Tracker 4
@simple_memo_captio_style Hi Yurika! The iOS app syncs all of the content across iCloud with the Mac app, so that's a strength for when ideas pop up or I happen across a bug that I need to log: I can open Fox on any device and drop off what's on my mind. The iOS companion is also more like a full fledged sibling as well and supports all of the same features, so I can do a bit more detailed entry when needed (like attaching screenshots in the moment). Personally, I like to add a status in my projects called "Review" and use it as catch-all category for Issues that I dump that need more work before starting or things may have been on the top of my mind before they get moved into the To Do group.
Good one today. Most trackers are a flat pile of tickets you slowly lose track of, so organizing the whole thing around versions and milestones is a genuinely different bet? An LLM reading my project is fine. An LLM closing issues and shoving milestones around is probably a write I'd want to see before it lands. Does the agent's action go straight through or is there a confirm step sitting between intent and your backlog?
Fox Issue Tracker 4
@artstavenka1 Hey Art! Thank you so much for your kind words :) To answer your question: it’s up to the user to decide how the LLM interacts with Fox since the MCP gateway offers interoperability, not necessarily direction. I specifically have instructed mine to only close issues after we’ve confirmed they’re complete and have added conclusive resolution details. The Kanban board also offers a high level look into a version release or milestone progression so you can see what issues have been moved, and even more if you want, you are able to customize statuses on the board to add a review step post LLM action for manual review before closing. A goal with Fox is to be structured but still flexible enough to respect each individual’s workflow.
The MCP integration caught my eye the most. We already use LLMs for code review and direction in our own workflow, so having a project workspace that an agent can actively write to feels like a natural next step. Curious how you're finding the write access in practice is it mostly status updates? or has it been useful for restructuring milestones mid-sprint?
For me, this is a very real problem -there are plenty of tasks, but no clear understanding of what will be finished and when!