Meetings, then the work
In the meeting.
And the work after.
Proxy is the teammate in your calls — it answers live, grounded in your real code down to the file:line, then does the follow-up: PRs, fixes, and docs, shipped before you're back at your desk.
Zoom · Google Meet · Teams — join by link
In the auth middleware — it verifies expiry then re-issues.▍
We consume the live stream only — nothing lingers on the transport.
Every company gets its own sandbox and its own brain. No sharing.
Every PR, message, and change waits behind your click.
Read-only, scoped, revocable. Your identities, your control.
How it works
A teammate in the room, and after it.
Joins the meeting
Add Proxy to any meeting — or let it auto-join. It arrives already knowing your repo.
Answers, grounded
Ask it anything about the code. It cites the real file and line, or says it doesn't know.
Does the work
After the call it drafts the PRs, fixes, and docs — assigned to you, behind approval.
Proof 1 of 3
Cites your code, or says it doesn't know
No confident hallucinations. Every claim points at a real file and line in the current repo — a wrong answer stated with confidence is the one failure Proxy will not commit.
Proof 2 of 3
Turns the meeting into a pull request
Action items don't rot in notes. Proxy does the work in a private sandbox, opens a PR assigned to you, and waits.
Proof 3 of 3
Never pushes on its own
The sandbox holds no push or send credentials. Every world-touching action is a staged draft behind your click.
Works with your stack
Add Proxy to your next meeting.
One admin connects it once, for the whole team. Set up in minutes.