…it really feels like they’re attempting to reinvent a project tracker and starting off from scratch in thinking about it.

It feels like they’re a few versions behind what I’m doing, which is… odd.

Self-hosting a plane.io instance. Added a plane MCP tool to my codex. Added workflow instructions into Agents.md which cover standards, documentation, related work, labels, branch names, adding of comments before plan, after plan, at varying steps of implementation, summary before moving ticket to done. Creating new tickers and being able to relate to current or others, etc…

It ain’t that hard. Just do inception (high to mid level details) create epics and tasks. Add personas, details, notes, acceptance criteria and more. Can add comments yourself to update. Whatever.

Slice tickets thin and then go wild. Add tickets as your working though things. Make modifications.

Why so difficult?

This was my take.

They’ve made an issue tracker out of json files and a text file.

Why not hook an mcp to an actual issue tracker?

Did you mean plane.so instead of plane.io?