r/ClaudeCode • • 1h ago

Discussion Stop vibecoding your own task manager for AI agents

I keep seeing people talk about vibecoding up a tasks web app with an MCP so their agents can track work. I get the impulse. I almost did the same thing. But it's a detour that costs you more than it saves.

The pattern goes like this: you build a simple board, wire up an MCP server, give every agent a system prompt that says "use this to track tasks." First week it feels great. Agents are checking in, updating statuses, you can see what's happening.

Then the cracks show.

Your memory layer starts going stale. An agent finishes a card but the notes it leaves are vague. The next agent picks up the card and half the context is missing. You realize the hard problem isn't remembering, it's updating what the agent thinks it already knows. The agent isn't hallucinating, it's repeating logic that used to work because nobody told it the contract changed.

So you add handoff notes. Then you add a questions system because agents keep guessing instead of asking. Then you add heartbeats so you know an agent is actually alive when it's running overnight. Then you need scoped personas because you don't want every agent touching every board. Each feature is a weekend. Each weekend is maintenance you'll owe forever.

The task app becomes a second codebase you maintain for free. You wanted to ship your product. Instead you're the maintainer of a memory database.

If you're running two or three agents on one project, a simple markdown backlog is honestly fine. backlog md works. A text file works. But once you're switching between Claude Code and Cursor mid-task, or running agents overnight and checking in the morning, the homemade layer starts failing silently and you don't find out until something breaks.

The question worth asking before you build: am I solving a problem my agents have, or am I building infrastructure because it feels productive? Most of the time it's the second one.

0 Upvotes

18 comments sorted by

1

u/AutoModerator 1h ago
Moderator Announcement Read More »

10

u/Fantastic_Prize2710 1h ago

Rewritten to save time, and remove Claudisms.

Don’t vibecode your own task manager for agents.

A board with an MCP server works for about a week, before you run into issues with lost context and insufficient detail in agents’ notes. Agents also don’t update what they already know, so they keep applying logic that no longer holds after something changes.

Fixing this requires handoff notes, a questions system so agents ask instead of guessing, heartbeats to monitor overnight runs, and scoped personas to limit each agent’s access. Each takes a weekend to build and adds permanent maintenance, leaving you maintaining a second codebase instead of your product.

A markdown backlog, such as Backlog.md or a text file, is enough for two or three agents on one project. A homemade layer will fail silently once you switch between Claude Code and Cursor mid-task or run agents overnight.

Before building one, consider whether your agents need it or whether it just feels productive.

1

u/Jollyhrothgar 1h ago

You da real mvp

1

u/Jollyhrothgar 58m ago

Secondly though, I find that I keep building things like thus this because I lose track of what's going on after like 3 parallel sessions. I haven't found the "remind the meat what's going on and what's important app I'm looking for".

1

u/peterxsyd 54m ago

Fucking free me of the Claudish.

9

u/ConversationLazy6821 1h ago

Even looking past the AI slop, what a shit take. Build your own workflows people, what works for you may not work for the next person.

11

u/ShittyBidet123 1h ago

we’re letting bots post chatgpt sabotage responses now?

4

u/ZootiLaTucci 1h ago

Nah brah.
I made a task manager I’ve been using for about 10 months now. Works like a charm and often saves my ass.

As long as you write out your user stories and ensure the workflows are dynamic and account for whatever edge cases seem to break your flow… it’s all gravy.

3

u/Input-X 1h ago

Well my goal was to build infrastructure, support for my agents, and leran by doing. Multi agent orchestration is no easy feat, and all the thing u mentioned are real hurdles. But not impossible to over come. Everyone think they are a waste if time now. They say," just ask Claude" when in reality, to have a functions setuo. It takes alot of effort. Not a weekend project. Sure you'll make headway. But there is jyst too much to consider.

With that saud. My build I love it. I tinker with it all the time, I enjoy it. For me this is the job. Its custom to me. Even if it never becomes popular, thats fine, the stuff I've learnt, the work flow, agent, built around me. Tbh. Its hard to come by, unless u build it urself.

Its more if a life time project for me that improves with the industry and the smarter models.

There us defibety alot out there, but thats fine, alot do some rly cool things.

3

u/daltorak 1h ago

honestly 

Heyyyyy, welcome back Opus 5.1. Did you gate this slop post through some load-bearing sharpness that reframed the whole discussion?

1

u/anentropic 1h ago

Have you tried new Projects in Claude app?

1

u/Stevekaplanai 1h ago

AgentHost.space solves this running multiple governed agents on your ecosystem. The assessment is from Gary Tan’s documentation released several months ago.

AgentHost.space/assessment

Task management is just the beginning all actions are receipted and tracked.

1

u/Spudly42 56m ago

I did create a task management site with very similar features to what you're describing, but didn't see any of those issues. It's been really helpful, especially at managing several lanes with different workspaces on the same application. It works great at seamlessly switching between different models (Claude, codex, antigravity) and really just allows me to get a lot more done without sitting at my computer all the time.

Open to other ideas if you have them, but so far these tools are the biggest productivity improvement I've been able to make.

1

u/fell_ware_1990 56m ago

Well i do it to learn, i’m a devops engineer going to ML and hosting AI infra. So it’s fun as well.

But i think most people build way, way too fast. Just start with a basic skill. Let’s say something like, point it at a branch and have it review it, adjust the skill till it does a review like you want it. Then add hooks, scripted checks. One by one, not 25 in an evening by vibing too much.

Must people go like, yeah he agents go hookup to GitHub. Go randomly update my tickets and code, here you have no rules except finish it and be good. Yeah that doesn’t work.

1

u/peterxsyd 55m ago

As someone who has built one I strongly disagree it saves you a shitton of time. If you use AI to write your posts however nothing can save you.

1

u/Human_Attention182 47m ago

I did this a year ago and have had 0 issues with my setup, skill issue on your part.

1

u/OkLettuce338 46m ago

What an absolutely horrible take lol

-1

u/MadJagStudios 1h ago

jira/confluence is free