Thought for 2.1s
Dead runner runner-11 held the lock on Acme’s export jobs. Releasing the claim and requeuing.
Agent infrastructure to enable the right harness, model, and context for every task.
import { Checkfu } from "@checkfu/sdk"const checkfu = new Checkfu({ apiKey: process.env.CHECKFU_API_KEY! })// 01 Create agents: pick a harness and a model for each jobconst fixer = await checkfu.agents.create({ name: "fixer", harness: "codex", model: "gpt-5", system: "Fix the failing test you are handed, then run the suite.", tools: [{ type: "agent_toolset_20260401" }],})const reviewer = await checkfu.agents.create({ name: "reviewer", harness: "claude-code", model: "claude-opus-5", system: "Find the root cause, hand the fix to the fixer, review its diff.", tools: [{ type: "agent_toolset_20260401" }], multiagent: { type: "coordinator", agents: [{ type: "agent", id: fixer.id }] },})Choosing the right model is only part of the equation. Pairing it with the right harness, context, and taste is what makes an agent actually work.
Every agent runs on an isolated machine with a terminal, filesystem, and browser. Fully managed out of the box, with zero infrastructure to configure.
A worker can die mid-command. The run keeps going, and the result lands once.
A desktop, a browser, and files that stay put for days.
Fresh compute in under a second. Run one job, then throw it away.
Easily mount git repositories, files, memory, and skills. Give your agents the exact context needed for each task.
Each agent mounts only what its job needs.
Give your agents tools across thousands of MCPs and APIs. With encrypted credentials, automatic token refresh, and permissions handled for you, focus on picking the best tool for the job.
Team chat, workspaces, calendar schedules, and email automation.
Issue tracking, design tokens, error monitoring, and code repositories.
Deep research, web crawling, neural search, and live browsers.
Cloud databases, serverless platforms, edge compute, and metrics.
Payments, CRM pipelines, storefront orders, and workflow triggers.
Every service with an MCP server or OpenAPI spec works out of the box.
Connect agents to your existing channels or integrate via API. Every session is saved to an exportable log, so you truly own your data and can continuously improve your agents.
Thought for 2.1s
Dead runner runner-11 held the lock on Acme’s export jobs. Releasing the claim and requeuing.
Found it, and it’s moving.
runner-11 died while holding the lock on Acme’s three export jobs. With maya’s approval, I released the claims and requeued the jobs. 1 of 3 finished; the rest will land in ~10 minutes.
Session
Run
Cost
From coding orchestrators and personal assistants to team coworkers and autonomous agents, build what’s next on Checkfu.
fix-flaky-tests
cloud+9 −3
bump-deps
local+41 −41
migrate-api
cloud+212 −87
rename-config
local
local runner
CI is flaky on the payments suite. Find the leak and fix it.
running vitest --retry 2
3 failed, isolating test order
patch applied to test/setup.ts
412 passed, opening summary
A shared fixture leaked between files. Reset it per test; suite is green.
test/setup.ts+8 −2
vitest.config.ts+1 −1
Fleets of parallel coding agents running inside isolated cloud microVMs with git worktrees and automated pull request generation.
Today 8:52
Delivered
7:00 · automation morning-brief
A 24/7 personal executive assistant with long-term memory, daily schedule triage, and proactive morning briefs.
Chats
Tasks
Projects
recent
Checkout spec → issues
Refund policy audit
Launch handbook refresh
Turn the checkout Figma spec into Linear issues and post them to the launch channel.
read figma:checkout-v3 · 12 frames
drafted 4 issues with acceptance criteria
create 4 issues in linear:acme — decide in Checkfu
created LIN-231 … LIN-234
posted summary in #launch
In-channel teammates collaborating with engineering and product teams inside shared Slack and Discord threads.
Acme Corp ▾
channels
# compliance
# legal-ops
# vendor-risk
apps
Fizz
priya9:02
FizzAPP9:02
acme-msa.pdfConfidential2 fields masked
northwind-nda.pdfInternalclean
globex-dpa.pdfRestricted6 fields masked
Tagged 14 files in box:legal-vault · audit trail written
Autonomous back-office agents classifying compliance documents, auditing risk factors, and tagging files in enterprise vaults.
Track today’s discussion of agent harnesses. Verify anything surprising, then draft a thread.
On it. Honey scouts, Fizz verifies. I’ll only pull you in for a yes.
MessagedHoney· 14 messages
Honey found three threads. The surprising one claims swapping harness mid-session drops tool state. Handing it to Fizz.
MessagedFizz· 11 messages
Fizz reproduced it: real on one harness, fixed this morning. Draft thread is ready with both links. Post it?
yes, post it
Posted. Honey keeps watching; next pass in 15 minutes.
Bumble’s screen
Routines
A crew of lightweight bots you message like contacts, each with its own durable computer, coordinated as one crew and reachable over A2A.
Focus on what differentiates your product experience with the right choice of model, harness, context, and taste.
Survive crashes and resume runs from the event log.
Isolated cloud or local compute decoupled from the loop.
Stage Git repos and files with zero app-side git.
Vaulted tokens with auto-refresh. Secrets stay hidden.
Personal vs. workspace scopes with human ActionApprovals.
Call MCP tools and APIs without custom protocol glue.
Proactive runs triggered by schedules and webhooks.
Scoped memory stores that auto-update from sessions.
Bind Slack and Telegram threads with delivery queues.
Coordinators delegating tasks to subagent teams.
Grade runs against success rubrics before closing.
Versioned prompts and scripts agents load on demand.
Pick the harness and model. Checkfu runs everything around them.