from their app’s codebase than hand-write each one in Navigation routes. The chatropic-guide-with-nav-route-generator skill scans your product’s routing layer and emits a ready-to-import route registry plus help-center markdown. It is a single Python 3 script with no dependencies, so it runs in Claude Code, Codex, Cursor, or a plain terminal, the only difference is how each tool triggers it.
The generated navigation-routes.json matches the route fields used in Navigation routes (label, path, description, keywords), so you can upload it directly in Navigation or POST each entry to the nav-routes API.

What it produces

Every run writes four files into the --out folder: Only user-facing pages are included. API endpoints, auth flows (login, logout, signup, oauth, sso, password reset, …), and webhooks are dropped automatically, they are not destinations a support agent would deep-link a customer to.

Prerequisites

Install & run

Claude Code

Skills are auto-discovered from a skills/ folder.
Then invoke it in a session:
…or just ask (“generate the Chatropic navigation routes from this repo”). Claude runs the script and writes a chatropic-help-guides/ folder in the working directory.

Codex (OpenAI Codex CLI)

Codex has no skills folder, make the script available and point the agent at it in AGENTS.md:
Then ask Codex to “regenerate the navigation routes”, or run the command yourself (Terminal).

Cursor

Add a rule at .cursor/rules/nav-route-generator.mdc so the agent knows the command:
Prompt Cursor’s agent, or run it in Cursor’s integrated terminal (Terminal).

Terminal

The universal path, no agent involved.
Exit codes: 0 ok · 2 nothing found · 1 bad args.

Import the routes

After reviewing navigation-routes.json, register routes in the dashboard:
  1. Open Navigation.
  2. Drag and drop navigation-routes.json or click to browse.
  3. Confirm imported routes in the sidebar list, edit or delete any that need adjustment.
For bulk automation or CI, use the Customer Support API instead, see Navigation routes, Configure routes (API). Add a description and keywords to each entry so the agent can match them with vector similarity.

Navigation routes

Configure and test routes the agent deep-links to.

Embed navigation

Host-side postMessage integration for clicks.