Skip to main content
Start in the Monnet web app. For a new workspace, share product context to build your company brain, review a real idea, then turn it into a spec. Connect your team’s tools after you’ve seen the first review. For a shorter walkthrough, follow the Quickstart. You can also accept an email invitation, join from Slack or Teams, or start from your coding agent.
Two-factor authentication (2FA) is not required by default at sign-up. After sign-in, if you belong to, or have a pending invitation to, a workspace that requires it, the web app asks you to set up a second factor if needed, then verify it before continuing. This applies across the web app, including your other workspaces. See Two-factor authentication.

​
Start from the web app

A browser and a Monnet account are enough. Sign up or sign in at app.monnet.ai. If you need preview access, join the waitlist or book a demo. If you already belong to a workspace, open it from the sidebar or check your inbox. If you have a pending invitation, accept it rather than creating another workspace for the same team.

​
New organizer

This flow is for new workspaces. If you’re joining an existing team by invitation, keep following that invitation; you don’t need to create a workspace or repeat the brain-seeding step.
1

Welcome and create your workspace

Click Get started, then name the workspace after your company. Review its URL and optional logo, and click Create workspace.
2

Teach Monnet about your product

Review the suggested Public website and Product docs URLs. They are guessed from your email and workspace name, so edit or remove anything incorrect.Drag and drop files or click browse to add product context: priorities, a roadmap, a product overview, or user research. Multiple files are allowed. Uploaded files appear as chips above the drop zone; click a chip’s × to remove it. The page lists supported types and the per-file size limit, and explains any upload error.Add at least one link or file to enable Start learning. You cannot skip this step. Monnet does not use what you share to train AI.
3

Draft your first idea while Monnet learns

Click Start learning to open the Get started with Monnet thread. Monnet builds a basic company brain from your links and files, with progress shown in the chat.You can type an idea or paste a whole spec while it works. Submit stays disabled until the brain-building task finishes. Monnet sends a message when it’s ready, and you can then submit the idea.
4

Read the review and write a spec

Monnet reviews the idea against your product context and shows the review in the chat. Discuss anything you want to change. You can adjust how feature ideas are reviewed in the new-feature playbook.Click the Write spec suggestion to turn the thread into a draft motion. Monnet applies the new-feature PRD template and adds a simple plan with your approval step. Review the document and plan before deciding whether to Kick off.
5

Connect chat and issue-tracking tools

Monnet first offers Add Monnet to Slack or Add Monnet to Teams, then Add Monnet to Linear or Add Monnet to Jira.Connections happen directly from chat: click the button, complete the provider’s OAuth flow in a popup, and return to the chat. The button shows a success state when the connection completes. You can also tell Monnet to skip a connection and add it later in Settings → Integrations.

​
Seed the brain

The first review uses the context you’ve shared. Include material that explains what your product does, who uses it, and what matters now. Monnet organizes what it learns into your company brain, including company context, product areas, users, priorities, and other subjects supported by the sources. Review the brain’s pages and correct anything incomplete or wrong. Keep adding context as your product and priorities change; reviews improve as the brain learns more.

​
From the first review to a motion

The onboarding starts with a thread, so you can get a review before dealing with a document and plan. Clicking Write spec introduces those parts on an idea you already care about:
  • Chat: discuss the idea and ask Monnet to refine it.
  • Document: the brief or PRD you’re shaping together.
  • Plan: who needs to do what next, beginning with your approval.
  • Motion: the document, plan, and conversation that carry the work forward.
Your playbooks guide both reviews and coordination: who Monnet involves, when it follows up, and where approval is required. Kicking off the motion activates its plan. Connecting a chat app alone doesn’t ask Monnet to ping your team. With a tracker connected, Monnet can turn a spec into a Jira or Linear issue when you approve creating it. Connecting the tracker does not automatically publish every reviewed idea.

​
Invited by email

When a teammate invites you to their workspace, you receive an email with an invitation link.
  1. Open the link. It takes you to an invitation page for that workspace.
  2. Sign in (or sign up) with the email the invite was sent to. If you’re signed in with a different account, Monnet tells you and lets you switch — the invite only works for the address it was issued to.
  3. Accept to join the workspace, or Decline to dismiss the invitation.
Accepting drops you into the workspace as a member; you skip the workspace-creation steps entirely.

​
Invited from Slack or Teams

If your team has connected Slack or Microsoft Teams, Monnet can reach you in a DM before you ever have a Monnet account. The DM links to the motion that needs you. Following that link signs you up and runs a short channel-specific flow: a welcome, a confirmation that you want to join the workspace, and a final screen that takes you straight to the motion that prompted the invite. From there you’re a full member and can use Monnet directly, not just from the chat channel. If you decline, nothing is lost — you can still join later from a future link.

​
Start from your coding agent

This optional path is useful when you want Monnet to learn from a repository or work folder and set up product idea intake from Claude Code or Codex. You can use it after starting in the web app, too. You need Node.js 20 or newer and the Claude Code or Codex CLI installed and available in your terminal. Your organization must allow local plugin installs. You can sign up during the flow.

​
Install and restart

Run this in your terminal:
The installer adds Monnet’s tools and onboarding command to the supported coding agents on your machine. You can also find the install command in Settings → Monnet MCP in Monnet. Quit your coding agent completely and reopen it. Starting a new session inside the running app does not activate the installation. Open the repository or work folder you want Monnet to learn from, then run the command for your agent:

​
What the guided setup does

The setup first checks what is already in your Monnet account, so it does not repeat completed work:
  1. It first checks for workspaces you already belong to and work waiting in your inbox.
  2. If the coding agent is not connected yet, it opens Monnet in your browser and shows a short code in the terminal. Sign in or sign up, then enter that exact code on the page that opened.
  3. If you need a workspace, it asks you to approve its name before creating it. If that name is already in use, it helps you check whether you should join the existing workspace instead.
  4. In a new workspace, it shows you the starter playbook for product ideas. Its initial plan names the workspace admin and asks them to approve the scope. You can adjust the playbook before it is saved.
  5. It drafts the initial company brain pages for your review: a complete profile page about you, the workspace page, and one page for each product you own.
  6. It connects the Slack or Teams workspace your team uses, then sets up a recurring check of motions that need your input every weekday at 8 a.m. If your coding agent cannot schedule recurring work, it tells you.
  7. It identifies one coworker close to the workflow and gives you a short message asking them to send their next product idea to Monnet. The instructions tell them where to send it and tell you where it will appear.
If you already belong to a workspace, setup leaves its existing onboarding and work intact. It takes you to relevant work in your inbox instead of creating another workspace or replacing its playbooks.
The short code is what authorizes the connection. It is only shown in the terminal that requested it. Enter your own code, never one sent to you by someone else.
If setup is interrupted, run the command again. It checks your current account and workspace before continuing, so completed work is not repeated. If the command or Monnet tools are missing, quit the coding agent completely and reopen it. If the installer could not find your agent’s CLI, make it available in your terminal and run the installer again. The first test involves one coworker, not a team rollout. You can invite more teammates later from Settings → Team or the Invite members action in your avatar menu. To let Monnet carry out assigned work on your machine, follow the separate Local Runner setup.

​
After onboarding

After your first review, you can keep refining the spec or start another idea from New. Return to an unfinished thread or draft motion from Drafts, Recents, or search. Future sign-ins take you to your inbox after any required 2FA verification. Invite teammates later from Settings → Team and manage connections from Settings → Integrations. Joining an existing workspace by invitation keeps its existing onboarding flow.