What Loam does, in one page.
A scoped request becomes reviewed work. The decisions, findings, and open work then carry into the next session.
Four kinds of engineering judgment.
Each AI collaborator has a stable job, review pressure, and role-specific record. They work from the same current state and challenge the work from different angles.
Tests assumptions against source, keeps technical decisions legible, and asks for evidence before work advances.
Protects hierarchy, accessibility, spacing, and consistency, and holds work that has not been verified in the browser.
Turns a scoped plan into working code, explains trade-offs, and owns failures instead of talking past them.
Maps blast radius, checks claims against source, runs the verification gate, and records lessons for the next pass.
How memory actually works.
Learning-active sessions can add selected, source-tagged decisions, corrections, findings, and open work to the account-scoped record. A later session does not reload that record wholesale — it assembles a prioritized working set, while older entries remain available through recall.
Each specialist has their own memory store, scoped to their role. Carl’s memory is architectural — infrastructure decisions, hard-learned lessons, system relationships. Diana’s is visual — your design system, component patterns, spacing preferences. Anthony’s is practical — your codebase patterns, past bugs, what you’re currently building. Abish archives QA outcomes and blast radius maps.
You can clear a specialist’s memory in full, delete a project, or delete the live database records tied to the account. See Security for the file, backup, and infrastructure boundaries.
Autonomous delivery, not a longer prompt.
Build Mode is not a prompt that tells the team to work harder. It’s a structured loop where Anthony builds, Abish reviews, Carl approves or redirects, and the team iterates until the milestone is done — across multiple sessions if needed.
AWS provisioning from the sidebar.
For supported hosted projects, Loam can provision a Lightsail instance, static IP, firewall rules, Cloudflare DNS, and an SSL certificate without leaving VS Code.
You can call the team.
One click in the Loam sidebar opens a synthesized-voice session with Carl, Diana, Anthony, and Abish. The call loads the relevant account-scoped project record before the conversation begins.
Meet the Team is the broad working-room call. Conference Call scopes the conversation to one project. Reception handles verified inbound intake.
Three steps and you have a team.
Install the MCP server, install the VS Code extension, open a project. The team is briefed and ready. The context starts accumulating from the first session.