Waymark Studio · Coming soon

Mission control for agentic software delivery.

A native macOS workspace for turning issues into isolated agent runs, checked changes, intentional approvals, and recoverable releases.

Join the waitlist Follow a run
Waymark Studio
⌕···

Overview

Product Lab · 2 repositories

Governed work active
Next actionReady for governed work

Policy, validation, and agent boundaries are healthy.

Work in progressView all
Define release boundaryPlanner
Planning
Harden session isolationBuilder
Running
Review credential flowReviewer
Running
Verify rollback pathTests
Approval needed
Needs attention1
Production approval

Exact release plan is ready for review.

System healthView evidence
Lab boundary Ready
Audit integrity Pass
Agents 4 available
Local services Ready

One operational picture

From backlog to delivery without losing the thread.

Studio keeps product scope, agent work, repository gates, approvals, and release evidence attached to the same task.

Agent fleet

Coordinate planning, implementation, testing, and independent review across the models and harnesses you choose.

Managed workspaces

Each run starts in a Broker-owned worktree with explicit scope and recovery protection.

RepoSeatbelt

A separate agent-proof recovery path protects local source before risky changes and integration writes.

Validation profiles

Map repository expectations into repeatable local and disposable-runner checks with visible evidence.

Approval policy

Stop after merge, require an exact production approval, or automate reversible delivery under saved policy.

Fail-closed control

Emergency stop, stale proof, scope drift, unsafe commands, and incomplete cleanup all halt execution.

From issue to production

Give Studio the work.
Choose how far it goes.

GitHub Issues is the first task source. More trackers are planned. From there, Studio coordinates the agents, proof, privileged actions, and human decisions around one task.

Bring in real work

An issue becomes a governed task.

Requirements, non-goals, repository scope, risk, and finish mode are captured before any agent touches code.

GitHub Issues · available firstHarden release recovery

Scoped · reviewed · ready

Other task sources planned
Fan out the work

Plan. Build. Test. Review.

Different agents can take different roles. Independent reviewers challenge the implementation before it moves forward.

Keep work isolated

Every agent gets its own lane.

Broker-managed worktrees keep concurrent changes separate until they are reviewed and ready to integrate.

PlanBuildTestReviewTask
Prove the change

Review and tests must agree.

Local checks, security scans, disposable runners, UI evidence, and reviewer findings resolve into one visible result.

Independent reviewPassedRepository checksPassedSecurity scanPassedRelease verificationPassed
Broker-owned delivery

PR. Merge. Production.

Studio can create the commit, push the branch, open the PR, merge approved work, and run the exact authorized release path.

Each boundary has its own policy
Capability stays outside the model

Agents never receive the keys.

Repository tokens, cloud credentials, signing identities, servers, and production controls stay behind the native Broker wall.

Agents do the creative work. The harness controls what they can reach—and what they can never reach.

Automation is your choice

Step by step. Or policy by policy.

Pause at every decision while you build confidence. Then automate the routine paths you trust without removing the hard safety gates.

Speed changes. The security boundary does not.
01
Review every step

Approve the plan, agent run, PR, merge, and release separately.

02
Automate agent work

Let approved agents plan, build, test, and review while delivery waits.

03
Automate through merge

Allow verified, policy-matching changes to open and merge PRs.

04
Automate delivery

Run an exact reversible release path under saved product policy.

Local-first

Your code, credentials, and agent subscriptions stay yours.

Studio uses installed agent harnesses and customer-owned execution. It does not need to become a hosted IDE or token marketplace to coordinate serious work.

  • Native macOS control plane
  • Customer-controlled model choices
  • Local Tier-B source and transcripts
  • Customer-owned disposable runners

Agent request

Local Broker

Approved action

Credentials never cross into the agent process.

Your agents, one harness

Use the right model for each role.

Studio is built around installed agent harnesses and customer-controlled model choices—not token resale or a locked-in model cloud.

CodexClaude CodeLocal modelsCustom adapters

Integration depth varies during development. Launch compatibility will be documented before release.

Scale the Lab, not the complexity

One Mac when you want focus. Multiple Macs when you want throughput.

A Studio Lab can live on one Mac or span paired Macs. Adding Macs expands the available worker capacity, so more isolated agent tasks can run concurrently under the same Lab policy and evidence model.

01

Single-Mac Studio

Ideal for an individual developer or a focused product. The Mac runs the control plane, local agents, checks, and approved delivery work.

Simple local setup
02

Multi-Mac Lab

Pair additional Macs into the same Lab to distribute agent runs and increase concurrent capacity while preserving one governed operational picture.

More machines · more parallel work

One license includes one Lab.Pair multiple Macs to expand capacity inside that Lab. Additional Labs are purchased separately when you need another governance boundary.

Private preview

Help shape the safer way to ship with agents.

Join the Studio waitlist for product progress, early previews, and launch access.

Join the waitlist