Support

A self-serve support flow for tokenpatch users. It maps the common setup failures from the project doctor and quickstart into concrete next steps. For full reference, start from the documentation center.

What are you using?

Use tokenpatch inside Codex and keep the strong model key in Codex itself.

What is blocked?

The wizard combines the selected client and issue into a concrete recovery path.

Codex app route

  1. Run `tokenpatch bootstrap` in the target project.
  2. Configure executor env vars in the Codex MCP settings.
  3. Ask: `tp: implement ... Only modify <files>.`
  4. If Codex asks for network or command permission during the CLI fallback, allow once and retry the same prompt.

Recommended next steps

  1. Run `tokenpatch bootstrap`.
  2. Open the First Run page and fix any warnings.
  3. Run `tokenpatch doctor --api` if keys are already set.