Get started with Explore

Your live Explore profile — set up with your agent in one session

Bring your existing CV, writing, or structured data — Explore maps it into a live profile in one setup session. Readable by people, queryable by agents. Follow the steps below to install the CLI, run `explore setup`, and complete browser approval only when prompted.

Start setup Watch the walkthrough
  • Takes minutes to install
  • Browser only when you need signup or approval
  • Your profile stays private until you publish

Install the CLI -> run `explore setup` -> finish browser approval only when prompted.

Watch the walkthrough

Watch a real profile go live in one setup session

Watch a quick walkthrough of installing Explore, approving login, importing a CV and blog, and publishing an interactive profile.

If the page feels like a lot, start here. Watch the full flow once, then come back to the steps below when you are ready to do it yourself.

Start the setup steps Watch on Loom

Step 1

Start here

Install the Explore CLI in your workspace terminal

Run this in the terminal attached to the same workspace where your agent is running, then install the CLI.

This makes the `explore` command available to your agent and terminal workflow.

gem install exploremyprofile

Step 2

After install

Run explore setup with your agent

Open your agent and run `explore setup` after the CLI is installed. This is the shared setup step across supported agents.

Use the shared CLI flow first. The browser appears only when signup, sign-in, or approval is needed.

explore setup
  • The same shared setup path works across Codex, Claude Code, OpenCode, and Cursor.
  • Optional helpers come later and are not required for this step.

Step 3

Only if needed

Approve in the browser when prompted — then return to your agent

Explore opens the browser only when you need signup, sign-in, or approval. Once that small step is done, return to your agent.

The browser is supportive here: use it for account creation, sign-in, or approval, then continue the real workflow in your agent.

  • The browser step stays small and supportive rather than becoming the main operating surface.
  • When approval finishes, return to your agent and keep going there.

Step 4

Then do this

Return to your agent and continue there

Once setup succeeds, go back to your agent and keep going there.

Ask for the update you want, inspect your profile, or open the profile YAML when you want more control.

After setup

What to do next after setup

After setup succeeds, the browser step should be done. From there, ask your agent naturally for the profile update you want or open your profile YAML locally when you want more control.

Ask your agent to update it for you

Start with a simple ask when you want your agent to handle the update flow for you through the shared Explore contract.

  • Import my CV into my Explore profile.
  • Add my blog or writing to my Explore profile.
  • Inspect my current profile and suggest improvements.

Edit the profile file directly

Want more control? Your agent can open your Explore profile YAML locally so you can make bulk edits yourself, then validate and apply the changes back to Explore.

  • Open my Explore profile YAML so I can edit it.
  • I made a few edits. Please update my Explore profile with the changes.
  • Open my profile file and help me tighten my summary and experience.
  • Apply the edits I just made to my Explore profile.

Optional helpers

Optional helpers for supported agents

Codex, Claude Code, OpenCode, and Cursor all use the same shared Explore CLI flow underneath. Helpers can improve the experience in some tools, but they are not required for basic Explore usage.

Keep the main path simple: finish the shared setup flow first, then add helper polish only when it genuinely helps in your tool.

# Optional Codex helper
Use $skill-installer to install:
https://github.com/johnnybutler7/explore-skill

# Optional Claude Code helper
explore setup claude --write
  • Install the Codex helper only if you want the optional Explore helper in Codex.
  • Use `explore setup claude --write` only when you want the Claude Code helper installed locally.
  • OpenCode and Cursor work through the same shared CLI flow without a required helper step.

Open the Explore skill repo

Supported agents

Supported agents today

Keep the support story practical: one shared Explore CLI and API contract, four supported tools today, and a conservative boundary around everything else.

Codex

Supported today on the same shared flow. Add the public Explore helper only when you want Codex-specific polish on top of the core CLI flow.

Claude Code

Supported today through the same CLI-first flow. `explore setup claude --write` is optional and sits on top of the same Explore auth and command flow.

OpenCode

Supported today through the shared CLI flow. Use Explore naturally after CLI install and auth; no separate helper is required for basic usage.

Cursor

Supported today through the shared CLI flow. Start with the Explore CLI and auth, then use Explore naturally from Cursor.

Shared core flow

Install the CLI, connect with Explore, use the CLI, inspect commands with machine-readable help, and read structured output. Tool-specific helpers stay thin and optional.

Other tools soon

Other tools that can run shell commands should also work with Explore's shared CLI flow, with fuller support rolling out very soon.

Advanced / manual workflow

Use the raw CLI only when you want to drive the workflow yourself

The main product story is one shared Explore flow: install the CLI, connect your account with explore setup or explore login, and use optional helpers only when they improve the experience in your tool. These commands remain available for manual, scripted, and fallback paths.