saphan init
Lays out a workspace and then, with your consent, writes its verification settings and the minimum permissions Claude Code needs there.
Lays out a workspace and then, with your consent, writes its verification settings and the minimum permissions Claude Code needs there. The layout step creates bridge/, sources/, worktrees/, tmp/ and an empty repository list, touching only what is missing. If this build carries a vendor-signed set of standing-rule documents, init verifies it and files it into the workspace's record (a set that fails verification stops init with nothing filed). Then two writes are each explained and proposed, with "no" as the default: the test suite saphan certify should run for the detected stack, written to your configuration file (<prefix>/etc/saphan.conf), and in .claude/settings.json a minimal Claude Code allow-list (git add, commit, status and diff) plus a session-start hook that tells a Claude Code session its unread messages and role memory. Codex gets no allow-list, because it does not read that file; it is confined by its own sandbox. Every answer, yes or no, is appended to .saphan/state/init-grants.jsonl; declining the Claude Code write exits non-zero, and re-running on a complete workspace changes nothing.
| flag | type | default | what it does |
|---|---|---|---|
--yes | bool | false | Gives consent to every proposed write without an interactive prompt; without a terminal and without this flag, nothing is written. |
Global options apply to every command — see Every command.
saphan infra
Places the deployment files Saphan Studio needs (container compose files, the telemetry collector configuration and a runbook) on disk, stores their secret values, and prepares the databases they serv
saphan install
Sets up this machine for Saphan Studio by running every step a new workspace needs, in order, and reporting each as already done, done now, or not done with the reason.