A home for your tasks, your agents, and the story of what you’re building. Follow the small wins as this project takes shape.
A few things we made a little better. Come follow the next chapter.
Get this public journal online so people can follow the product while the private workspace keeps taking shape.
Move this product’s own tasks and agent handoffs into a dependable shared workspace, then use it to build the next release.
Tasks, project notes, agent handoffs, and a public journal are working in the local prototype. The next step is putting a small, dependable version online. The reason for building this is simple: recording more work should not force a small team to upgrade. The core has no artificial issue or seat limits, and ordinary task management needs no AI subscription.
The local workflow can now launch a configured runner when a task is assigned. It checks whether the work is ready, asks about missing decisions, and wakes again when a person answers. A sample runner and a real MCP client have exercised the flow. Connecting an actual coding agent and running it on the hosted service comes next. Finished work still comes back to a person for review.
The public journal is a separate, curated view of the build. It shows approved wins and what’s coming next, without copying the internal board or agent conversations. There is also a working preview of scheduled X updates: review the exact words, approve the time, and let the schedule take over. Real X account connection is still ahead.
