Getting Started

End-to-end setup for first-time users.

Prerequisites

Installation

npm install -g @openai/codex @jstn-sdk/rcs
rcs doctor

When @jstn-sdk/rcs actually bumps to a newer version, the global npm install prints an explicit reminder instead of launching rcs setup automatically. When you're ready, rerun rcs setup manually or use rcs update to check npm and then run the same setup refresh path. Fresh RCS-managed gpt-5.5 configs now recommend model_context_window = 250000 and model_auto_compact_token_limit = 200000 only when those keys are missing.

Explicit latest-version triggers also exist:

npm install -g @jstn-sdk/rcs@latest
rcs update
rcs latest
rcs @latest

rcs doctor verifies the install shape. Before treating the runtime as ready, also prove that the active Codex profile can perform a real request:

codex login status
rcs exec --skip-git-repo-check -C . "Reply with exactly RCS-EXEC-OK"

Recommended Launch

rcs --xhigh --madmax   # trusted environments
rcs                    # standard launch

First Run Walkthrough

  1. Create or enter a project directory.
  2. Install or update RCS globally.
  3. After install or real RCS version bumps, rerun rcs setup yourself when you're ready, or use rcs update when you also want npm to update RCS first.
  4. Run rcs doctor, then the codex login status plus rcs exec smoke test above.
  5. Start Codex CLI with rcs.
  6. Use $brief "clarify the creator workflow change" when intent or boundaries are still unclear.
  7. Use $blueprint "approve the plan and review tradeoffs" to lock the implementation plan.
  8. Choose $forge "carry the approved plan to completion" or $crew "execute the approved plan in parallel" based on execution style.

Creator Workflow First

The canonical public path is:

$brief -> $blueprint -> $forge / $crew -> $autoforge

The creator-first path stays $brief -> $blueprint -> $forge / $crew -> $autoforge. Supporting execution surfaces still exist for operational control, but onboarding should stay creator-first and Roblox-first.

Optional Live Studio Connection

If you want real-time Roblox Studio inspection or script/object changes against an open Studio session, use the upstream robloxstudio-mcp compatibility lane instead of treating RCS itself as the live Studio transport.

See robloxstudio-mcp Compatibility for the standard Codex commands, read-only inspector mode, and Windows fallback config.

Prompt Instruction Source

RCS layers project instructions by default (extends Codex behavior, does not replace/bypass Codex core system policies):

-c model_instructions_file="<cwd>/AGENTS.md"

Override behavior when needed:

RCS_BYPASS_DEFAULT_SYSTEM_PROMPT=0 rcs
RCS_MODEL_INSTRUCTIONS_FILE=/path/to/instructions.md rcs

Troubleshooting

IssueWhat to check
rcs command not foundRe-run global install and ensure npm global bin is in PATH.
Prompts not availableConfirm files exist in ~/.codex/prompts/ and re-run rcs setup.
Skills not loadingVerify ~/.codex/skills/*/SKILL.md files were installed.
Doctor reports config issuesRun rcs doctor and apply the suggested fixes.
Doctor is green but execution failsRun codex login status and rcs exec --skip-git-repo-check -C . "Reply with exactly RCS-EXEC-OK" from the same shell/profile. A green doctor is install evidence, not proof of authenticated model execution.
Custom or profile HOME cannot authenticateCheck the active ~/.codex or CODEX_HOME. Containers, profile shells, and service users may not see the same auth/config as your normal user home.
Local proxy or compatible endpoint returns 401If you use a proxy, verify the active ~/.codex/config.toml contains the expected openai_base_url. Proxy keys sent to the wrong endpoint can look like missing bearer auth or an incorrect API key.
rcs doctor --team sees a dead tmux teamIf the team is intentionally abandoned, run rcs team shutdown <team-name> --force --confirm-issues, then rcs cancel, then rcs doctor --team.

Need deeper operator help? See Troubleshooting execution readiness.