Control,
by design.
How LocalDesk handles your work today — described plainly, with nothing rounded up.
Workspace boundaries
A Mission works inside the workspace you open for it.
Human approvals
Actions that reach outside your workspace — sending, publishing, purchasing — wait for your approval.
Execution visibility
File changes, tool calls and terminal output are shown as they happen.
Stop at any point
You can stop a running Mission at any point.
Audit records
High-impact actions are recorded in an audit trail.
Where work runs
Missions execute through a local runtime on your computer. Model requests go to the AI providers LocalDesk routes to.
Accounts and payment
Sign in with a single-use email link, Google or GitHub. Payment happens on a hosted checkout; card details never pass through this website.
Your account data
Account records are kept apart per user with database row-level security.
Every action has a permission level.
Read
Open files, search the codebase, read documents
Automatic
Safe write
Edit files inside the workspace, run tests
Automatic
External change
Send email, push to GitHub, publish
Needs your approval
High impact
Purchases, production changes, deletions
Needs explicit confirmation
What we don't claim.
We don't display certifications, audit reports or security badges that LocalDesk doesn't hold, and we don't describe encryption or data-retention guarantees until they are implemented and verified. When that changes, this page will say so — specifically.
Model requests are processed by the AI providers LocalDesk routes to. Missions execute through a local runtime on your computer, inside the workspace you choose.