Auth timeout fix
Runner working, 3 h. Tests green so far.
Before the prompt
The work goes on under the lid.
Offlid is a private preview of a contribution desk for one person. Before an agent gets a prompt, see how an issue or personal brief could be weighed against policy, maintainer context, predicted overlap, and the proof the change must carry.
See how it works
Private preview. No connections, runs, or payments yet.
Saturday, 7:41 a.m. Quiet up here.
Repro for the worktree crash
Failing test written. Fix in progress.
One question waits for morning
Keep the legacy session format, or migrate?
Illustrative flow
Choose the contribution worth an agent slot.
The proposed flow begins only after a task is chosen. Offlid starts earlier: compare a few candidates, keep shared ground serial, and pass on work that has not earned the cost or attention.
Chosen for tonight
Fix crash when a session resumes with no worktree
Maintainer confirmed. Failing test attached. Session recovery only.
What returns
The same docket, now with proof
Supported146 tests at the returned commit
Needs youOne timing choice remains judgment
One of three slots
Predicted overlap: none. Shared files stay serial.
Nothing merges yet
Failing test firstfour of six checks passing
The runner stays linked to the docket above.
Two runner slots remain free.
Needs your judgment
Keep the legacy session format, or migrate?
Illustrative return
Two things returned. One needs you.
This example is the entire morning briefing. Not a feed, a queue, or forty notifications. Just the delta since you closed the lid, and at most one question.
Returned 2:14 a.m.
Auth timeout fix, PR #491
Tests green. Contract unchanged at the surface.
Returned 4:02 a.m.
Worktree crash repro and fix
Failing test first, then the fix. Both in the pull request.
Needs you
Keep the legacy session format, or migrate?
The review
You are not reading 400 lines. You are answering one question.
The intended receipt keeps its contract, commands, results, and changed files together. Anything uncertain would be flagged before you open the diff. Review bots inform your judgment. They never grant permission to ship.
Example proof receipt
Passed146 unit tests, 12 new
PassedRepro script, before and after
FlaggedTiming constants chosen by judgment, worth your eye
NotedTwo review tools flagged the same constants
What stays under your control
Read-only until you say otherwise
The planned GitHub connection begins with sight only. Write access remains a separate, explicit choice for each repository.
Nothing merges without you
A runner may prepare a branch and draft a pull request. You decide whether anything leaves your account, and you decide whether it merges.
Repos you do not own, respected
Before dispatch, Offlid is designed to show contribution and AI policy, keep the change bounded, and stop work that the repository forbids.
One person’s judgment, not a team’s process
No projects, cycles, assignees, or inboxes. If it belongs in a project tracker’s sidebar, it was left out on purpose.
Planned pricing
Pay for the desk. Keep run costs visible.
The hosted price is a working target while the private preview is being built. No payments are being taken yet.
Hosted Offlid
The reasons, decision memory, planned dispatch record, and morning return.
$20 a month target
Agent work
Runner and model charges sit outside Offlid. The biller, estimate, and cap will be shown before dispatch.
Planned separately
See which contribution deserves a slot.
See the grounds first. Send nothing until the set makes sense.
Explore the preview
Private preview. No connections, runs, or payments yet.