Checks, not guarantees
Review the diff and recorded check results. A passing test is evidence, not acceptance.
Coding workspace · private preview
Delegate the change.
Keep control of the result.
A local workspace for coding-agent work. Keep the plan, conversation, diff and checks together—from request to review.
- Git-native
- Apple-silicon macOS · Linux
- Your coding agents
From request to review
Less coordinating. More reviewing.
- 01
Define the change
Choose a repository. Ask questions, then approve the work you want done.
- 02
Run the work
Changes run in a separate working copy, with progress and decisions kept on the task.
- 03
Review the result
Inspect the diff and check results. Publish only within the delivery scope you approve.
Work that stays together
Come back to the work, not an empty prompt.
Tasks, conversations, working copies and check history stay on disk. Interrupted work is recorded as interrupted—not quietly marked complete.
Review stays yours
See what changed. Know what was checked.
Your choice of runtime
Claude Code, Codex, local models and compatible endpoints. Claude Code is the preview’s most exercised path.
Measure the workflow
Record effort, cost and your judgement of the result. Missing inputs stay missing—not estimated.
Local storage does not mean offline execution. External providers receive work context. Provider-process confinement is macOS-only; provider internals are not fully visible to Struktly.
Common questions
What the product is, what it records, and what it deliberately does not claim.
Who is the preview for?
One developer working on a local Git repository. Claude Code is the most exercised path; Codex, local models and compatible endpoints are implemented but less exercised.
Does approval mean it can merge or deploy?
No. Publication requires an approved delivery scope. Changed plans or unproven results can need further review. A delivered pull request is not permission to merge or deploy.
Where does my work live?
Tasks, chats, working copies and check history are stored locally. External providers receive work context and can make their own network requests. Provider-process confinement is available on macOS, not Linux.
What happens after an interruption?
Saved work remains available. Recovery reconciles the recorded task and delivery state; ambiguous provider activity is not silently retried or marked complete.
Which platforms are supported?
Apple-silicon macOS and Linux x86-64/arm64. No Windows or Intel macOS build. The macOS preview is ad-hoc signed, not notarized; Linux bundles are unsigned. Follow the supplied verification and installation guide.
Do I need GitHub?
Ordinary work uses a local Git repository. Opening a draft pull request requires the GitHub CLI; plain pushes use your existing remote. The preview form uses your GitHub username to identify your request, not to grant repository access.
How do I get access?
Submit the form below. Requests are reviewed manually. Approved applicants receive an email with a single-use claim link. Requesting access does not guarantee approval or a response date.
Try it on a repository you already know.
For one developer and one repository at a time. Requests are reviewed manually; approved applicants receive a download link by email.
Requirements and preview limitations
What you need
- A Git repository on this machine that you know well
- Claude Code or Codex installed and signed in — Struktly runs the one you have
- Apple-silicon macOS, or Linux on x86-64 or arm64
What the preview does and does not cover
- Walked end to end
- A bounded repository change with Claude Code: ask, approve, inspect changes and checks, then deliver a draft pull request. Saved work remains available after reopening. This is preview evidence, not general release acceptance.
- In the build, less exercised
- Codex, the bundled local model, and OpenAI-compatible endpoints. Linux, which has no confinement boundary and says so. Pull-request import from GitHub into a workflow.
- Not there
- Windows and Intel macOS. More than one repository in one piece of work. Anything shared, hosted, or between people. Any figure Struktly did not measure or you did not enter.
How you get in
Approved requests receive a single-use claim link by email. Your chosen sign-in is then linked to your preview approval.
No automatic approval or promised reply date. Verify the release using the supplied installation guide and SHA-256 manifest.
- macOS
- Apple silicon. The build is ad-hoc signed and not notarized, so macOS refuses it on first launch; the installation guide has the one-time override and Gatekeeper stays on.
- Linux
- x86-64 and arm64, as a .deb, an AppImage or a Flatpak. There is no operating-system confinement around a provider process here, and Struktly reports that rather than implying one.
- Windows
- No build.
- Agents
- Claude Code and Codex, run from the CLI already installed and signed in on this machine, plus an OpenAI-compatible endpoint you configure yourself.
- Account and telemetry
- No product account required. Workspace data is stored locally; external providers receive work context.
- License
- A signed file you keep, verified offline on every machine you use. Reading and exporting what you already recorded never depends on it.