Projects

Projects live in the Command Center sidebar. Each repo you work on is a project group there, with its missions listed underneath. There is no separate Projects page: the old /spaces and /projects/repositories URLs redirect to Command Center.

Mental modelCopy Anchor Link

• A repo is the imported GitHub repository Mogplex knows about.
• A project is a repo as it appears in the Command Center sidebar, with its missions grouped under it.
• A sandbox is the runtime and preview environment attached to that repo work.
• A worktree is a separate task checkout inside selected Sandbox compute. Starting the Sandbox does not create one.

Start work on a repoCopy Anchor Link

Open Command Center and pick the repo in the composer's project picker. New project… is pinned at the top of the picker and creates a fresh GitHub repository. If the repo does not have a running sandbox yet, Mogplex launches one when the mission starts.

Project settingsCopy Anchor Link

Open the ⋯ menu on a project in the sidebar:

• Environment variables opens the Project settings drawer on its environment variables tab.
• Project settings opens the same drawer on General.

The drawer has these tabs.

Environment variablesCopy Anchor Link

A key/value table for the repo's sandbox variables. Values are masked; use the eye button to show one. Paste .env imports KEY=value lines: existing keys take the pasted value and new keys are added. Variable scope applies to every variable in the repo:

• Sandbox only: the sandbox gets exactly the variables in the table.
• Sandbox + preview conventions: the sandbox also gets Vercel-style preview defaults such as VERCEL_ENV=preview and NEXT_PUBLIC_APP_URL set to the preview URL. A variable in the table always wins over a default.

Unsaved edits stay in the drawer while you switch tabs. Select Save variables to store them.

GeneralCopy Anchor Link

The runtime shape for the repo: runtime, sandbox billing, root directory for monorepos or sub-projects, install command, dev command, and dev port.

GitHub Secrets, Skills, Rules, Models, SnapshotCopy Anchor Link

• GitHub Secrets: GitHub secret configuration managed alongside the repo.
• Skills and Rules: repo-level skills and rules for agent runs.
• Models: repo-specific exclusions from the globally enabled model set.
• Snapshot: the snapshot state Mogplex uses for sandbox work.

Repository settingsCopy Anchor Link

Settings → Repositories holds the account-wide repo controls:

• Sync GitHub to pull in newly accessible repositories
• search and filter connected repositories by owner
• remove a repository from Mogplex lists, or remove all repositories from one owner
• Show removed to restore a repository you removed earlier
• a link to Sandboxes for cross-repo sandbox management

Removing a repository hides it; it does not touch the GitHub repo, and you can restore it at any time.

A practical first workflowCopy Anchor Link

1. Connect GitHub in Settings.
2. Confirm the right user or org has Mogplex GitHub App coverage in Installations.
3. Open Settings → Repositories and select Sync GitHub if the repo is new.
4. In Command Center, pick the repo in the project picker.
5. Open Project settings from the project's ⋯ menu if you need to set environment variables, a root directory, dev command, or dev port before boot.
6. Start the mission. If no sandbox is running yet, Mogplex launches it.

MonoreposCopy Anchor Link

If a repo has multiple app or package entrypoints, Mogplex picks a web app workspace automatically when it can. If it picks the wrong one, set the root directory in the General tab so preview commands and sandbox settings match the app you want to run.

Sandbox managementCopy Anchor Link

Use Sandboxes when you need a cross-repo operational view of running or pending previews, or when you want manual override on a specific sandbox.

Use Control Execution Environments when you need to choose between Sandbox compute and a task Worktree.

Failure modes that matterCopy Anchor Link

• Repo is visible but trigger-backed features do not work: GitHub OAuth is connected, but the correct GitHub App installation is missing.
• The first mission on a repo feels slow: the repo probably needs its sandbox created or installed first.
• Sandbox launch says access is unavailable: the account plan may not include managed sandbox access yet.
• Preview opens the wrong app in a monorepo: set the root directory, dev command, and dev port in the General tab.
• Creating a new repository fails: an organization owner must accept the GitHub App's Repository creation permission. A personal account needs the App installed and Authorize GitHub once. See Repository creation.
• A repo disappeared from the project picker: it may be removed. Restore it from Settings → Repositories → Show removed.

Related surfacesCopy Anchor Link

• Installations explains GitHub App coverage and repo triggerability.
• Assignments is for standing repo-to-agent work.
• Triggers is for installation-scoped event routing.
• Observability is where you inspect cost, calls, sandbox linkage, and runtime health after work starts.
• Worktrees explains task, branch, checkout, and Sandbox binding after Control delegates isolated coding work.