Prerequisites · Quick Start · How it works · What it does · Daily flow · Privacy · Contributing

A Codex job-search assistant. Track jobs in a single CSV, discover openings via LinkedIn + web search + optional Indeed, orchestrate referrals, tailor resumes, prepare application materials, and keep application state in one local workspace.

Scope on purpose: Codex handles the repetitive organization, drafting, browser navigation, and file preparation. You approve anything externally visible or judgment-heavy: messages, emails, uploads, applications, sensitive screening answers, and final submissions.

This is intentionally prompt-first: Markdown instructions and local files, no helper programs or hidden services.

Looking for the Claude Code version? See claude-linkedin-assistant.

Prerequisites

You need these before the job-search flows can work end to end:

• Codex app - open this repository in the Codex desktop app so Codex can read and write the local workspace files. The browser-only experience is not enough for this repo because the assistant needs local resumes, tracker files, application folders, and git commits.
• Codex Chrome extension - this lets Codex use your signed-in Chrome session for LinkedIn, Gmail, company career pages, and ATS forms. Set it up from Codex with Codex -> Plugins -> Chrome, follow the setup flow, then confirm the Chrome toolbar extension shows Connected.
• Chrome signed in to LinkedIn - use the same Chrome profile where the Codex extension is connected.
• Git - used to clone the repo and create end-of-day commits.

Optional:

• Indeed account - sign into indeed.com in the same Chrome profile if you want Indeed discovery or Indeed profile optimization. Indeed is disabled by default and can be enabled during jobs setup.

For resume uploads and referral/application attachments, also enable file access:

Chrome -> Extensions -> Manage Extensions -> Codex extension -> Details
Allow access to file URLs

Quick Start

1. Clone and open in Codex

git clone https://github.com/FarzamHejaziK/codex_linkedin_assistant.git
cd codex_linkedin_assistant

Open the folder in Codex. Codex reads:

AGENTS.md

That file points to the project skill:

.agents/skills/jobs/SKILL.md

2. Add your resume

Best path: attach/upload your resume in Codex chat during jobs setup, or paste its absolute local file path. Codex should copy it into resumes/ for you.

You can also put one or more resume files in:

resumes/

Supported formats:

• .pdf
• .tex
• .docx
• .md
• .html

3. Add search preferences

Codex can create this for you during setup by asking about target roles, locations, salary, work authorization, sponsorship, and dealbreakers.

Optional manual file:

resumes/search_profile.md

Use it for must-haves, deal-breakers, locations, salary floor, level, industries, company stage, and role preferences.

4. Confirm browser file access

For application uploads and referral materials:

Chrome -> Extensions -> Manage Extensions -> Codex extension -> Details
Allow access to file URLs

5. Run setup

jobs setup

If no real resume is present yet, setup should pause and ask you to upload one here, paste an absolute local path, or drag a file into resumes/. After that, Codex should ask onboarding questions and create the search/profile files itself.

Setup also asks whether you want optional Indeed support:

• Choose no or later to keep the workflow LinkedIn + web/company-board search only.
• Choose yes to add Indeed discovery.
• If Indeed discovery is enabled, profile optimization is offered as a separate optional step. Every public-facing profile edit is shown before saving.

6. Run daily

jobs daily

jobs daily is the main orchestrator. It checks the tracker, applies to ready jobs with approval, runs referral workflows, discovers new jobs, instant-applies no-referral jobs with approval, commits, and summarizes the day.

How it works

The assistant is built around local files:

• job_tracker.csv is the source of truth.
• resumes/ describes who you are and what jobs fit.
• profile/ stores reusable application fields and screening answers.
• base_resumes/ can hold editable resume sources.
• applications/ stores per-job materials.
• outreach/ stores referral contact logs.
• .agents/skills/jobs/references/ contains workflow instructions.

There is no database. Open the CSV and folders to inspect the current state.

At the start of every operational jobs ... workflow, Codex should confirm the Codex Chrome extension/tool is exposed and connected, open LinkedIn, and verify the active LinkedIn profile name matches the name on the resume. Installing the Chrome extension is not the same as exposing a working Chrome connection to a Codex session; both have to be true. If Chrome-specific tools are not exposed or not communicating after discovery/connection attempts, Codex should explain the exact state and help you reconnect Chrome instead of falling back to Computer Use. If the resume is missing, setup pauses for resume intake first.

