Actofy documentation

Product overview

The core concepts behind Actofy — plain language, no jargon wall.

Actofy behaves like a senior engineer inside a real dev environment: it reads your repo, plans work, executes in isolation, validates evidence, and ships a pull request — pausing whenever you need to approve.

Blueprint
The step-by-step execution plan Actofy drafts before writing code. You can approve, edit, or reject it at a Checkpoint.
Checkpoint
A typed approval gate before risky actions — shell commands, file writes, merges, deploys. Every pause is logged in the Console.
Workspace
Where a run executes: your Mac by default (local-first), or a hosted runner when you opt into team tiers.
Validator
Independent agents that re-check work — tests, lint, logic review — before Actofy opens a PR.
Console
The audit surface: every tool call, diff, terminal line, and approval decision in one timeline.
Build / Run
A Build is your task container; a Run is one execution session on a Workspace tied to that Build.

Surfaces

  • Actofy desktop app (macOS) — Workbench composer + Console
  • CLI (operator) — headless access to the same control plane
  • Hosted console (Team+) — cloud sync and shared workspaces