The AI development team that doesn't forget.
Four teammates plan, build, review and ship your project inside VS Code, and remember it the next time you open it.
What it's like
Open Loam and the project is there. The people you work with, the session you're in, the plan you're building against and what the team remembers, in one window beside your editor. Pick up where you left off.
Hand work to the team, get evidence back. Ask for a plan, a build, a review or a fix. The work comes back with the checks that prove it, and a fix is carried through only when the approved scope includes implementation.
Call the front desk. Meg answers the phone. Order a review, research or a document by phone, and it lands in your inbox. Small repairs by phone are available.
The team
| Carl |
Diana |
Anthony |
Abish |
Meg |
 |
 |
 |
 |
 |
Carl — Principal Architect.
Sets the plan and keeps scope and risk in view. |
Diana — Lead Designer.
Owns how it looks, reads and works on every screen. |
Anthony — Senior Developer.
Turns the plan into working code and sees failures through. |
Abish — Junior Engineer.
Checks every claim against the source before anything ships. |
Meg — Front Desk.
She answers “Loam, front desk — this is Meg,” verifies callers and gets your request to the right person. |
How it works
- Install Loam from the Marketplace. The first run walks you through the rest.
- Connect your Loam account on the Settings page in Open Loam.
- Open a project and choose Work.
- Start Session. Pick the kind of work, and the team takes it from there.
Codex, when you want it
Collaboration is off until you turn it on. Updating this extension does not install Codex, does not start anything in the background and does not hand over any work. When you connect it, Loam writes each task with its context and limits, then reviews what comes back. Connecting and handing over work are two separate choices. Letting Codex pick up follow-on work inside a plan you already approved is a third, and you turn it on yourself.
Pricing
The Marketplace extension is free to install. The Loam service is USD $499 per user per month. Your own provider accounts, such as your Claude Code/Anthropic account, are separate and billed by those providers.
Good to know
- Who they are. Carl, Diana, Anthony, Abish, and Meg are AI working contexts with synthesized identities, voices, and images; they are not people or human employees, and their profiles are not fictional resumes.
- What the team remembers. Learning-active sessions can save selected, source-tagged decisions, corrections, findings, and open work without treating every conversation as durable memory. Later sessions receive a prioritized working set and can recall older indexed detail. Not every session writes memory, and not every stored item enters every prompt.
- Build Mode. Build Mode advances the milestone plan the user starts, and when the GitHub App is configured and the project has a linked repository, each completed milestone pushes the project's stored files to that repository's main branch without a separate prompt. It does not open a pull request. Turning Build Mode off lets the current milestone finish and stops everything after it.
- Permission. Authorization happens up front, not per action, and provisioning servers and setting up deployment are performed by Loam administrators.
- By phone. A phone call is not authorization to change code. For a small repair, a verified caller can confirm one specific, bounded change to a registered project that Loam can write to and publish. Loam saves the change, the project's own pipeline puts it live, and you are told those two things separately, because they are two different facts.
- Your data. There is no default repository scan, and Workspace Indexing is opt-in and off by default. Stored text and credentials are field-encrypted at rest; phone-call transcripts are stored as plaintext for memory synthesis. Setup installs two local, user-space components, the VS Code extension and the Loam MCP server; hosted account, memory, and audio services are service surfaces, not local modules.
- Deleting. Self-service controls can remove one role's memory, a project, or the live database records tied to an account. Server-stored generated audio requires Loam-operated cleanup, and disaster-recovery snapshots may retain deleted database data during the published backup window. The Codex helper's history stays on your machine and is not erased when you disconnect or when a hosted account is deleted.
Install and links
Search for docpro.docpro-app in VS Code Extensions. The docpro publisher ID is intentionally retained so existing installations continue to update.
Getting started · Releases · For IT · Security · Privacy · The proof · Proof packet · Built on Claude Code
| |
