Upwork Autopilot

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

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

.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

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 scripts/launch-logged-in-chrome.sh

If you want a fully isolated browser profile, use:

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:

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

Main commands

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

Install for personal use

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

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 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.

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