Tutorial

Your first issue → merged PR

In about ten minutes you'll install Moa, connect it to a repo, and watch it take a real GitHub issue all the way to a merged pull request — with you keeping the merge button.

By the end you'll have a green PR opened by Moa and merged on your say-so. Pick a small, well-scoped issue in a repo you can write to — a typo fix or a one-function change is perfect for a first run.

Note.You need a GitHub account and Node 18+. Onboarding happens in the dashboard first; the CLI comes after. For the full setup path and the access Moa needs, see Setup & authentication.

Steps#

Onboard in the dashboard

Open app.fnmoa.com and sign in with GitHub. Complete the setup wizard — connect your workspace and GitHub identity, install the GitHub App and allow the repo you'll use, and connect Claude. (Members only connect their identity; the owner sets the rest.)

Create an API key

In the dashboard, open Keys → New key, name it, keep the task scope, and create it. Copy the key now — it's shown only once.

Connect the CLI

Install the CLI and store the key. moa login prompts for your workspace API URL and the key you just copied.

bash

npm i -g @fnmoa/cli
moa login

Confirm everything is connected:

bash

moa status

operator   you@org · workspace api.fnmoa.com
claude     connected
github     connected · 4 repos

Solve an issue

Point Moa at a repo and an issue number, and add --watch to stream the live step timeline to your terminal. Replace the slug and number with your own.

bash

moa wf solve your-org/your-repo 7 --watch

You'll see the run move through its steps — each one a visible result, not a black box:

text

run wf_8c21 · issue→PR · your-org/your-repo#7
✓ branch     moa/issue-7
✓ agent      wrote the fix — reasoned, never ran git
✓ verify     typecheck · lint · build
✓ open-pr    #12 ready for review
done in 1m48s · $0.06

Tip.The agent writes the code; the harness creates the branch, runs the verify-gate, and opens the PR. If the verify-gate fails, the run stops before a PR is ever opened — you won't get a red branch.

Review and merge

Open the PR link from the output. It's a normal pull request — diff, checks, description. When CI is green and you're happy, either click merge yourself or let Moa do it once it's approved and green:

bash

moa wf merge your-org/your-repo 12

That's the whole loop: an open issue became a reviewed, merged PR, and you stayed in the chair for the decision that matters.

What you just did#

Installed the CLI and connected it to a workspace.
Ran the issue→PR workflow — the agent reasoned, the harness did every git action.
Merged on your terms, with a passing verify-gate behind it.

Next.Explore the other five workflows in Workflows, see every command in the CLI reference, or read How Moa works to understand the determinism split and the memory graph.