Who it is forA self-hoster who finds a small annoyance in the planner and wants it fixed without writing code.
The problemSoftware you use changes only when its vendor releases, so small friction stays for weeks.
The outcomeA chat request becomes a triaged change that ships to the web app, phone or Mac with a summary of what changed.
What you need first
- A Mac or Mac mini where Claude Code runs, as the README describes
- A server you control to host the hub (FastAPI and SQLite), with HTTPS and a few tokens
- Access to the model provider you choose (the README says Anthropic today)
- Comfort with self-hosting, per docs/SETUP.md
Steps
- Open the chat in the web app or the phone app and describe the change, for example a font size or a layout tweak.
- Wait for the Claude Code session on your Mac to triage it and mark it as auto or ask.
- If it appears under Needs your decision, tap Approve.
- Open the app after the push that says what shipped and check the change.
Prompt for your agent
In the TimeLovercc/mojito repo, pick up open feedback from the hub, decide whether it is auto-ship or ask, and apply the change for <feedback-id> in the private copy. Expected output: a one-line plan, a passing typecheck and build, and a summary sent to the hub. Verify the change appears in the app after the build.
Caveat. Risky changes wait for your OK only because the maintainer follows the docs, since the README says the code does not enforce this yet.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page