Four AI engineers who plan, build, review and ship your software. Meg answers the phone. Call with a fix, a review or a website, and next time, they remember where you left off.
Open Loam beside your editor and the whole project is there: the four people you work with, the session you are in, the plan you are building against, and what the team remembers. Start a session, follow a build, read a member’s story, make a call.
The 5.5.0 workspace, captured before an account was connected. Readings that have nothing to report say Unavailable. Open the full-size image.
The work has a place.
Start a session. Follow the plan in Build Mode. Reviews, debugging, recordings and settings are each a page away instead of a stack of panels.
The team is in the room.
Read a member’s story, see how the week has gone for them, email or call any of them, or Call the Shop for the whole team at once.
Nothing on the screen is invented.
States come from the notes each member wrote. Counts come from your record. Server readings say when they were taken. Anything not reported says Unavailable.
Loam is a working software team inside VS Code and on the phone. Give it an idea, a codebase, a broken build, or a production target. The team scopes the work, executes it, checks it, and returns the evidence.
01 / PLAN & BUILD
Turn the rough brief into working software.
Development meetings expose the hard questions, produce a scoped plan, and hand that plan into stateful, multi-session Build Mode.
Planning meetings
Scoped specs
Build Mode
Stateful Git
02 / REVIEW & CORRECT
Run a cold review with a finding ledger.
Findings enter a durable ledger, remediation assigns each one a terminal state, and later audits can challenge those decisions without re-deriving the original issue.
Codebase review
Remediation
Audit ledgers
PDF reports
03 / SHIP & OPERATE
Move from repository to a live system.
For authorized repositories, the team can commit, push, and publish to your own server through steps you approve once. For Loam-managed hosting, Loam administrators set up the server, DNS and SSL. Either way, the team inspects the result and monitors what it shipped. Publishing to your own server is available now; see what Loam can do today.
AWS Lightsail
Cloudflare DNS
SSL & deploy
Visual QA
04 / CALL & COORDINATE
Call the front desk. Get the work.
Meg verifies you, listens, and reads back what you will get. Order a review of your application, a dev meeting, a document, a deck, a spreadsheet, or a website. Finished work arrives in your inbox; a dev meeting includes a walkthrough call.
Send photos during the call, amend delivered work, or email the team instead. Code changes by phone are available: a verified caller confirms the change, the team makes it on the project connected through GitHub, and it goes online through the steps you approved for your own server or, if your project already publishes itself from GitHub, through that. Saved and live are reported separately. See what Loam can do today. See what you can order →
Phone & email orders
Photos on the call
Delivered files & sites
Walkthrough calls
Also in the system: project documents and frameworks, scheduled meetings and calendar invitations, email and SMS follow-up, site monitoring, and browser-based quality review. Read the one-page overview.
A real session
One sentence in. A working plan out.
The brief is one line: a mobile app for job-site photos. In four minutes the team surfaces the hard questions, defines the scope, records the risks, and makes the call.
Live Loam output / no scripted response
Continuity
The record moves with the work.
Memory is part of the mechanism, not the pitch. Loam carries the decisions, corrections, open work, review outcomes, and evidence that let the team resume accurately and stay accountable.
01 / LOAD
Start from current state.
The session opens with verified identity, durable lessons, prior decisions, open work, and a bounded recent window.
02 / WORK
Use the record through a role.
Carl tests the architecture. Diana protects the interface. Anthony builds. Abish handles bounded execution and keeps the lessons.
03 / RETURN
Write the outcome back.
Decisions, fixes, rejected findings, blockers, and proof become part of the next session instead of disappearing with this one.
The retained-work loop
The raw record stays intact. Each new session gets the bounded working set it needs, with older detail available through recall. See the full platform workflow →Read this diagram as text
Work creates decisions, corrections, preferences, and outcomes. New lessons are saved, indexed, and retained. The next session loads identity, durable lessons, current state, and a bounded recent window. Older detail remains searchable on demand.
Four working styles
Different judgment. One engineering record.
The four are not fictional résumés or human employees. They are stable AI working contexts: recognizable collaborators with different responsibilities, instincts, and ways of challenging the work.
Loam publishes implementation evidence, redacted workflow artifacts, data boundaries, provider disclosures, deletion controls, and the limitations that are still roadmap work.
Evidence you can read.
The proof pages connect product claims to architecture, code excerpts, review ledgers, memory records, and production patterns. Internal case results are labeled as internal evidence, not universal benchmarks.
Loam is onboarding builders and pilot teams deliberately. We will help you evaluate the workflow, the boundaries, and the fit before you put it near production work.
