+ INFRASTRUCTURE FOR AGENT-BUILT SOFTWARE

Give your agents
somewhere
to build.

A persistent home for the tools your agents create. Run them in isolation. Keep their data. Make them better with every session.

Design partner preview · Working foundation · Runnable prototype

CAPABILITY / RESEARCH-DIGESTInteractive model
01 / Define the capability
PERSISTENT TOOL

Research digest

v1
Tenant data Isolated runtime Scoped input

A small tool. Its own data. A place to run.

01✓Resource graph resolved
02✓Tenant data attached
03✓Tool version 1 stored
records → summarize → digest
Illustrates the tested prototypeSee the evidence ↗
THE FOUNDATION
Effect + Alchemy + Cloudflare
One programmable system ↗

01 / SOFTWARE THAT OUTLIVES THE SESSION

Useful once.
Useful from now on.

Your agent builds a research tracker, a reporting tool, a tiny internal app. It works. Then the session ends.

Harness Compute is being built to give that software a durable home—with its execution, data, and permissions managed together.

Meet the capability model →

02 / THE COMPLETE LIFECYCLE

From an idea
to a capability.

Build something useful.
Then keep making it useful.

01

Define it

Application code and infrastructure in the same typed model. Dependencies become part of the program.

Effect + Alchemy
02

Run it

Execute tool code in an isolated Worker. The trusted host decides what data and capabilities it receives.

Cloudflare Dynamic Workers
03

Keep it

Store the tool and its data beyond the current session. Upgrade behavior without replacing the underlying records.

Persistent source + D1
04

Control it

Version capabilities and revoke access. Build a system that can change its mind about what should run.

Host-enforced boundaries

03 / RUNNING CODE, BEFORE BIG PROMISES

The engine runs
in the cloud.

We ran Alchemy’s infrastructure engine inside a deployed Cloudflare Worker. It created a real resource, updated it, and deleted it—all from the Worker itself.

Read the reproduction →
PROTOTYPE VALIDATION SEP 2026
14 / 14Application checks passed
locally and on live infrastructure
  • ✓ Data survived restart and redeployment
  • ✓ Tool upgrades preserved existing data
  • ✓ Tenant separation and revocation checked
  • ✓ Worker-hosted infrastructure lifecycle verified

Functional evidence, not a production SLA. Durable deployment recovery is still ahead.

04 / START WITH ONE USEFUL THING

Small software.
Longer shelf life.

Explore the use cases →
[ 01 ]

Tools that remember

A research tracker that keeps its sources and improves how it summarizes them.

PERSONAL SOFTWARE
[ 02 ]

Workflows that evolve

An internal reporting tool whose behavior changes without losing its working history.

TEAM UTILITIES
[ 03 ]

Environments on demand

A bounded place to deploy and exercise agent-built code against actual infrastructure.

AGENT DEVELOPMENT

These are the workflows we want to build with design partners.

DESIGN PARTNER PREVIEW

What would your agent build
if it had somewhere to keep it?

Bring one real workflow. Help shape the runtime around it.

Let’s build it ↗