Call the software team.
Commission a review, work through a project, or let the team call when a milestone or blocker needs you. The same project record is already on the line.
By phone today: read-only codebase review, research, and document generation. Debugging and code changes by phone are planned, not shipped.
Commission a codebase review by phone.
Say what you need in plain words. Meg verifies the caller, captures the request as stated, and routes it into the engineering workflow. The finished review comes back as a PDF with the findings and source anchors.
The review is a cold, read-only pass over the authorized snapshot, delivered as a PDF with cited lines and a file list. Here is what happens to the working copy:
What happens to your code — and we show our work. We touch a repository only after you authorize it: a GitHub App you install, a project you register, reached with a short-lived, read-only credential that can't fetch twice. We take one point-in-time snapshot into a locked, isolated sandbox, review it read-only — never written back — and then the working copy is removed when the review finishes, fails, or is cancelled. The job cannot report done until removal is confirmed. We don't keep a copy of your codebase. What remains is the review report, including quoted lines and the list of files reviewed, scoped to your account. Individual work-order deletion is not currently available as a self-service control. Deleting your account deletes its work orders, intake records, and delivered report files. What Reception keeps, stage by stage.
No default repo scan, ever. We reach a codebase only through a GitHub App you install and a project you register — with a short-lived, read-only credential that can't fetch twice.
One sealed, point-in-time copy in an isolated sandbox — reviewed read-only, then removed when the run finishes, fails, or is cancelled.
The retained result is the report you commissioned and the list of files reviewed, scoped to your account. Individual work-order deletion is not a self-service control today; deleting your account deletes the report.
Planned next: phone-initiated debugging and autonomous coding. Those capabilities are roadmap items, not shipped features.
Meg runs intake. The engineering team does the engineering.
Full detail on what a review stores and how it is removed lives on Security.
Talk through the work with the team doing it.
Call the full team from the road or between meetings. They load the project record before the call, so the conversation can start with the decision in front of you.
Give them context the night before and they can arrive with the codebase, open questions, and prior decisions in view. Use the call to shape a feature, settle a fork, or work through what is blocked.
The relationship can carry personal context too, when you choose to share it. That context remains account-scoped and user-controlled.
A boundary first, because it matters: the team only remembers the personal context you choose to share through your sessions and calls, and that memory is account-scoped, user-controlled, and deletable.
A standing phone workflow for all four roles. Before the call, Loam prepares a prioritized working set from the available account and project record so the current decision can be discussed without loading the entire archive.
Feed them context the night before — study the app, come ready to talk through a new feature — and they pick up already in it, so the drive in becomes the meeting.
Project history and the personal context you choose to share can carry across calls. The record stays account-scoped and deletable.
The call starts with the current state, not a fresh explanation.
Conference calls, callbacks, and daily briefs.
A working session scoped to one project — the team loads that codebase and nothing else, and you can ask for anyone by name.
The team calls you when a moment earns it — a blocked build, a finished milestone, a fork only you can settle. Opt-in, per trigger.
A daily brief synthesized from the team's memory and read in four voices — in your inbox before the first coffee.
What voice calls and audio store, and how you delete it, is on Security.