SETUP GUIDE
Get started
with Lamied.
Install Lamied, open a project, connect your AI model, make a first change and publish it to GitHub.
For Linux and WindowsExplorerYour project's files and folders.
EditorThe files you open, in tabs.
AI assistantQuestions and changes, beside the code.
INSTALL
Install Lamied
Download the installer for your computer, save it in Downloads, and close any running Lamied window.
Then follow the steps for your system.
Open the Download pageFor Linux and Windows. No account needed to download.
cd "$HOME/Downloads" &&
sudo apt install "./lamied.ai-0.4.0-amd64.deb" &&
lamiedUse the folder and filename you actually saved. Your system may ask for your password or for permission.
Already installed, or updating?
Close every Lamied window before installing an update. Reopen the app and run lamied -v to check the version. The download page includes checksum and reinstall commands.
OPEN A PROJECT
Open your project folder
Choose File → Open Folder and select your project root. Explorer brings all its files into view.
Choose the root
Open the folder containing your project's source and configuration files.
Find your way around
Choose a file in Explorer, or press Ctrl + P to find it by name.
Start where you are
An existing project or an empty folder both work. GitHub can come later.
CONNECT A MODEL
Connect your AI provider
Open View → AI Assistant, or press Ctrl + J. Select the settings gear to connect a provider.
- Choose a providerSelect the provider you want to use in the Provider menu.
- Add your API keyPaste the key into the API Key field and select Save.
- Pick your modelType
/modelin the conversation to choose a provider or model.
AI features require Lamied Pro access and a configured provider. Your provider's usage charges are separate.
Prefer a local model?
Start a model server with an OpenAI-compatible API. Choose Local Model, enter its Base URL, and select Save. The example in the app is http://localhost:11434/v1; use your server's actual address. Choose the model with /model.
Local chat does not make sign-in, remote embeddings, or other connected features work offline.
Lamied, your provider, and GitHub accounts
Lamied sign-in manages your app access. Provider credentials connect the model. GitHub sign-in connects repository publishing. Setting up one does not configure the others. If the assistant is locked, follow the sign-in and access controls in the app.
FIRST TASK
Ask about the project first
Let the assistant help you understand the project before making a change. Copy this prompt into the AI chat and select Send.
Explain where this app starts, how to run it locally, and which tests already exist. Point me to the relevant files. Do not change any files.Turn on Plan Mode. The assistant proposes its approach and waits for approval before editing files or running commands.
Starting from an empty folder?
Turn on Plan Mode, then start here:
Help me plan a small app in this empty folder. Ask me what I want to build and which language or framework to use. Do not create files or run commands until I approve the plan.Try a focused code change
Find an existing input-validation function and add a test for an empty input. Preserve its current behavior and run the relevant tests. If there is no test setup, explain the options before editing.Follow the work in the conversation. A new message adds instructions. Use Stop or /stop to stop a task, or press Escape while the chat input is focused.
REVIEW
Review the change
Open a changed-file summary to read its diff. Green lines are additions; red lines are deletions. Then run the checks that matter for your project.
Read the code diff
In normal mode, edits can already be applied. Line counts describe the edit; they do not mean tests passed.
PUBLISH
Commit and publish to GitHub
Keep working locally, or connect GitHub when you're ready to share. Open View → Source Control to get started.
Publish a new repository
Lamied creates the repository and pushes your code.
- Choose Sign in with GitHub. Enter the device code on the page opened in your browser and approve access.
- Select Publish to GitHub, enter a repository name, and choose its visibility.
- Follow the publishing progress, then open your repository link.
Already have a remote?
- 1StageChoose your changes
- 2CommitRecord them locally
- 3PushSend them to GitHub
Where do GitHub Actions fit?
Ask the assistant to create or edit a workflow in .github/workflows/. Review it, commit, and push. GitHub runs matching workflows; find their results in the repository's Actions tab.
FEATURE REFERENCE
Where each tool lives
Find a tool, see where it lives, and learn what to do next.
Files & search
Explorer shows your project's folders and files. Search finds text across the open workspace.
- Open your project with File → Open Folder.
- Choose a file in Explorer to edit it, or use Ctrl+P to find a file by name.
- Use Ctrl+Shift+F to search across files. Save edits with Ctrl+S.
A workspace is the folder you opened. Choose the project root so related files are available together.
MORE TOOLS
Indexing, Task Workspaces, Scenario Lab and charts
Codebase IndexingFind relevant project context
Open AI settings → Codebase Indexing, configure embedding credentials, and select Index Workspace. The Voyage AI key is separate from your chat provider key. Review these settings before indexing confidential code.
Task WorkspacesSave a focused handoff
Open View → Task Workspaces → New task. Capture the objective, selected saved files, setup notes, and acceptance criteria. Export a bundle to share it. Importing does not automatically apply files or run code.
Scenario LabExplore your app's edge cases
Start your local development server, then open View → Scenario Lab. Set a local URL, synthetic API responses, and an expected page state. Adjust the viewport and locale to reproduce different conditions.
Visual explanationsTurn an idea into a chart
Ask the assistant: “Plot linear and quadratic growth for input sizes from 1 to 100, and explain the difference.” Interact with the chart in the conversation to inspect its values.
TROUBLESHOOTING
Common questions
I am signed in, but the AI panel is locked.
Confirm your Lamied account has Pro access, then configure the provider in AI settings. GitHub sign-in and a provider API key do not unlock Lamied Pro by themselves.
The assistant cannot see my files.
Use File → Open Folder to open the project root. Check Explorer, save your edits, and include the relevant filename in your request.
Why am I being asked for command approval?
Plan approval does not grant shell command permission. Read each requested command before approving it. Remembered command permission is a separate workspace setting in the AI panel.
My GitHub sign-in expired. How do I reconnect?
Use the GitHub icon in Source Control and complete a new browser approval. You can also sign out from that control. GitHub authorization is separate from your Lamied account and browser session.
NEXT STEPS
Read the docs
for each feature.
The docs cover the assistant, slash commands, complexity and network analysis, source control and troubleshooting.