Local Workbench
Repositories, installed tools, local data classifications and terminal behavior.
SECURITY & PRIVACY
Your environment deserves
plain-language boundaries.
Workbench is designed around local development. Before launch, every statement here will be checked against the shipping implementation.
Implementation review required before launch
FOUR DISTINCT BOUNDARIES
Know which system
handles what.
No single “local-first” label can answer every privacy question. Workbench documentation will distinguish local application storage, Apple-managed synchronization, Req2Code services and agent-provider processing.
Apple services
Any optional iCloud synchronization and the data included in that boundary.
Req2Code services
Future account, billing, support and commercial records.
Agent providers
Information sent to Codex or Claude Code under your provider relationship.
LAUNCH DISCLOSURES
The security page will answer
the practical questions.
- Where Workbench runs and how repositories are accessed
- What remains local and what may synchronize
- Whether terminal transcripts are captured
- How source code and credentials are treated
- What external agent providers may receive
- How signed updates are delivered
- How data can be exported or deleted
- How vulnerabilities can be reported
!
Report a security concern ↗Claims follow the product.
Offline behavior, synchronization, transcript handling and provider boundaries are launch-sensitive. This draft site deliberately avoids turning those open decisions into promises.
WORKBENCH
See how local execution
fits the workflow.
Explore the product model, supported agents and evidence-based verification.