Experiencer
Experiencer
Open Free Editor

Experiencer documentation

Use Codex or Claude Code

Connect Codex, Claude Code, or your own scripts to Experiencer with a personal API key and the REST API.

Cloud account: This workflow is available to signed-in Free and paid Pro accounts within tier limits.

Last reviewed:

Coding agents such as Codex and Claude Code can edit your saved Experiencer résumés through the REST API. This suits a job search you run from a local folder or an Obsidian vault: the agent reads your notes, job descriptions, and application tracker there, and edits the résumé in Experiencer.

API access works on every plan, including the free account, within your plan’s usage limits. Your AI provider handles the conversation and its costs.

Prefer a chat assistant such as ChatGPT, Claude, or Grok? See Connect an AI assistant.

1. Generate your API key

  1. In Experiencer, open Settings → Connected tools.
  2. Under API access and agent editing, choose Generate API key.
  3. Copy the key now. It is shown only once.

The API access and agent editing settings with a newly generated sample key

You have one active key. Rotate API key replaces it immediately, and Revoke API key turns it off.

2. Store the key in an environment variable

Save the key as EXPERIENCER_API_KEY so the agent can use it without seeing it in the conversation. Never paste the key into a prompt, a notes file, source control, or a URL.

On macOS or Linux, add this line to your shell profile, such as ~/.zshrc or ~/.bashrc:

export EXPERIENCER_API_KEY="paste-your-key-here"

On Windows, run this once in PowerShell:

[Environment]::SetEnvironmentVariable('EXPERIENCER_API_KEY', 'paste-your-key-here', 'User')

Open a new terminal afterward so the variable is loaded.

3. Point your agent at the instructions

The agent needs Experiencer’s agent instructions. They describe authentication, the preview-then-approve workflow, and the main endpoints. Add a short note to the instructions file your agent reads in your job-search folder:

## Experiencer
Before working with my résumés, download and follow
https://experiencer.app/api/agent/v1/instructions with curl.
Authenticate with the EXPERIENCER_API_KEY environment variable.
Never print the key.

Download the instructions with curl rather than a web-fetch tool: the /api/ paths are closed to crawlers, so many fetch tools are refused.

Claude Code

Put the note in CLAUDE.md in your job-search folder, then start Claude Code there. Claude Code inherits environment variables from the terminal you start it in. Approve the curl commands it asks to run.

Codex

Put the note in AGENTS.md in your job-search folder, then start Codex there. Codex usually needs two settings in ~/.codex/config.toml before it can call Experiencer:

# Let commands in the workspace sandbox reach experiencer.app.
[sandbox_workspace_write]
network_access = true

# Codex hides variables whose names contain KEY, SECRET, or TOKEN by default.
# Pass only the Experiencer key through.
[shell_environment_policy]
ignore_default_excludes = true
include_only = ["PATH", "HOME", "USERPROFILE", "SYSTEMROOT", "TEMP", "TMP", "EXPERIENCER_API_KEY"]

If you already have these sections, add the settings to them rather than repeating the headings.

4. Ask for a change

Start with a task such as:

Use my preferences and this job description to tailor my saved master résumé to two pages. Preview the changes and ask before saving. Then propose an update to my job tracker.

The agent creates a preview without saving. It shows you a preview link and the proposed changes, and saves only after you approve. Open the preview link to check the layout yourself.

For more requests, including converting a Word résumé, see Example prompts.

Reference for scripts

REST and MCP use the same review, preview, and editing services, with the same ownership checks and the same approval step before saving. Your agent’s local files stay on your computer; Experiencer does not upload or host your vault.

Troubleshooting

Next: Review with an AI assistant.