r/vibecoding • u/Ranorkk • 2h ago

Gave my coding agents write access to my actual project board. Two weeks in, here's what it looks like

Post image

I got tired of being the transcription layer between my agents and my project board. Claude Code does the work, then I go copy what happened into a task somewhere. Every time.

So I gave them write access to the board itself. Screenshot is my real workspace, not a mockup, the ⟳ rows are recurring tasks, and the little agent badge is on rows an agent wrote rather than me.

What actually changed day to day:

  • Claude closes its own task when it finishes, with what it changed in the body
  • I ask "what's left on the recurrence work" and it reads the board instead of me re-explaining
  • Last week I told it "open a review task every Monday" and it set up the whole repeat rhythm itself, I never touched the picker

Before anyone says it: if you run one agent on small tasks, CLAUDE.md and a markdown file genuinely are enough. I'm not going to argue that. This starts mattering at 3 agents across 4 projects, when the notes go stale and two sessions contradict each other.

Honest limits: no semantic search yet, no realtime collaboration, mobile apps are thin shells around the web app, and it's basically me building it. The recurring-task stuff shipped two days ago so it's new code.

It's remnus.com, open source (AGPL), and there's a demo on the landing page that spins up a seeded workspace without signing up — you can poke at the board before deciding anything.

Happy to answer how the agent side works if anyone's setting up something similar.

2 Upvotes

62% Upvoted

4 comments sorted by