Help & Support

Mo (short for Motionode) is an AI-powered decision enforcement platform. When your team agrees on something — a product rule, a technical constraint, a business requirement — Mo captures it as a “decision” and automatically checks that it’s reflected in your code before any pull request or merge request is merged.

Code linters enforce syntax rules and style conventions. Mo enforces your team’s actual agreements. A linter can’t tell you whether the trial period was implemented as 14 days like your team decided — Mo can. Mo reads your decisions and compares them against the actual code diff, catching semantic violations that static analysis tools miss.

Mo reads PR/MR diffs to evaluate decisions and does not clone full repositories. The system stores check metadata and findings (for example file paths, line ranges, and short diff excerpts used in the result view). It does not persist a full copy of your codebase.

Mo is fully language-agnostic. It works on any codebase — JavaScript, TypeScript, Python, Go, Rust, Java, C#, Ruby, PHP, and more. Because Mo reasons about what your decisions mean in context of the diff, it doesn’t need language-specific parsers.

No. You need at least one code host (GitHub, GitLab, or Bitbucket) and at least one decision source (Slack, Teams, Jira, Azure DevOps, Linear, Basecamp, Asana, monday.com, or manual entry). All other integrations are optional and add richer context to your verdicts.

Yes. Slack is one of several ways to feed decisions into Mo. You can use Microsoft Teams, add decisions manually from the Decisions page, capture them from Jira, Azure DevOps, Linear, Basecamp, Asana, or monday.com, or extract them from uploaded documents — all without Slack.

A decision is any agreement your team reaches about how the product or system should behave. Examples: “The trial period must be 14 days,” “User passwords must be hashed with bcrypt,” “The API response time must be under 200 ms,” “The checkout button must be green.” Decisions can be product rules, technical constraints, UX requirements, or business policies.

Yes. Go to the Decisions page, find the decision, and open it. You can edit the title, description, and linked issues. Changes are reflected in future PR checks immediately. Editing a decision does not affect already-completed check results.

When a new decision contradicts or replaces an existing one (e.g., changing the trial from 30 days to 14 days), Mo marks the old decision as “superseded” and the new one becomes the active rule. Both remain visible in the History view so you have a full audit trail.

Approved decisions are active rules — Mo enforces them in every PR check. Pending decisions have been captured but not yet reviewed or confirmed. Rejected decisions have been explicitly dismissed. Only approved decisions affect PR verdicts.

There is no hard limit on the number of decisions per project. Mo handles large decision sets efficiently. That said, keeping decisions focused and well-described produces more accurate verdicts than having many vague or overlapping rules.

Yes. From the Decisions page, click + Add Decision. Write the title and description directly. You can optionally link it to an issue key from any connected integration. Manual decisions are fully supported and enforced exactly like decisions created from Slack, Microsoft Teams, issue trackers, Linear, Basecamp, Asana, or monday.com.

The most common causes: (1) The code in the PR contradicts an approved decision — for example, a constant is set to a different value than what was agreed. (2) A required implementation is missing from the diff. (3) A configuration value doesn’t match what was decided. Read the Mo comment on the PR for a specific explanation of each conflict.

Usually under 30 seconds for most PRs. Larger diffs or projects with many decisions may take up to 60 seconds. Mo posts its result to the PR as soon as the check is complete.

Mo triggers a new check whenever a PR or MR is opened, reopened, or updated with new commits. Each push to an open PR triggers a fresh check so you always see the latest verdict.

Yes. From the Checks page in this portal, you can mark a specific check as overridden. This lets the PR be merged even if Mo flagged a conflict, and logs who approved the override and why. Overrides are tracked for accountability.

“Conflict” means Mo found code that directly contradicts an approved decision. “Review” means Mo found something worth a human look but isn’t certain it’s a violation — often because the decision is high-level or the diff is ambiguous. “Pass” means the diff aligns with all decisions.

Yes. From Integrations → GitHub, GitLab, or Bitbucket, you can select exactly which repositories Mo should monitor. You can add or remove repositories at any time without re-connecting the integration.

First, verify that your Slack integration is connected: go to Integrations → Slack and check the status. Second, make sure you’ve invited Mo to the channel by typing /invite @Mo in that channel. Mo must be a member of the channel to read messages and respond. Third, check that you’re mentioning @Mo (not @mo lowercase — both should work, but try the exact username you see after installation).

