AI 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.
Download Friday Studio  Supports macOS
Contact us
Friday Studio's run inspector showing a step-by-step execution timeline

What an agent harness actually does

A model reasons. A harness handles everything else so the model can focus on reasoning.

  • Memory — stores context across runs so agents remember what happened last week
  • MCP tools — connects GitHub, Slack, HubSpot, Gmail, and any MCP server
  • Scheduler — fires agents on cron, webhook, or message without you being present
  • Orchestration — FSM-based job execution with observable state at every step

Generated from conversation

Describe what you want. Friday writes the workspace.yml. You own the file.

  • No node editors, no drag-and-drop, no visual wiring
  • The config is plain YAML — readable, diffable, portable
  • Version it with Git, share it with a teammate, import it on any machine

Every run is traceable

Friday logs every step, every tool call, every decision. Nothing runs invisibly.

  • Session inspector shows exactly what each agent did and why
  • Failed runs show the exact step and error — no guessing
  • Fix the config, redeploy, run again from a clean state

Built for Mac

A native Mac app. Nothing to host, nothing to keep running on a server.

  • Daemon runs locally — memory, agents, and scheduler all on your machine
  • Your LLM keys go direct to the provider — no middleman, no markup
  • Free to download at hellofriday.ai

Common 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.

Discover Spaces

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

View on GitHub

Explore the Docs

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

Read the Docs

More Tips

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

Read the Blog

Done beats promised.

Download now Supports macOS