The standalone Orion LinkedIn Agent — the one that needed a local bridge, a separate WXT Chrome extension, and an MCP registered in Codex — is retired and no longer maintained. All of its capabilities (LinkedIn search, candidate profiles, conversation and connection history, Recruiter evidence search, plus Liepin search / recommendations / resumes / conversations) are now built directly into the web recruiting Agent.

​
How to use it now

No local bridge, no separate LinkedIn extension. Just two steps:
  1. Install the Orion Browser Operator extension once and connect it to your Orion workspace. See Browser Extension.
  2. Ask the Orion Agent in plain language. With My Browser enabled, the Agent uses your already-signed-in Chrome to work on LinkedIn and Liepin — you watch every step and can take over or stop at any time.
This is one clean recruiting surface: the same Browser Operator extension powers both general web tasks and LinkedIn / Liepin recruiting. You do not run two extensions side by side — if you installed the old LinkedIn extension, remove it using Clean up the old install below.

​
Capability mapping (old → new)

Once Browser Operator is installed and connected, everything you used to run through Codex is available right in the web Agent chat:
What you wantJust tell the Agent
Check the connection”Is my LinkedIn connected?”
Source against a JD (evidence-backed pool)“Find people on LinkedIn for this JD: <paste JD>”
Read a candidate profile”Read this candidate, don’t contact them yet: <profile url>”
Recent conversations / who added me”Who have I talked to recently?” / “Who connected with me recently?”
Search Liepin”Search Liepin for <keywords>”
Outreach / reply (sending)“Send this candidate a note: <content>” — real sends always show an approval card with the recipient and full text first
Real sending is off by default and requires an administrator to enable it explicitly. Even when enabled, every real send shows an approval card so you can confirm exactly what goes to whom. Read-only analysis, search, profile reads, and report generation never send a message.

​
Clean up the old install (only if you used the old version)

If you previously installed the standalone LinkedIn Agent, remove that stack after installing the new extension so the two don’t conflict:
  1. Remove the old Chrome extension: open chrome://extensions and delete the old Orion LinkedIn extension (the WXT one with the floating widget). Keep only Orion Browser Operator.
  2. Stop the resident local bridge process: Codex starts the bridge (default port 8765) on demand, and it stays running detached from the terminal. Ask it to shut down, then verify: 
    curl -s http://127.0.0.1:8765/shutdown >/dev/null 2>&1 || true
# If it's still listening, confirm the process on the port before stopping it:
lsof -nP -iTCP:8765 -sTCP:LISTEN
  3. Stop and remove the local bridge LaunchAgent (macOS, only if you set up auto-start): 
    launchctl unload ~/Library/LaunchAgents/com.orion.linkedin-bridge.plist 2>/dev/null || true
rm -f ~/Library/LaunchAgents/com.orion.linkedin-bridge.plist
  4. Unregister the Codex MCP: remove the local MCP named linkedin (codex mcp remove linkedin, or delete its entry from ~/.codex/config.toml).
  5. Delete the install directory and skill: 
    rm -rf ~/orion/linkedin-agent
rm -rf ~/.codex/skills/linkedin-agent
  6. Strip the old AGENTS.md snippet: open ~/.codex/AGENTS.md and delete the whole block from BEGIN orion-linkedin-agent to END orion-linkedin-agent.
On Windows, replace ~/orion/linkedin-agent with C:\orion\linkedin-agent and the skill path with %USERPROFILE%\.codex\skills\linkedin-agent; there is no LaunchAgent step.

​
Why this changed

The old setup kept a local bridge running on your machine, maintained a separate WXT extension, and wired an MCP into Codex — a long install chain that only worked locally. The new setup builds those capabilities straight into the web recruiting Agent: install the extension once, connect the workspace once, and anyone on your team who signs in can use it. Capabilities ship with the web app, so there’s no local component to update by hand.