# AI use cases for Mojito (TimeLovercc/mojito)

Repo: [TimeLovercc/mojito](https://github.com/TimeLovercc/mojito) | Use cases: 4 | Page: https://dedupedai.com/use-cases/timelovercc-mojito/

Mojito is a self-hosted, TypeScript personal app where a Claude Code agent on your own Mac rewrites the app's code from chat requests and ships the update to your web app, phone, Mac, and server.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Host a private daily planner you own: https://dedupedai.com/use-cases/timelovercc-mojito/self-host-daily-planner/
- Ask for an app change in chat and get it shipped: https://dedupedai.com/use-cases/timelovercc-mojito/ship-app-change-from-chat/
- Get a daily card of the mail worth reading: https://dedupedai.com/use-cases/timelovercc-mojito/daily-gmail-worth-reading-card/
- Skip one Google Calendar event with Undo: https://dedupedai.com/use-cases/timelovercc-mojito/skip-one-calendar-occurrence/

## How to host a private daily planner you own with Mojito

Repo: [TimeLovercc/mojito](https://github.com/TimeLovercc/mojito) | Difficulty: Advanced | Time: half a day | Basis: From the README

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

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

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

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

### 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 to paste into your agent

```text
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.

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

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/timelovercc-mojito/self-host-daily-planner/

## How to ask for an app change in chat and get it shipped with Mojito

Repo: [TimeLovercc/mojito](https://github.com/TimeLovercc/mojito) | Difficulty: Advanced | Time: half a day | Basis: From the README

Describe a small fix or feature in chat and let the Claude Code loop ship it to your devices.

**Who it is for:** A self-hoster who finds a small annoyance in the planner and wants it fixed without writing code.

**The problem:** Software you use changes only when its vendor releases, so small friction stays for weeks.

**The outcome:** A chat request becomes a triaged change that ships to the web app, phone or Mac with a summary of what changed.

### Steps

1. Open the chat in the web app or the phone app and describe the change, for example a font size or a layout tweak.
2. Wait for the Claude Code session on your Mac to triage it and mark it as auto or ask.
3. If it appears under Needs your decision, tap Approve.
4. Open the app after the push that says what shipped and check the change.

### Prompt to paste into your agent

```text
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.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/timelovercc-mojito/ship-app-change-from-chat/

## How to get a daily card of the mail worth reading with Mojito

Repo: [TimeLovercc/mojito](https://github.com/TimeLovercc/mojito) | Difficulty: Advanced | Time: 1 hour | Basis: From the README

Turn your Gmail inbox into one read-only card in your feed every morning.

**Who it is for:** A busy person who wants the important email surfaced in the feed without opening the inbox.

**The problem:** Scanning a full inbox each morning takes time, and important messages get buried.

**The outcome:** A daily feed card that lists the mail worth reading, built from a read-only Gmail connection.

### Steps

1. Connect your Gmail account to your self-hosted Mojito instance as the setup guide describes.
2. Confirm that the connection is read-only before you enable the card.
3. Ask in chat for a daily mail-worth-reading card in your feed.
4. Check the next morning's feed for the card and open one item to confirm it matches your inbox.

### Prompt to paste into your agent

```text
In the TimeLovercc/mojito repo, enable the daily 'mail worth reading' feed card using a read-only Gmail connection on <hub-url>. Expected output: one feed card for the day with a short list of messages. Verify that no message was sent, archived or deleted.
```

### Caveat

The README says the mail card ships in the repo and is read-only, but the exact Gmail setup steps are in docs/SETUP.md, which this summary does not reproduce.

Risk, credentials: This use case gives the hub and agent read access to your Gmail, so store the connection on your own server and revoke it if you stop using it.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/timelovercc-mojito/daily-gmail-worth-reading-card/

## How to skip one Google Calendar event with Undo with Mojito

Repo: [TimeLovercc/mojito](https://github.com/TimeLovercc/mojito) | Difficulty: Advanced | Time: 1 hour | Basis: From the README

Ask in chat to remove a single recurring meeting from your Google Calendar.

**Who it is for:** A professional with a recurring meeting that is off this week and who wants it removed without editing the whole series.

**The problem:** Editing a recurring series by hand is slow, and deleting the whole series removes meetings you still want.

**The outcome:** Only the chosen occurrence is removed from Google Calendar, and you can undo the change in the app.

### Steps

1. Connect your Google Calendar to your self-hosted Mojito instance as the setup guide describes.
2. In chat, name the recurring meeting and the single occurrence you want to skip.
3. Check the change in your calendar.
4. If the removal is wrong, use the Undo that the app shows for the change.

### Prompt to paste into your agent

```text
In the TimeLovercc/mojito repo, remove only the occurrence of '<event-name>' on <date> from the connected Google Calendar. Expected output: confirmation that one occurrence was removed and the series is otherwise unchanged. Verify in Google Calendar that the other occurrences still exist.
```

### Caveat

The README gives this as an example request, and calendar setup details are only in docs/SETUP.md, so confirm the connection works in your own instance first.

Risk, credentials: Calendar write access lets the agent delete events, so limit this to one occurrence and check the result before relying on it.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/timelovercc-mojito/skip-one-calendar-occurrence/