Using the AI assistant

The AI assistant reads your project, answers questions, and makes changes: it edits files, runs commands and tests, starts your app and checks it works. It needs Lamied Pro (see Account and sign-in).

Open the assistant

Press CtrlJ, click the ✦ icon in the activity bar, or choose View → AI Assistant. Open a folder first (File → Open Folder) so the assistant can see your project.

If the panel shows a lock, either you're signed out (click Sign in) or your account doesn't have Pro yet (click Unlock Pro, or redeem a promo code).

Then choose the model the assistant uses. There is no default: add your API key for a provider in ⚙ settings and pick the model with /model. See Models and providers.

Ask

Type in the box at the bottom (“Ask Lamied about your code…”) and press Enter. ShiftEnter adds a new line. Good requests say what you want and how you'll know it's done:

• “Explain where this app starts and how to run it. Don't change anything.”
• “Add a test for an empty title in src/tasks.ts and run the tests.”
• “There's some issue in this app, please fix it.”
• “Plot linear and quadratic growth for inputs 1 to 100 and explain the difference.”

Mention files by name (tasks.ts) or path (src/tasks.ts). File names in the conversation become links: click one to open the file. Type / for commands like /model and /undo. See Slash commands.

What the assistant already knows

• The file you have open and where your cursor is.
• The errors and warnings the editor shows, including in changed files you've closed, when language servers are on (Extensions and language servers).
• Your project's rules in LAMIED.md or AGENTS.md (Project rules).
• It can search the whole project by symbol, text and meaning (Codebase indexing).

When you report a problem without details, it starts from real evidence (editor errors, recent changes, the project's own type check, tests and build) before changing anything. If everything passes, it asks you what goes wrong.

Follow the work

While a task runs, the chat shows what's happening:

• A live summary line, for example Editing 2 files, explored 6 files, 3 searches +30 −16.
• Reading and searching fold into one Exploring… group. Click it to see each step.
• The model's thinking, as plain text, when the model provides it.
• Each command it runs, with its output streaming live.
• Each file edit, with its diff.

When the assistant starts your app, for example npm run dev or mvn spring-boot:run, Lamied notices once it is ready and keeps it running in the background. The command's row shows the address, such as Running in the background at http://localhost:8080, and the app stays up after the task ends. Ask the assistant to stop it when you're done, or close the window.

Steer or stop

Review the result

• Under the answer: Copy (copies the answer) and when it was written.
• An N Files Changed card lists every file with its +/− line counts. Click a file to open it, or Review to see every diff.
• Code blocks in answers can be inserted at your cursor in the editor.
• Once the assistant has changed files, a Changes +A −D bar appears above the message box. Click it to open Source Control, where you review, stage and commit. The assistant never commits for you.
• A final line reports what the task cost, for example Tokens this task: 12k in (9.1k from cache, 76%) · 1.2k out · 4 model calls.

Questions from the assistant

Sometimes the assistant needs you: to approve a command, confirm a file deletion, approve a plan, or answer a question. These appear as cards in the chat. See Plan Mode and approvals.

Bigger tasks

For broad work the assistant can hand parts to helper agents. Research agents read and search in parallel (for example, one each for auth, billing and sync) and report back. A worktree agent implements a change on its own Git branch, lamied/…, in a separate copy of your repository. Your working files stay untouched until you merge it. Every command a worktree agent runs asks for your approval.