Get started with Explore
Set up Explore with your agent
Recommended today: Codex plus the Explore CLI. Get Codex, install the Explore CLI, install the Explore skill, then run `explore setup`. Explore opens the browser only when signup, sign-in, or approval is needed.
Codex is the supported first-class path today. The Explore CLI is the broader compatibility layer today for shell-capable agent environments. More first-class setup paths may come later, but they are future work rather than current support.
Install the CLI
Install the public skill
Run explore setup
What to do next
Install the tooling once, then start in your agent.
The page below shows the shortest path: install the CLI, install the skill, then run `explore setup`.
Signed out right now. Start in your agent with `explore setup`; Explore will open the browser only if signup, sign-in, or approval is needed.
Step 1
Start here
Install the Explore CLI
Install the RubyGems package so the `explore` command is available for agent and terminal workflows.
This is the only install step for the CLI itself.
gem install exploremyprofile
Step 2
Do next
Install the Explore skill
Get Codex, then install the public Explore skill:
Codex is the supported first-class path today.
Use $skill-installer to install:
https://github.com/johnnybutler7/explore-skill
- Use the official Codex getting-started page if you do not have Codex yet.
Step 3
After install
Run explore setup with your agent
Open your agent and run `explore setup` after the CLI and public skill are in place.
Complete browser approval when prompted, then return to your agent. The browser supports auth here, but it is not the main operating surface.
explore setup
- Complete browser signup, sign-in, or approval only when prompted.
- Return to your agent and continue there.
After setup
Then ask Codex to update your profile
After setup, use Codex to inspect your profile, refine it, or import more material when you need to.
- Import my CV into my Explore profile.
- Add my blog or writing to my Explore profile and show me the preview first.
- Inspect my current profile and suggest improvements.
Preferred agent
Current support boundary
Keep the setup story practical: Codex plus the Explore CLI is the supported path today, while the CLI remains the broader compatibility layer for shell-capable agent environments.
Recommended today
Codex plus the Explore CLI is the supported first-class path today. Install the public skill there, then run `explore setup`.
Broader compatibility today
If your agent environment can run shell commands, it can use the Explore CLI as the current compatibility layer. That is CLI-level compatibility, not a broader first-class provider integration.
Browser role
The browser opens only when signup, sign-in, or approval is needed, plus the small account settings that belong there.
Not current support
More first-class setup paths may come later, but Explore is not claiming them as supported today.
Helpful links
Keep support close, but keep the main story simple
Advanced / manual workflow
Use the raw CLI only when you want to drive the workflow yourself
The recommended path today is to ask naturally in Codex while the Explore CLI handles the underlying workflow. These commands remain available for manual, scripted, and fallback paths, and they are also the broader compatibility layer for other agent environments.
Show manual CLI details
Install and connect directly
Use these commands only when you want to drive the CLI yourself instead of asking Codex to do it for you.
gem install exploremyprofile
explore setup
explore login --account <slug>
Use the profile document directly
The normal V1 path for CVs, writing, projects, links, and summary updates is to export the profile document, edit it, validate it, and apply it back to Explore.
explore export profile --account <slug> --format yaml > profile.yaml
explore validate profile.yaml
explore apply profile.yaml --account <slug>
Preview and inspect directly
Use these commands when you want the current preview or live profile output without the guided Codex flow.
explore publish preview --account <slug> --json
explore profile inspect --slug <slug> --json
Advanced / manual access fallback
Manual tokens and no-browser login remain available for advanced or scripted use. They are not the primary onboarding path.
explore setup --no-browser
explore register --no-browser
printf '%s' "$OWNER_API_TOKEN" | explore login --token-stdin --account <slug>