LinkedIn remains the primary discovery source. Indeed is optional. When enabled, jobs find adds Indeed search, best-effort Indeed recommendations, and user-pasted Career Scout recommendations after the LinkedIn search pass. If Indeed is blocked or unavailable, the rest of the workflow continues.

Repository Structure

Codex_Linkedlin_assistant/
├── AGENTS.md
├── CONTRIBUTING.md
├── LICENSE
├── MAINTAINERS.md
├── README.md
├── REQUIREMENTS.md
├── SECURITY.md
├── job_tracker.csv
├── .gitignore
├── assets/
│   ├── logo-animation.gif
│   └── logo.png
├── .github/
│   ├── CODEOWNERS
│   └── PULL_REQUEST_TEMPLATE.md
├── .docs/
│   ├── PRD.md
│   └── plan.md
├── .agents/
│   └── skills/
│       └── jobs/
│           ├── SKILL.md
│           └── references/
│               ├── apply.md
│               ├── browser-preflight.md
│               ├── check.md
│               ├── daily.md
│               ├── find.md
│               ├── indeed.md
│               ├── overview.md
│               ├── referral.md
│               ├── resume-backends.md
│               ├── setup.md
│               ├── tracker-schema.md
│               ├── workspace-files.md
│               └── writing-style.md
├── resumes/
│   ├── README.md
│   └── search_profile.example.md
├── profile/
│   ├── personal_info.example.json
│   └── screening_answers.example.md
├── base_resumes/
│   └── README.md
├── applications/
│   └── README.md
└── outreach/
    └── README.md

What it does

Intent	What it does
jobs setup	Verifies workspace files, tracker schema, resume intake, resume backend, and browser preflight
jobs check	Shows dashboard, deadlines, ready-to-apply jobs, and outreach queues
jobs find	Searches LinkedIn Jobs in Chrome first, supplements with web/company boards and optional Indeed, or intakes a pasted job link
jobs referral	Handles replies, referral materials, email-vs-LinkedIn decisions, follow-ups, outreach, and deadlines
jobs apply	Prepares materials, tailors resume when possible, fills forms, uploads files, and submits after approval
jobs daily	Runs the daily sequence and commits at the end when appropriate
jobs indeed-setup	Enables/retries optional Indeed discovery or optimizes the Indeed profile from local resume/profile data

There is no standalone jobs add or jobs update.

Daily flow

1. jobs check
2. jobs apply        # ready jobs
3. jobs referral     # replies, follow-ups, outreach, deadlines
4. jobs find         # LinkedIn-first discovery, optional Indeed, and manual-link intake
5. instant apply     # newly found no-referral jobs, with approval
6. commit
7. summary

Resume Backends

Backend	Use when	Notes
LaTeX	You maintain .tex resume sources	Codex can edit source and use local LaTeX tools if available
DOCX	You maintain Word-style resumes	Codex can use available document tools or prepare edits for manual export
Markdown/HTML	You want simple editable sources	Codex edits source and uses available export tools
PDF-only	You only have a final PDF	Works as an attachment, but true tailoring needs editable source

Codex must never invent experience. Tailoring means truthful emphasis and wording, not fabrication.

Tracker Format

Do not change the header:

Priority,Company,Role,Location,Type,Salary,Status,Applied Date,Next Action,URL,Notes,Discovered Date,Referral Needed,Referral Status,Referral Deadline,Apply Via

Privacy

Private files are ignored by default:

• Real resumes
• Real profile data
• Screening answers
• Application folders
• Outreach contact logs
• Base resume sources

Do not commit private job-search data unless you intentionally change .gitignore.

Contributing

Pull requests only. Direct pushes to main should be blocked on the public project.

• See CONTRIBUTING.md for the workflow.
• See MAINTAINERS.md for the approval model.
• For security reports, see SECURITY.md and do not open a public Issue.

Design Docs

• .docs/PRD.md
• .docs/plan.md

Related

• Claude Code version: claude-linkedin-assistant

License

MIT. See LICENSE.