What is running now
- Sessions waiting on you, first
- Workflows and subagents, with progress
- “Due back about 2:40 PM” for each run
- How many are working at once, and tokens per hour
Early access · macOS 15+ · iPhone on TestFlight soon
Your calendar fills itself in.
Didcal reads your Claude Code sessions on your Mac and turns them into calendar blocks: time at the keyboard, and time waiting on your agents. They sit next to your Google and iCloud calendars. You never log time.
Free while in early access · macOS 15 or later · Direct download
How it works
You never log time.
Didcal works from what your Claude Code sessions already wrote down, and from the calendars you already keep.
-
01
It reads your sessions on the Mac
Claude Code keeps a transcript of every session in
~/.claude/projects. Didcal reads them there. They are never uploaded. -
02
It splits your time two ways
Prompting and reading is time at the keyboard, drawn solid. While the work is with your agents, you are waiting on them, drawn hatched.
-
03
It sits next to your calendars
Your blocks go beside your Google and iCloud events, so one day shows what you planned and what you did.
Agents
Know what your agents are doing, and when they’ll be back.
Everything your prompts start, workflows and subagents included, has its own place, kept apart from your day.
What already ran
- Each run is one prompt of yours and everything it started
- “While you were away”: the overnight summary
- “Needs you” flags on runs that want a decision
- How it ran: agents, max at once, agent time, tokens, models, and a timeline
Calendars
Every calendar, with work and personal kept apart.
Add several Google accounts and your iCloud and macOS calendars. Each Google account signs in on its own, with calendar-only access. Add, edit and delete events right in Didcal. iCloud and macOS calendars stay on the device that has them.
- Blocks time
- Shown on your day and counted as meetings. Routines and focus are planned around it.
- Show only
- Shown, but Didcal can plan over it. Good for holidays and other people’s plans.
- Hidden
- Not shown and not used. It stays in the account untouched.
Routines and habits
Routines that make room for meetings.
- Checklists like Morning launch and Wind-down, each with a Full and a Short version for busy days.
- Steps count toward habits. A PT set ticks PT, a glass of water ticks Water.
- A nudge at the start time, never during a meeting.
- When a meeting lands on a routine, it moves to the nearest free slot.
- On iPhone, the checklist sits on your Lock Screen while it’s due.
- While you wait: when an agent run is long, Didcal suggests a habit or a focus block that ends when the run is due back.
iPhone · TestFlight soon
Step away. Your phone knows when they’re back.
The iPhone app shows your day and your agents, from summaries your Mac uploads to your Didcal account.
- Today: your blocks, your calendars, and your habits.
- Agents: what needs you, “remind me at 9 AM”, and the reply to read.
- A Lock Screen notification when an agent run finishes.
- A new event sheet for any calendar you can edit.
Privacy
Your transcripts stay on your Mac.
Didcal reads your sessions where they already are. No Didcal server stores your transcripts.
On your Mac
Transcripts
Read from ~/.claude/projects on your Mac and never uploaded.
In your Didcal account
Summaries, not transcripts
Times, session titles, counts and results, so your iPhone and the web can show them. Prompt text goes too only if you turn it on.
With Google
Calendar access only
Didcal reads events and can add, change or delete events in calendars you can edit. It never sees your email.
Early access
Early access is free.
Didcal is free while it is in early access. The Mac app is ready to download; the iPhone app comes to TestFlight soon. A Projects roadmap comes later.