THE AGENTS ARE IN THE COMPUTER.

Scroll

SO PUT THEM IN A BOX.

Stop letting AI tools run loose on your machine and bring law and order back to your development workflow with Heff.

03Out of your repo, into a sealed container

ALONGSIDE YOUR CODE. NEVER INSIDE OF IT.

Heff · encapsulation

your repository

src/

api/

worker/

tests/

package.json

AI artifacts

.agent-config/ .mcp/ .cursorrules .env.agent

AI state, keys and prompts that sprawl through your tree and into git history.

AI container · sealed

Identities & scopes4 registered

Run history & artifactsappend-only

Secrets & grantsAES-256

Tickets, PRs, reviewsnative

Every AI artifact lives here, sealed and kept out of your git history.

ENCRYPTED

AES-256 at rest, keys held on device.

PEER TO PEER

Share an AI container with a teammate directly. No copy on our infrastructure.

LOCAL FIRST

Works offline. The AI container is a file, not an account.

SCOPED

Every path, key and network call an agent touches is granted, not assumed.

04one pane for the whole workflow

EVERYTHING RUNNING, EVERYTHING WAITING ON YOU

Tickets, pull requests and agent runs are objects in the same container, so they share one queue and one set of rules.

Running now4 active · 2 queued

Migrate queue worker to retry budgets

claude-code · step 4/7 · writing tests

4m 12s

Rotate staging credentials

paused · requests read on ~/.aws/credentials

held 40s

Backfill changelog for v2.14

cursor · step 2/3 · summarising commits

1m 03s

Nightly dependency audit

failed · lockfile drift in packages/api

02:14

Regenerate API client

queued · waiting on capacity

—

Needs you3

Grant read on ~/.aws/credentials?

requested by rotate-staging-credentials

Allow onceDeny

Review PR #4182

agent-authored · +412 / −87 · waiting 6h

HEFF-1188 blocked

no staging environment available

05automations, gated at the boundary

IT ASKS BEFORE IT REACHES

inside the container

outside · your machine

trigger

plan

edit files

~/.aws/credentials

permission requested

nightly-rotate wants to read ~/.aws/credentials

not covered by any existing grant · run is paused

Allow for this runDeny

A workflow runs inside the container.

Grants, not trust

An automation starts with nothing and asks for each path, key and endpoint it needs.

One decision, recorded

Allow once, allow for this workflow, or deny. Every answer is written to the run log.

Nothing runs unattended by accident

Unattended is a mode you turn on for a scoped grant, not the default.

06 · early access

YOUR CODE. YOUR MACHINE. YOUR CALL.

Early access is opening soon. Leave your email to be first in line for an invite.

No newsletter. One email when your invite is ready.