Workspace & native analysis
Files, native parsing, and local complexity analysis run on your machine. The editor uses project context to support your task.
CLARITY BEFORE CONFIDENCE
Your code deserves
clear boundaries.
Understand what runs locally, what can leave your machine, and what a command approval actually means.
Know where the context goes.
Local analysis and AI requests are different parts of the workflow.
AI & embedding providers
Cloud configurations may send relevant code, prompts, and tool output to configured providers or services. Remote embeddings may also transmit code during indexing.
Review provider policies, account settings, and model and embedding endpoints before opening confidential repositories. A local model setting alone does not guarantee that every application feature works offline.
PERMISSION IS A CHOICE
Useful automation.
Visible responsibility.
Approve the work
Review file-change requests and command approvals in the editor. For trusted workspaces, command permission can be remembered and later revoked.
Understand shell access
A command runs with your operating-system permissions and can affect more than the current folder. A workspace approval is not an operating-system sandbox. Read commands before granting broad permission.
THE BUILDING BLOCKS
Native where it matters.
Native C++ engine
The packaged native addon powers parsing and analysis. It loads in the Electron process; it is not a separate security boundary.
Desktop interface
An Electron application brings editor surfaces, project navigation, and terminal tools into one workspace.
Verified installation
The Debian release includes the native engine and a published checksum. Package validation checks native loading and application startup.
Have a security question or found an issue?
Contact the team