Back to blog
Product Update

wrok Meets OpenClaw: Manage Your Career from Your AI Assistant

Wrok||2 min read

wrok Meets OpenClaw: Manage Your Career from Your AI Assistant

Status (SRA-230 / SRA-229): the dedicated OpenClaw plugin is Coming / Roadmap — not Live. Do not treat plugin install or static API keys as the current bot path.

If you already use an AI assistant to write code, answer questions, and automate your workflow — career data should live where you work. wrok’s live agent doors today are MCP + OAuth, or the same OAuth access token as Bearer on job-pipeline HTTP for Instinct-class clients that cannot attach MCP.

Live bot paths today

  • Bots with MCP: MCP + OAuth at https://mcp.wrok.app/mcp. Five tools: get_career_data, get_coding_profile, list_inbox, create_application, advance_application.
  • Bots without MCP: the same OAuth access token as Bearer on job-pipeline HTTP at https://mcp.wrok.app — inbox, create, and typed advance.

Never wrok_sk_ keys, device-code, /cli-auth, or WROK-… user codes for bot install.

Why a dedicated plugin is still on the roadmap

A first-party OpenClaw plugin would let a locally hosted assistant talk to wrok without a browser. That work is not shipped. Until it is, do not follow old install or create-key guides.

The problem those guides tried to solve is real: most people update a résumé once a year, usually in a panic. Friction, not motivation, is the blocker. Live wrok already keeps the career record where agents can read and write it — through OAuth, not a static key.

What wrok can do once a bot is connected

Through MCP or Instinct OAuth Bearer HTTP, an agent can work from the live record:

  • Read career data and coding profile
  • List the job-pipeline inbox
  • Create an application
  • Advance an application with a typed next_action

Resume, public profile, blog, and the rest of the HTTP SoR spine remain product surfaces for humans and SDKs — not the bot install story.

Getting started

  1. Create an account at wrok.app
  2. Connect with MCP OAuth, or use the same OAuth token as Bearer on job-pipeline HTTP
  3. Treat OpenClaw as Coming until Product marks it Live

New to wrok? Sign up free at wrok.app →. Connect an agent with OAuth — never a static API key.

Product UpdateOpenClawAI IntegrationHeadless API