Skip to main content
plugin CX Codex

upwork-autopilot — Claude Code plugin: Upwork search and proposals

The upwork-autopilot plugin for Claude Code and Codex searches Upwork jobs, checks proposal pages, and submits proposals through Chrome. It supports user-controlled job search sessions.

MIT ★ 1,596 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add hashgraph-online/awesome-codex-plugins
/plugin install upwork-autopilot@awesome-codex-plugins
Open on GitHub

What upwork-autopilot does

The plugin checks whether your Upwork session is signed in, searches jobs using configured criteria, and inspects a proposal page before submission. It reads proposal data from JSON payload files and records successful submissions in JSONL. Applicant details and search preferences live in local configuration.

Sign in to Upwork in your own Chrome profile first. The plugin does not copy cookies or credentials; Chrome launches with CDP enabled and may need to restart once. Avoid concurrent navigation on the live Upwork tab. It stops when available Connects drop below 15; proposals must begin with Hi, and must not include a CV attachment.

What it helps with

  • search Upwork listings with configured filters
  • inspect a job page before preparing an application
  • submit a proposal from a JSON payload
  • record successful submissions in JSONL

Example prompts for the agent

  • Search Upwork for “AI integration developer LLM automation” and show me the first result’s details.
  • Check the job page at <job-url> before I apply.
  • Submit the proposal at <proposal-url> using /abs/path/to/payload.json.

How to install upwork-autopilot

Plugin marketplace

/plugin marketplace add hashgraph-online/awesome-codex-plugins
/plugin install upwork-autopilot@awesome-codex-plugins

Step by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own

Questions about upwork-autopilot

How do I install upwork-autopilot in Claude Code?

Run /plugin marketplace add hashgraph-online/awesome-codex-plugins, then /plugin install upwork-autopilot@awesome-codex-plugins.

What does upwork-autopilot do?

It searches Upwork listings, checks proposal pages, and submits proposals using JSON payload files. Successful submissions are written to a JSONL log.

What do I need before using the plugin?

Sign in to Upwork in your local Chrome profile. The plugin uses that profile through CDP and does not transfer credentials; Chrome may need to restart.

Source text

upwork-autopilot · MIT
# Upwork Autopilot

Codex plugin for controlled Upwork job search, qualification, and proposal submission sessions.

