Give your AI tools real-time availability context so they know when to act, when to wait, and when to escalate. Setup takes about 2 minutes.
{
"status": "OFFLINE",
"returnsAt": "2026-04-03T09:00:00-06:00",
"action": "DEFER",
"reason": "Offline until 9 AM. Queued for morning digest."
}
{
"status": "OFFLINE",
"returnsAt": "2026-04-03T09:00:00-06:00",
"action": "DEFER",
"reason": "Offline until 9 AM. Queued for morning digest."
}
One shared availability layer across Claude Code, Pi, Cursor, VSCode, iOS, and Android.
hd busy 2h
from your terminal. A tap on your phone. Or let Google Calendar handle it automatically. HeadsDown knows when you're online, in deep work, or gone for the night.
Before interrupting, your agent checks once and gets a clear answer: proceed, wait, or escalate only when your rules allow it.
Back in 20 minutes? The agent waits. Gone until morning? It queues the question for your digest, or taps your watch for a 10-second yes/no when it is truly urgent. Your rules.
This is where individual builders lose time. The hard tasks are the ones that need one quick human call. HeadsDown makes that call explicit.
Your agent hits a decision at 11pm. It does not know you are asleep, so it stalls for hours on a question that should take 10 seconds.
Multiply by every night, every meeting, every lunch break.
Your agent hits a decision while you are in a meeting. HeadsDown says "back in 22 minutes," so the agent keeps moving and asks at the right moment.
No notification needed. No wasted time.
Your agent hits a decision at 11pm. HeadsDown says "offline until 9am," so it can queue for digest and send a quick watch approval only when needed.
Your rules. The agent follows them.
Native iOS and Android apps with push notifications, home screen widgets, Apple Watch and Wear OS complications, and lock screen quick actions. When your agent needs a yes/no at 2am, it taps your wrist. When you wake up, your morning digest is waiting.
The difference between a productive overnight agent and a stuck one isn't the model. It's whether the agent knows your availability.
Same task, two outcomes. Without context the agent stalls. With HeadsDown it defers cleanly and closes the loop in digest.
Scene 1
The agent sees Sam is busy and should avoid non-urgent interruptions.
Scene 2
HeadsDown returns a clear defer decision instead of waking Sam up mid-focus.
Scene 3
Sam comes back to one clear digest item and decides fast, without context switching.
{
"decision": "DEFERRED",
"reason": "Sam is in focus mode until 12:00 PM",
"nextAction": "Queue for digest",
"returnsAt": "2026-04-03T12:00:00-06:00"
}
Everything. No paywall. No "upgrade to unlock." Early access members get the full product while we're building it.
hd busy 2h
hd offline until 9am
hd online
Free to use right now. No credit card required.
HeadsDown is an API. Anything that can make an HTTP request can check your availability before it interrupts you: agents, Slack bots, deploy pipelines, CI/CD, internal tools. Start with your agent. The rest follows.
Everything on your machine is open source and auditable. The engine behind the API is the product.
// The agent checks HeadsDown before every taskimport { GraphQLClient } from "graphql-request"; const client = new GraphQLClient(HEADSDOWN_URL, { headers: { authorization: `Bearer ${API_KEY}` },}); export async function beforeTask(task) { const { submitProposal } = await client.request(` mutation($input: ProposalInput!) { submitProposal(input: $input) { decision reason proposalId } } `, { input: { agentRef: task.agent, model: task.model, framework: "pi", description: task.description, estimatedFiles: task.files, estimatedMinutes: task.minutes, sourceRef: task.id, }, }); if (submitProposal.decision === "DEFERRED") { return task.defer(submitProposal.reason); } return task.proceed();}
I spent three years building availability tools for humans. The problem was always the same: things interrupt people because they have no idea who's available. Then I started using AI agents and realized they have the exact same problem. Same gap, new audience. This time the integration is two minutes, not two quarters.
Solo founder. Elixir + Phoenix. Building in public.
Create your account, connect your tool, and set interruption rules in about 2 minutes.
Free to use right now. No credit card required.