BETA RELEASE
Triggers for your agents, with you in the loop.
Personal AI automation that lives on your machine. Cron, files, and events wake your agents — watch, steer, or take over from one inbox.
$ curl -fsSL https://loopkeep.run/install.sh | sh
Run it three ways — the lk CLI, the desktop app, or the terminal UI.
WIRED TO YOU
Organization automation watches repositories. Yours watches you.
Workflows trigger on what happens to you — a mention, an assignment, a question in your channel — across the places you work. Being personal is the point: your agents act with your context, your credentials, and your taste.
You get mentioned
@you lands on an issue. The loop reads the thread, gathers context, and drafts a reply for your approval.
You get assigned
A PR is assigned to you. By the time you open it, review notes and a risk summary are already waiting.
Your own rhythm
Morning triage, nightly cleanups — cron loops tuned to how you work, not to your organization's pipeline.
And personal doesn't mean stuck: when a loop proves itself, promote it — export it to your team's repository as a GitHub Agentic Workflows file.
ATTENTION LEVELS
Every action gets exactly the attention it deserves.
A policy you write — and explicitly trust — grades every action an agent proposes. Your attention is the scarce resource; loopkeep spends it deliberately.
auto-approve
Routine work flows through. Logged in the event trail, never interrupting you.
notify
Worth knowing, not worth stopping for. Bundled quietly into your inbox.
ask-first
The run pauses and asks. Approve, steer, or abort — right from the inbox.
deny
Never allowed. A built-in floor that no policy layer — and no agent — can relax.
And when you want the wheel: take over a live run — loopkeep opens claude in your terminal or multiplexer so you drive it directly, then hand it back. The floor stays on the whole time.
ARCHITECTURE PRINCIPLES
Three principles we never break.
Only the wake signal travels
The cloud never sees your issues, messages, or code. It sends a nudge — your daemon fetches the real thing straight from the source, with your own credentials. Even a forged nudge can't start a fake run.
Content stays home
Signing in uploads nothing. Sync is off by default — and even when you turn it on, only metadata and summaries leave. The bodies never do.
Works when the cloud is down
Expired auth, no network, a full outage — cron, file-watch, runs, and your inbox keep working indefinitely. There is no kill switch to your automation.
CONTROL / DATA PLANE
Control plane and data plane, kept apart.
The Console owns sign-in, devices, connections, and entitlements. Delivery is a separate gateway: it takes the webhook and forwards nothing but the wake signal. Your daemon holds a single outbound WebSocket and opens no inbound ports.
- Persistent outbound WebSocket (WSS), no inbound ports
- Store-and-forward, at-least-once, idempotency keys
- Verdicts signed with the device key, ready for remote approval
SOURCES
GitHub · Slack
CONSOLE
control plane — login · devices · connectors
gateway — verify → wake signal (meta only)
YOUR MACHINE
loopkeepd fetches the real content directly, with your own credentials
CONNECTORS
Connecting is just an install.
GitHub
Install the shared GitHub App on your organization — that's the whole setup. It subscribes to issues and pull_request, and passes them on as wake signals. The App private key never leaves our servers.
Slack
One “Add to Slack” OAuth flow. No app to build, no token to paste. Message bodies are never carried; your daemon fetches them with the bot token.
NO LOCK-IN
Your workflows are markdown files in your repository.
Definitions live in .loopkeep/ as plain markdown with GitHub Agentic Workflows-compatible frontmatter — versioned, reviewed, and portable like any other code.
Import and run locally
Bring a GitHub Agentic Workflows file and run it on your machine — before push, with minute-level cron, and no Actions bill.
Promote what works
Export a proven loop to GitHub Agentic Workflows and it becomes your team's automation — every feature classified green, yellow, or red, nothing degrades silently.
Engine-neutral
Runs the claude CLI you already sign in with — API keys optional. Other engines connect over the same adapter protocol.
PRICING
You pay for server resources. Everything else is free.
The line is simple — remote operations that consume Console resources are paid. Anything that runs entirely on your own machine stays free.
Free
Desktop¥0Desktop only
- One paired desktop
- cron / file-watch / git / manual
- Remote revoke for a stolen device
- Runtime independent (runs indefinitely)
Pro
ConnectorsSoonConsole resources
- Multiple desktops
- GitHub and Slack connectors
- Remote approval (signed verdicts)
- Upstream sync (read-only mirror)
GET STARTED
Get loopkeep.
Install the CLI, run the desktop app, or live in the terminal UI — one runtime, all on your machine.
$ curl -fsSL https://loopkeep.run/install.sh | shmacOS · Builds are published on GitHub Releases.