Lamied 0.4.0
Conversations are saved. Each conversation is written to your computer as it happens, so closing Lamied, a crash or a power cut doesn't lose it, and opening a folder again brings back the conversation you had open there. /resume lists the folder's other conversations, newest first. /fork continues a copy of the conversation, whole or up to one of your messages, so you can try another approach and keep the first.
Hooks. A project can run its own commands while the agent works: before it uses a tool, to block an action such as committing a secret; after it uses one, to lint every edit, say; and when it says the task is done, to send it back to work while tests still fail. Lamied asks before running a project's hooks for the first time, and again when they change. Hooks use Claude Code's format, and a project without .lamied/hooks.json uses those in .claude/settings.json, so hooks a team already has carry over. See Hooks.
Rules for each folder. A folder can have rules of its own, in a LAMIED.md, .lamied/rules.md or AGENTS.md inside it, so each package of a monorepo can say how it is built and tested. The agent reads them the first time it works in that folder. A project set up for Claude Code works as it is: where none of these files exists, Lamied reads CLAUDE.md.
Also in this release:
/initwrites anAGENTS.mdthat says how to build, test and work in the project./review [base]reviews the changes sinceHEADor a branch for bugs, risks and slower code.- Long conversations keep working. Lamied summarizes the start of a conversation once and reuses that summary, so a request stays the same size however long the conversation runs. Before, a very long conversation stopped accepting messages.
- A dropped connection no longer ends a task. The agent reconnects, up to four times over about 40 seconds, and sends the step again with the work already done kept.
- On the Team plan, agent tasks no longer fail when hosted requests are rate limited. They wait their turn, and the status line says for how long.
- Replies start sooner after a pause. Connections stay open for a minute: measured from Ethiopia, a request after 5 to 60 idle seconds reaches Lamied's server in about 0.3 s instead of 0.8 to 0.95 s.
- Agent tasks cost less, because more of each request is served from the provider's prompt cache. In simulated tasks of 25 to 80 steps, input cost fell by 35–62% on Claude and 15–40% on GPT-5-class models.
- Long file writes show their progress, such as "Writing src/app.ts (120 lines so far)…", instead of "Thinking…". MCP servers start while you type, and a task waits at most 5 seconds for one still starting, instead of 30.
- Closing a file never loses unsaved changes. With autosave on, the file is saved first; otherwise Lamied asks whether to save, discard or cancel.
- A model that wrongly says it has no tools is sent back to work, and its refusal is taken out of the chat. After three refusals in a row, the task stops and says why.
- With a Voyage key, semantic search uses Voyage's
voyage-4-litemodel. Each workspace is indexed again once, the first time this version opens it. - A paid account no longer reads as Free when two status checks overlap.