SECURITY & CONTROL

Let agents build. Keep your branch yours.

Container agents work with an agent home directory and an isolated Git worktree. Panolayer stands between that workspace and your branch: verification first, your approval next.

How the boundaries fit togetherFrom isolated work to approved code

Room to build

Agent container

A separate environment for every agent you launch.

Coding agentRuns its tools inside the sandbox

Agent home directorySettings and files outside your personal home

Isolated worktreeStarts from your branch; changes stay here

No direct edits to your working branch

Request verification

The merge boundary

Panolayer

The gatekeeper between agent changes and your branch.

Verification Engine

Checks the proposed changes for regressions. Only a passing result unlocks a merge request.

Fix failed checks, then verify again.

Pass → request your approval

Your approval

Review the diff, findings, and any errors. You confirm the merge in Panolayer.

Approved merge

Back in your hands

Your branch

Only the changes you approve come back.

Verification passedHuman approved

Branch out to build. Pass verification. Get your approval. Merge back into your branch.

FREEDOM INSIDE. CONTROL AT THE BOUNDARY.

Give agents room. Keep the final say.

A workspace of their own.

An agent can install tools, create files, and work on code inside its container. Its agent home holds settings and files outside your personal home; each session’s isolated worktree keeps code changes separate from your everyday workspace.

A gate before your branch.

The Verification Engine checks for regressions before an agent can ask to merge. Failed checks keep the request blocked. If the agent changes the code again, it needs a fresh verification result.

You make the merge call.

A passing check opens the door to review. Panolayer prompts you with the proposed changes and verification results, including warnings and errors. The agent can ask; you decide whether it merges.

AND WHEN YOU’RE FINISHED

Work done. Workspace cleared.

When you finish a session, Panolayer releases its runtime and session files. Finished workspaces can be cleaned up; unmerged work stays available until you choose what to keep or discard.