TokenX help desk

Useful details. Human reply.

Get help with installation, routing decisions, configuration, or a security report. TokenX does not require a separate publisher account.

PRODUCT SUPPORT

Email TokenX support

Send the TokenX version, Codex version, operating system, and the smallest reproducible description. Remove prompts, credentials, proprietary source, and personal data before sending diagnostics.

Email TokenX support
SENSITIVE REPORTS

Security report

Do not file credentials or private prompts in a public issue. Email a concise impact description and reproduction steps with the subject "TokenX security."

Send a private security report

First use

Install and trust hooks.

01

Install TokenX

Add the TokenX marketplace source and install the Codex plugin through the supported Codex plugin commands. No custom agent files under ~/.codex/agents are required.

02

Review hook trust

Use /hooks to inspect the four TokenX commands. Routing does not activate until the installed hooks are trusted.

03

Start a new Codex session

Plugin updates and hook registrations load at session start. Close the current thread after an install or update and test in a new one.

Common fixes

When routing looks wrong.

01

Confirm hooks are trusted

Open /hooks and verify the TokenX SessionStart, UserPromptSubmit, PreToolUse, and SessionEnd commands are trusted for the current workspace.

02

Run the doctor command

From a normal shell, resolve the installed plugin path, export PLUGIN_DATA, then run node "$TOKENX" doctor --json. Share only bounded error codes and remove local paths before contacting support. The route-agents skill explains routing; it does not replace the doctor CLI.

03

Refresh after config trouble

If stored configuration is incompatible, run node "$TOKENX" update when the plugin is installed from a marketplace, then start a new session. See the public repository README for the shell resolver preamble.