DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to host a private daily planner you own with Mojito

Run Mojito on your own server to get Today, plans, notes, feed and chat in one place.

Credentials. The hub stores your data and tokens on a server you run, so you must secure that server and its HTTPS setup yourself.

Who it is forA solo professional who wants a planner on machines they control and is willing to self-host.

The problemCloud planners keep your tasks and context on a vendor's servers and change only at their release schedule.

The outcomeA running hub with a Today page, two-week plans, notes, a feed and a chat, all on your own machines.

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

  1. Read docs/SETUP.md in the repo at https://github.com/TimeLovercc/mojito and list the server and tokens it asks for.
  2. Prepare a server or always-on computer for the hub, with HTTPS set up as the setup guide describes.
  3. Follow the setup guide to start the hub and the web app.
  4. Open the web app, check that Today, plans, notes, feed and chat load, and try one Undo on a data change.

Prompt for your agent

Using the TimeLovercc/mojito repo, follow docs/SETUP.md to deploy the hub on <target-server>. Report which steps succeeded and the URL of the running web app. Verify that the Today page loads and that the chat responds.

Caveat. The README calls Mojito experimental alpha with rough edges and breaking changes, so expect setup steps that assume you can run your own server.

Share: 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