Amruth Pillai
3c195dc3f8
Upgrades to Better Auth 1.7, expands Custom Styles coverage of item headers, and adds a human-approval step to the AI agent's resume edits. Breaking for self-hosters using a custom OAuth provider: the callback path changes from /api/auth/oauth2/callback/custom to /api/auth/callback/custom, and installs using OAUTH_DISCOVERY_URL need one additional UPDATE after upgrading. Both are documented in docs/self-hosting/sso.mdx. - Better Auth 1.7, with the account issuer migration and the jwks alg/crv columns the 1.7 jwt plugin requires - Agent edits gated behind an approval step, with crash-safe runs and context pruning - item-header now covers every section header row on every template; adds the item-header-row part - Fixes provider unlinking, auth error messages, and version conflicts on freshly created resumes - New /auth/error page, translated across all 53 target locales - DeepSeek Harness plugin moved into packages/dsh-plugin - Dependency bumps across the workspace
dsh-plugin-reactive-resume
Connect Reactive Resume to DeepSeek Harness. Read, create, and edit your resumes and job applications from a Harness session.
Install
dsh plugin --profile <name> add dsh-plugin-reactive-resume
This package declares dsh.bundle, so the profile picks it up as a layer and mounts it automatically. Until you configure a key it mounts nothing and logs a warning, so installing it never leaves a profile unbootable.
Configure
Mint an API key at https://rxresu.me/dashboard/settings/api-keys and export it as RXRESUME_API_KEY — the bundle patch reads that variable. To set it explicitly, or to change any other option, patch the row by id from your profile's cordis.patch.yml:
- id: reactive-resume
config:
apiKey: !!js process.env.RXRESUME_API_KEY
Options
| Key | Default | Description |
|---|---|---|
apiKey |
'' |
API key from <url>/dashboard/settings/api-keys. Empty mounts nothing. |
url |
https://rxresu.me |
Origin of your instance. Set this if you self-host. |
serverName |
resume |
Tool namespace. Tools reach the model as mcp__<serverName>__<rawName>. |
toolCallTimeoutMs |
60000 |
Per-tool-call timeout. |
Every tool Reactive Resume publishes is exposed. Narrowing that set is not currently possible from a plugin: Harness's ctx.tools.restrict() requires an agent-scoped context, which a plugin context is not.
Self-hosted
- id: reactive-resume
config:
apiKey: !!js process.env.RXRESUME_API_KEY
url: http://localhost:3000
What it does
Bridges Reactive Resume's MCP server into ctx.tools, and contributes a system-prompt section covering the things models get wrong about resume editing: reading before patching, RFC 6902 path construction against the published schema, UUID-keyed section entries, and locked resumes.
You could wire the bridge yourself with a raw @deepseek-ai/dsh-mcp-client row. What you cannot do that way is contribute the prompt section — that is what this package adds.
Development
This package lives in the Reactive Resume monorepo at packages/dsh-plugin, next to packages/mcp — the server it bridges. src/tool-names.test.ts checks every tool the prompt guide names against @reactive-resume/mcp/tool-names, so renaming a tool breaks this package in the same pull request.
pnpm --filter dsh-plugin-reactive-resume test
pnpm --filter dsh-plugin-reactive-resume build
License
MIT