Get started

Get started with Explore

Install Explore, inspect a public profile, then log in only when owner work begins.

This is the shortest path from first look to a real owner workflow: public profile first, browser approval when needed, then explicit draft and preview steps.

Create your profile View example profile

What you'll do

  • Install Explore and the Codex skill.
  • Inspect a public profile first.
  • Log in only when you want to manage your own content.

Sample public target: /profiles/johnny

You only need an Explore account for owner-only steps. Public profile inspect comes first.

Need the deeper product contract? Visit /agents.

Start here

Follow the first useful path in under a minute

Do these steps in order and you will see the full Explore flow quickly: public profile first, browser approval when owner work begins, then the draft workflow.

Step 1

Install Explore

gem install exploremyprofile

This installs the explore command.

Step 2

Install the Codex skill

Use $skill-installer to install:
https://github.com/johnnybutler7/explore-skill

This gives Codex the Explore workflow and safety guidance.

Step 3

Try the public profile inspect

Use Explore to inspect the public profile for johnny as JSON

This works without owner credentials and shows the public profile flow first.

Step 4

Approve login in the browser

explore login

Run explore login. Explore opens browser approval by default. Approve it, return to Codex, and continue with an authenticated session.

Most users should use explore login exactly as shown here. Public inspect works without owner auth, and owner actions begin with this browser-approved step.

Step 5

Continue in Codex

List my current writing drafts in Explore

Once login is saved locally, Codex can continue naturally with authenticated owner-only prompts.

Step 6

Try the owner-only draft workflow

Import this blog post into my writing drafts and show me the preview before applying it: <url>

Replace <url> with the article link you want to import, then preview the draft before applying it.

Need an account before this step? Create account or log in.

One real outcome

See the import flow become a live profile

Once setup is working, one practical owner workflow is importing existing material into Explore and turning it into a live profile.

See the CV-to-Explore proof page for a concrete example from login to mapped profile result.

Next prompts

Keep going in Codex

Show my latest Explore writing
Preview my latest Explore draft

These keep you in the natural-language Codex flow before you drop down to direct terminal commands.

Auth model

Keep the login story simple

  • Public profile inspect works without owner auth.
  • Owner actions begin with explore login.
  • Browser approval is the normal and recommended path.
  • Manual account tokens remain available only for advanced, scripted, or fallback use.
  • You can stay on this page for the whole first-run flow, then use /agents when you want the deeper product guide.

Prefer direct CLI commands?

Verify the same flow in Terminal

explore profile inspect --slug johnny --json
explore login
explore whoami --json

Naming note: the RubyGems package name is exploremyprofile, but the installed command you run is explore.

More Explore commands

Use the CLI directly after login

explore drafts list --json
explore content create-draft --account johnny --input tmp/draft.json --json
explore drafts apply-preview --account johnny --draft 12 --json

These are the lower-level commands behind the owner-only flow you just tried in Codex.

Advanced configuration

Use a different host or a manual fallback only when needed

export EXPLORE_BASE_URL=https://your-host.example
explore login --no-browser --account acme-careers
printf '%s' "$OWNER_API_TOKEN" | explore login --token-stdin --account acme-careers

Most users should use plain explore login first. Only use these overrides if you are not using the default hosted Explore service, want to open the approval URL yourself, or need a non-interactive manual fallback.