Workspace & native analysis
Files, native parsing, and local complexity analysis run on your machine. The editor uses project context to support your task.
SECURITY
What stays on your computer,
and what doesn't.
Understand what runs locally, what can leave your machine, and what a command approval actually means.
Where your code 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.
PERMISSIONS
Edits, commands
and approvals
Reviewing edits and approving commands
Review applied edits in inline diffs and choose command permissions 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.
ARCHITECTURE
How Lamied is built
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.
Checksummed installers
Every installer includes the native engine, and the Download page publishes its SHA-256 checksum so you can confirm the file arrived intact. The installers aren't code-signed yet.
REPORT A VULNERABILITY
Found a security issue?
Email us privately
Write to [email protected] with the subject “Security report”. Describe the issue, the steps to reproduce it, and the Lamied version or web page involved.
Give us time to fix it
Please don't share the issue publicly until it's fixed, and don't access other people's data or disrupt the service while testing. This address is also listed in security.txt.
Questions about permissions or data?
Contact the team