An agent harness, generated from conversation

A decent model with a great harness beats a great model with a bad one. Friday is the harness.

Complete runtime: memory, MCP tools, signals, scheduler, and FSM orchestration.
Generated from conversation: Friday writes the workspace.yml. One file you own.
Config you control: versioned, diffable, portable. No invisible runtime behavior.

Frequently asked questions

What is an AI agent harness?: An agent harness is the runtime layer around your model — handling memory, tool access, scheduling, credentials, and orchestration so the model can focus on reasoning. Friday ships the harness pre-built.
How is Friday different from OpenClaw?: Friday is built for reliability from the start. Workflows run from a versioned workspace.yml — diffable, repeatable, importable, shareable. Every run is traceable to the config that produced it. No hidden state, no invisible behavior to debug around.
What is workspace.yml?: The single source of truth for a Friday workspace. It declares agents, tools, triggers, memory stores, and job steps in one file. Diffable, portable, and readable without a UI. Runs identically on any machine.
How do jobs get triggered?: Signals. A signal can be a cron schedule, an HTTP endpoint, a Slack message, or a webhook. You define the trigger in workspace.yml; Friday's signal gateway handles the rest.
What happens when an agent fails?: The FSM captures the failure state. You get the exact step, the error, and the config that produced it. Fix the workspace.yml, redeploy, and the job runs from a clean state — no hidden runtime behavior to debug around.

Browse what we've built, import any space, and have it running today.

Learn how Friday Studio works and what you can do with it today.

Read our blog for more on how we're building and using Friday.