[![Upwork Autopilot on HOL Registry (Trust Score)](https://img.shields.io/endpoint?url=https%3A%2F%2Fhol.org%2Fapi%2Fregistry%2Fbadges%2Fplugin%3Fslug%3Dklajdikkolaj%252Fupwork-autopilot%26metric%3Dtrust%26style%3Dfor-the-badge%26label%3DUpwork+Autopilot)](https://hol.org/registry/plugins/klajdikkolaj%2Fupwork-autopilot)

## What it does

- launches either an isolated Chrome profile or your normal logged-in Chrome profile with CDP enabled
- asks each user for their own applicant profile and search defaults
- probes whether the live Upwork session is logged in
- searches filtered Upwork job results
- opens and probes proposal pages before submission
- submits proposals from ordered payload JSON files
- logs successful submissions to JSONL
- keeps the public plugin generic while storing private applicant data in local-only config files

## Core rule set

- proposals must start with `Hi,`
- tone must stay friendly and professional
- no off-platform contact details
- do not attach the CV
- do not run concurrent browser navigation against the live Upwork tab
- stop once available Connects fall below `15`

## Repo layout

```text
.codex-plugin/
config/
docs/
examples/
references/
scripts/
skills/
```

`config/*.template.*` files are public and safe to commit.

`config/*.local.*` files are private user data and are ignored by git and excluded from release archives.

The applicant profile is intentionally user-specific. Proposal tone, differentiators, proof points, and closing CTA should be customized per applicant rather than hardcoded into the plugin.

## Quick start

Install with npm:

```bash
npm install -g upwork-autopilot
upwork-autopilot install-home
upwork-autopilot setup-profile
upwork-autopilot launch
upwork-autopilot probe
```

Install with Homebrew:

```bash
brew tap klajdikkolaj/upwork-autopilot https://github.com/klajdikkolaj/upwork-autopilot
brew install klajdikkolaj/upwork-autopilot/upwork-autopilot
upwork-autopilot install-home
upwork-autopilot setup-profile
```

Install from a local checkout:

```bash
cd /path/to/upwork-autopilot
bash scripts/bootstrap.sh
node scripts/setup-applicant-profile.mjs
bash scripts/launch-controlled-chrome.sh
node scripts/upwork-session-probe.mjs
```

By default, `launch-controlled-chrome.sh` now reuses the machine's normal logged-in Chrome profile.

If you want an explicit logged-in-profile launch, use:

```bash
bash scripts/launch-logged-in-chrome.sh
```

If you want a fully isolated browser profile, use:

```bash
bash scripts/launch-isolated-chrome.sh
```

The default and logged-in launchers relaunch Chrome with the machine's existing user profile and CDP enabled, so saved Upwork cookies remain available to the automation.

Important:

- the plugin does not ship, copy, or transfer Chrome cookies or Upwork credentials
- each user must already be signed into Upwork in their own local Chrome profile
- the logged-in mode only reuses credentials that already exist on that machine
- Chrome may need to close and relaunch once so CDP can attach to the real profile

Useful environment variables:

```bash
UPWORK_AUTOPILOT_CHROME_MODE=system-profile
UPWORK_AUTOPILOT_SYSTEM_PROFILE_DIRECTORY=Default
UPWORK_AUTOPILOT_CLOSE_EXISTING_CHROME=1
UPWORK_AUTOPILOT_PORT=9225
```

## Main commands

```bash
upwork-autopilot setup-profile
upwork-autopilot search-plan
upwork-autopilot search-inspect 'AI integration developer LLM automation'
upwork-autopilot search-inspect 'AI integration developer LLM automation' detail 0
upwork-autopilot apply-probe '<job-url>'
upwork-autopilot submit-proposal '<proposal-url>' /abs/path/to/payload.json
upwork-autopilot launch
upwork-autopilot launch-isolated
upwork-autopilot validate

node scripts/setup-applicant-profile.mjs
node scripts/upwork-search-plan.mjs
node scripts/upwork-search-inspect.mjs 'AI integration developer LLM automation'
node scripts/upwork-search-inspect.mjs 'AI integration developer LLM automation' detail 0
node scripts/upwork-apply-probe.mjs '<job-url>'
node scripts/upwork-submit-proposal.mjs '<proposal-url>' /abs/path/to/payload.json
bash scripts/launch-controlled-chrome.sh
bash scripts/launch-isolated-chrome.sh
bash scripts/validate.sh
bash scripts/package-release.sh
bash scripts/export-github-repo.sh
```

Run `upwork-autopilot --help` for the full installed command list.

## Install for personal use

```bash
upwork-autopilot install-home
# or, from a checkout:
bash scripts/install-home.sh
```

This installs the plugin into `~/plugins/upwork-autopilot` and updates `~/.agents/plugins/marketplace.json`.

## Publish as a standalone GitHub repo

1. Run `bash scripts/export-github-repo.sh`
2. Change into the exported repo under `dist/github-repo/upwork-autopilot`
3. Follow [docs/PUBLISHING.md](./docs/PUBLISHING.md)

The export keeps:

- plugin manifest
- skills
- scripts
- docs
- templates
- examples

The export removes:

- `node_modules`
- local applicant config
- local search config
- runtime logs
- previous build artifacts

## Validation

Run:

```bash
bash scripts/validate.sh
```

This checks shell syntax, Node script syntax, and runs Codex skill validation when the local validator is available.

## Example payload

See [examples/proposal-payload.example.json](./examples/proposal-payload.example.json).

For multi-question forms, keep `textareas` and `inputs` in the same order the page presents them.

© Klajdi Kolaj · MIT · hashgraph-online/awesome-codex-plugins

Similar plugins

Plugins catalog →

From the same set391

The whole set →
voicemoat-skills voicemoat-skills — a collection of 26 skills for LinkedIn and Twitter drafting, draft audits, and post analysis. Runs locally in your chat without accounts or API keys. CX Codex ★ 1,596repo stars vidseeds vidseeds connects Claude Code and Codex to VidSeeds.ai to prepare SEO metadata for existing videos and publish them across platforms. Use it before uploading a finished clip. CX Codex ★ 1,596repo stars varg Connects the varg MCP server for generating video, images, voice and music, plus a skill for finding ready-made AI video tutorials. CX Codex ★ 1,596repo stars vals Build and deploy serverless TypeScript on Val Town. It adds skills for HTTP vals, cron jobs, SQLite, email, OAuth, and React UIs directly in your agent. CX Codex ★ 1,596repo stars unified-ai-system The unified-ai-system plugin for Claude Code and Codex connects to a self-hosted AI gateway that structures prompts and governs MCP tools. Docker testing requires no API keys. CX Codex ★ 1,596repo stars tokrepo-search The tokrepo-search plugin for Claude Code searches TokRepo for installable skills, prompts, MCP configs, and workflows. It bundles a skill and an MCP server. CX Codex ★ 1,596repo stars tokenchronicle tokenchronicle stores your work history in a local archive so you can search past sessions, track token usage, and resume interrupted work without rerunning costly prompts. CX Codex ★ 1,596repo stars thermal-fluid-research-workflow The thermal-fluid-research-workflow plugin for Claude Code and Codex checks CFD calculations and uncertainty and supports manuscript preparation for thermal-fluid research. CX Codex ★ 1,596repo stars

Project sponsors

Companies that keep this analytics open