MemoireMemoire
Start→
5-minute path

Quickstart

From nothing to a Memi-shipped PR in five minutes. Three real steps: install Memi in Slack, give it a coding-agent key, ask it to do something.

1. Add Memi to your Slack workspace

Memi connects via Slack's standard OAuth flow and Socket Mode, so nothing on your network has to change. The bot auto-joins all public channels once installed.

Add to Slack
OAuth flow lives in your Memoire dashboard
→
Create a Memoire account
14-day trial · no card required for signup
→

2. Connect a coding agent

Memi spawns Claude Code or Codex as a subprocess to do the actual code writing — but it uses yourcredentials, not Memoire's. That keeps inference costs on your account where you already have a budget, and lets you pick the model.

From the dashboard:

  1. Go to Coding Agents.
  2. Click Connect on either Claude or Codex. OAuth flow handles the rest.
  3. Or paste a raw API key — it's encrypted at rest and only decrypted inside the spawned subprocess.

Tip: a Pro plan Anthropic OAuth subscription works just as well as an API key, and won't show up as a separate line item.

3. Ask Memi to do something

In any Slack channel where Memi is, post:

@memi add a /healthz route to apps/web that returns 200 with {ok:true}

What happens next:

  • Memi reacts with 👀 within ~2 seconds.
  • It posts a quick plan in the thread, then either ships immediately or waits for your approval, depending on the task complexity and your org settings.
  • When the code is done, Memi pushes a branch, opens a PR, and records a short demo video showing the new behaviour running in a sandbox.
  • Final reply has the PR link, the demo, and a short summary.

4. Watch it work

While Memi is running you can keep talking to it. Reply in the same thread to:

  • Steer mid-task: "actually use TypeScript not JavaScript" — Memi picks it up before the next subroutine.
  • Pause: !pause stops at the next safe boundary; !resume continues.
  • Bail: EXIT halts the run and tells you where it stopped.

5. (Optional) Verify gateway health

For monitoring or red-team review, the gateway exposes two public endpoints:

# Quick liveness + version
curl https://api.trymemoire.com/readyz | jq

# Full diagnostics + recent events
curl 'https://api.trymemoire.com/diagnostics?limit=20' | jq

Or use the in-product status page at /dashboard/status for a visual version of the same data.

What's next