Mo can capture from either a thread or regular channel flow, but it needs enough context to infer a decision. Include an explicit capture phrase (for example @mo approve this, @mo update this, @mo store this, @mo lock this — many verbs work the same way), ensure the bot is in the channel, and add a little surrounding discussion or context when possible. Threads are recommended because they usually give cleaner context.

Yes. Any team member with access to the channel and the Mo project can use a capture phrase (@mo approve this, @mo update this, @mo store this, and the other verbs in Help). Mo tracks who captured each decision (the person who typed the command) and links back to the thread.

Mo deduplicates repeated captures. If the new approval resolves to the same decision title as an existing approved decision, Mo skips creating a duplicate. If the new approval represents a changed rule or value, Mo can create a new decision and supersede the older one.

Confirm Integrations → Teams shows as connected (the Mo portal flips to Connected automatically once the bot receives its first activity from your tenant). Make sure the Mo app is installed in the team and added to the specific channel. Finally, your @mention must include the decision text — e.g. “@Mo approve this: API errors must return JSON”. Unlike Slack, Mo does not read Teams channel history, so a bare “@mo approve this” will not capture anything.

The Mo Teams integration is a bot app; it does not require Microsoft 365 user consent or broad Graph permissions. Installation is done by your Teams admin uploading the Mo app package (.zip) from this portal to the Teams admin center. If your tenant disables custom app sideloading, ask your Teams admin to enable it for the Mo app or wait until Mo is listed in the Microsoft Teams Store (coming soon).

In Teams, Mo focuses on capturing decisions from channel conversation: use the same capture phrases as elsewhere (@mo approve this, @mo update this, @mo store this, @motionode, mo update, etc.). Commands such as undo, listing decisions, upload document links, and document rule approval are available in Slack or from this portal; use those surfaces until Teams parity expands.

Mo supports Jira Cloud only. On-premise (Jira Server or Jira Data Center) is not currently supported. Connecting Jira usually requires someone with admin access on your Atlassian site to approve Mo.

Not currently. Mo supports GitLab.com (cloud). Self-hosted GitLab Enterprise Edition integration is on the roadmap. Contact support if this is a blocker for your team.

Yes, as long as the connected GitHub identity or app installation can access those repositories. In Integrations, select the repos you want Mo to monitor. If your company keeps work split by separate permissions or teams, using separate Mo projects can still be the cleanest setup.

Your existing decisions are preserved. Disconnecting a source (e.g. Jira) means Mo will no longer fetch new issue context from that source, but all previously captured decisions remain active and are still enforced in PR checks. You can reconnect the integration at any time.

Yes — this is actually the recommended setup for maximum verdict accuracy. When a PR is opened on GitHub, Mo checks the diff against your decisions and pulls fresh context from the linked Jira issue (via the issue key in the branch name or PR title). The combined context produces richer, more accurate verdicts.

In Mo, open Integrations, choose the tool, disconnect, then connect again and accept the permissions—this fixes most issues after consent or passwords change. Make sure you are commenting or updating where Mo listens (for example an Asana task comment or a monday item update). If it still does not work, contact Motionode support with the tool name and roughly when you tried.

Mo records every capture in this portal. For Asana, Linear, monday.com, Basecamp, Jira, and Azure DevOps, Mo also tries to post a short acknowledgment on the same task or thread when your integration token has the right scopes (for Asana, comment and write access is requested on connect). If you connected before that was added, disconnect and connect again so Asana can grant comment permission. The reply quotes the captured decision title (the same title Mo saves). Slack and Microsoft Teams use their own reply channels. Always confirm captures on the Decisions page.

The free tier includes the core Mo workflow with usage limits that are enforced at the account level (shown on the Billing page). Current limits and trial state (for example decisions and checks available and days left, if trial started) are shown live in Billing, and Pro unlocks higher limits plus blocking enforcement.

A collaborator is any person (other than you) who can access a Mo project. Each collaborator requires a paid seat. You can manage collaborators from the Collaborators page in this portal. Removing a collaborator frees up their seat on your next billing cycle.

Yes. You can use Mo on the free tier before subscribing. In the Check portal billing flow, a free-trial window starts automatically after your first approved decision; Billing shows remaining days and limits in real time. Upgrading to Pro requires adding a payment method.