Think inside your AI world.
Google Calendar + GitHub through Unl
Open pull requests need focused hours; meetings eat them. Whether what’s open this week fits the time that’s left is a question the calendar and the repo can’t answer apart.
Google Calendar + GitHub through Unl weighs the hours meetings leave against the open work in GitHub, judged by the shipping-capacity rule you set, so the week reads as “shippable” or “more open than the hours hold.” The rule is held in Unl.
The criterion that binds them
Say you’ve ratified a shipping-capacity rule: the focused hours a week can hold once meetings are counted, and the rough hours each open item needs — because promising a merge in a week booked solid is how a deadline quietly slips.
The two naked reads
Google Calendar returns the booked events and free/busy. GitHub returns the open pull requests, issues and their state. Each is exact and blind to the other — the repo has no idea your week is booked, the calendar has no idea what’s queued to ship, and the two never meet until the deadline arrives.
The one measured answer
Against your rule: once meetings are counted, roughly fourteen focused hours remain; the queued pull requests and issues need about twenty — a good six hours beyond the capacity you set, so a couple of open items simply won’t land this week unless something gives.
And back again
The moment you park a non-urgent pull request for the following week, you settle that in Unl — and the following read sizes the queued work against the hours you genuinely have left.
The answer comes back measured against what you already decided, and why.
A router can line up Calendar events with GitHub work. What it can’t say is that the queued work won’t fit, because the shipping-capacity rule — focused hours weighed against each open item — belongs to neither the calendar nor the repo.
The lane is live and open to this tool today: one box, paste anything. If it speaks MCP, Unl can reach it. Readings arrive unprompted, the data beside the criterion; Unl is a courier, not a warehouse, and keeps only your keys and the frame.
Read further
Questions people ask
Can AI tell me if I have time to ship my open work?
Yes, through Unl. You ratify a shipping-capacity rule — real hours after meetings, against the work each open item needs — and Google Calendar and GitHub are read together against it, so the week reads as shippable or over capacity.
Why can’t a calendar app answer this?
The calendar knows your time and GitHub knows your open work; neither holds your capacity rule. That rule lives in Unl, so only a read across both can tell you the week holds more than the hours allow.
Does Unl change my calendar or repo?
Unl reads through Google Calendar and GitHub, and can write back on your explicit gesture — it never acts as a side effect of a read.
What this is
Think inside your AI world — you stay in command
Unlimitless (Unl to friends) holds what you've settled, reads what your tools are showing, and catches what's changed out in the world — and hands your AI whatever bears on the work, the moment it's needed, without you asking. The right thing, in front of the model, unprompted, with you in command of the call. So you keep moving toward what you set out to build, on top of everything you've already decided.
It plugs into Claude, Claude Code, ChatGPT and Cursor as an MCP connector. Quick to connect, in a couple of steps.
Unlimitless is open now to invited Alpha. Apply for the Beta waitlist to come in ahead of the full launch:
Alpha is invite-only · free at launch.