Local-First
Open tasks live in SQLite on your machine. Nothing leaves your computer until you schedule something or sync.
Tasks + Calendar · TUI + Agent-Native
Your calendar speaks shell
your agent gets it
Local-first tasks and Google Calendar sync. Capture in a backlog, schedule when it matters, and work from the TUI, CLI, or your agent.
brew tap alexapvl/mytime https://github.com/alexapvl/mytime && brew install mytime
Why mytime
Local, Synced, Agent-Ready
Capture tasks locally, schedule them when ready, and use the same calendar CLI workflow in your terminal, shell scripts, and agent sessions.
Google Calendar Sync
Scheduled work syncs to a dedicated "mytime" calendar. Other calendars can be pulled read-only for context in daily and week views.
Agent-Ready
mytime agent exposes the same database with token-efficient
output and next-step hints. MCP is still available for older clients.
Workflow
From Backlog to Calendar
mytime is built around a simple loop: capture without pressure, schedule when it matters, then see the day in one terminal view.
1. Capture
Add tasks with quick-add NLP, priorities, projects, and tags. Unscheduled work stays in the backlog until you are ready.
2. Schedule
Pick a slot from free-time hints, move blocks by hour, or mark something all-day. The schedule editor shows what is already on the day.
3. Live It
Daily, week, and month views keep tasks and external calendar events in one place. Sync keeps Google and local state aligned.
mytime · synced 2m ago
[1] Backlog [2] Daily [3] Week [4] Month [5] Past Due
P0
ship mytime site
fix sync edge case
P1
review PR @work
grocery run
P2
write release notes
P3
read rust book ch.4
←/→ column · ↑/↓ select · s schedule · q quick-add · r sync · esc quit
For Agents
Setup Your Agent Can Do Most Of
Google OAuth needs a one-time Cloud Console project. That sounds annoying, but it keeps credentials on your machine and avoids a hosted service. An agent with browser access can handle most of the clicking.
mytime setup --agent-onboarding-prompt
Paste the onboarding prompt into your agent after install. Your agent gets the same backlog, schedule, slots, and sync tools you do.
# made for agents - TOON output, contextual hints (axi.md)
$ mytime agent
backlog 4 open
p0 ship mytime site
p1 review PR @work · tomorrow 3pm
today Sun Jul 12
09:00 standup
15:00 review PR @work
past due 0
help:
mytime agent task quick "dentist Fri 2pm"
mytime agent slots --date tomorrow
mytime agent sync
Setup
Install, Configure, Authenticate
Same three steps either way - agent-assisted setup is fastest if you already use one.
Install first, then let your agent handle the Google Cloud Console setup.
01
Install mytime
Homebrew is the fastest path on macOS. Source install works anywhere with Node 20+.
brew tap alexapvl/mytime https://github.com/alexapvl/mytime && brew install mytime
02
Run agent onboarding
Paste this prompt into your agent. With browser access, it can walk through the Calendar API, consent screen, and OAuth client setup.
mytime setup --agent-onboarding-prompt
02
Set up Google Calendar
Run setup for a checklist and Console links. You will place OAuth
credentials at ~/.mytime/credentials.json.
mytime setup
03
Authenticate and sync
Google sign-in opens in your browser. After that, sync creates the dedicated mytime calendar.
mytime auth
Privacy
Your Machine, Your Google Project
mytime does not ship shared OAuth credentials. That is intentional for a personal, local-first tool.
No Hosted Service
Tasks and tokens stay under ~/.mytime/. There is no maintainer server in the loop.
Write Scope Is Narrow
mytime only writes to its own calendar. Other Google calendars are optional and read-only.
You Own Revocation
Rotate or delete credentials any time in Google Cloud Console. Your agent never needs your token file in git.
FAQ
Common Questions
Ready to Try It?
Install, run setup, and open the TUI. Your backlog is waiting.
brew tap alexapvl/mytime https://github.com/alexapvl/mytime && brew install mytime