career-ops

tracker

Quick read of where every application stands. Useful as a daily check-in or when preparing the weekly review. The full keyboard-driven UI lives in the Go TUI dashboard; this mode is the chat-side summary.

What it does

The tracker mode reads your tracker, data/applications.md, and shows every application with its current status in a single response. A statistics block follows: the total, the count per status, the average score, how many rows have a tailored PDF and a report, and, once you have applied somewhere, how fast your applications move from stage to stage.

When to use it

Use tracker for a daily fifteen-second status check. Use the Go TUI dashboard when you need to dig in.

Example

`/career-ops tracker` — output is a structured status summary in the chat.

What a run looks like

A tracker run prints the full applications table plus a statistics block in a single response, so you can read the whole search at a glance. Each row is one application with its company, role, score, current status, and whether a tailored PDF and an evaluation report have been generated.

Example
# | Date       | Company   | Role              | Score | Status    | PDF | Report
1 | 2026-06-14 | Anthropic | AI Engineer       | 4.5/5 | Interview | yes | yes
2 | 2026-06-18 | Vercel    | Applied AI Eng    | 4.2/5 | Applied   | yes | yes
3 | 2026-06-21 | Figma     | Product Eng, AI   | 3.9/5 | Evaluated | yes | yes

Total: 3   Applied: 1   Interview: 1   Evaluated: 1
Average score: 4.2/5   PDF generated: 100%   Report generated: 100%

An application moves through a fixed set of states: Evaluated (report written, decision pending), Applied (you submitted it), Responded (the company replied but no interview yet), Assessment (an online assessment or asynchronous screening is in progress), Interview (an active process), and then a terminal state: Offer, Rejected, Discarded, SKIP for roles that do not fit, or Hired once you accept an offer. To record a status change, ask for it in the chat or run node set-status.mjs --report <report#> <state> yourself, adding --on YYYY-MM-DD when it happened on an earlier day. A row without a report is selected by its company instead, node set-status.mjs "<company>" <state>, with --role when several rows share the company. The command rejects unknown states, locks the tracker while it writes, and logs the transition in data/status-log.tsv, the ledger the funnel-velocity statistics read, so use it instead of hand-editing the row.

To correct a note rather than add another one, pass the old note with --replace-note and the new text with --note. Without it, --note only appends, which leaves contradictions like not applied; applied in the row. The match is on a whole note between ; separators, and if neither text is in the Notes cell nothing is written:

node set-status.mjs --row 12 Applied --replace-note "not applied" --note "applied via referral"

Three more flags exist mainly for the Go TUI dashboard, which now records its status changes through set-status.mjs. --report-link N selects the row whose Report cell holds exactly one link to report N, and refuses malformed cells instead of guessing. --repair-status-log and --repair-followup apply when an Applied change is re-run on a row that is already Applied: they add the ledger entry or the follow-up reminder that the first attempt failed to write, and add nothing when it is already there.

node verify-pipeline.mjs reports Report not found when a row's Report cell links a file that no longer exists. npm run fix-report-links repairs those rows by changing only that cell to the tracker's usual "no report" mark. It does not regenerate the missing report. Preview first:

npm run fix-report-links -- --dry-run  # list the affected rows, write nothing
npm run fix-report-links               # apply; the tracker is backed up to .bak first

Every other cell, the row order and the line endings stay as they were. A Report cell holding anything other than exactly one link is listed for you to check by hand and left unchanged. Running it twice changes nothing the second time.

Checking whether postings are still open

Postings close while their rows sit in Evaluated or Applied. node check-liveness.mjs --tracker checks the posting of every Evaluated and Applied row; --status= chooses other statuses. It takes each posting from the row's URL cell or from its report's **URL:** line, and lists by number the rows that have neither.

To clear out the Evaluated rows whose posting has closed, preview first:

node check-liveness.mjs --tracker --discard-expired          # dry run: lists the rows it would move
node check-liveness.mjs --tracker --discard-expired --apply  # moves them

Only a posting judged expired moves its row, from Evaluated to Discarded, with the note posting closed YYYY-MM-DD. A row with an uncertain verdict stays as it is, and so does every Applied row.

Reading the lifetime numbers

For cumulative figures — the full funnel, scanner totals, portal coverage, and follow-up compliance — the mode runs node stats.mjs --summary and presents its output verbatim. That command reads your local files and costs zero tokens, so the numbers are never recomputed by hand or estimated from memory. Use the chat summary above for a fast daily read, and the stats command when you want the running totals across the whole search.

Exporting a repaired copy

Over hundreds of rows a markdown table picks up damage: mojibake placeholders, a score stranded in the status column, duplicate ids, stray pipes. node tracker.mjs sync finds and repairs these in its SQLite index, data/applications.db, without touching the markdown. tracker.mjs needs Node 22.13 or later (23.4 or later on Node 23) for that index; the markdown tracker keeps working without it. node tracker.mjs export is how you adopt that repaired copy of your own tracker:

node tracker.mjs export                            # rebuilt table on stdout
node tracker.mjs export --out repaired.md          # write to a file; an existing one is backed up to repaired.md.bak first
node tracker.mjs export --out repaired.md --force  # write even when something would be lost

export never touches data/applications.md unless you pass it as --out.

It preserves the layout it read, not just the values: your header row, columns career-ops does not map (Location, Via, URL or your own), the title, any preamble and trailing lines, and CRLF vs LF line endings. Extra columns come back in their own positions, though query cannot filter on them.

Anything it cannot reproduce is named on stderr. When that list is not empty, --out over an existing file refuses to write (exit code 1, nothing written) until you re-run with --force; when it is empty, --out backs up the existing file and overwrites it. What gets reported:

ReportedWhy it cannot be rebuilt
A cell outside the columns the header declaresThe header has no column to put it in
A line between the first and last table row, such as a heading or a second table's headerA single rebuilt table has nowhere to put it
A row belonging to a later table, such as an ## Archive sectionIt was indexed against the first table's header, so re-emitting it would move archived data into the active table
A cell whose value had to be rewritten to survive as a cell (a stray | comes back as │)The value itself changed

No losses reported does not mean the output is byte-identical. export emits the repairs sync made, and some of them are silent: aplicado is a recognized alias for Applied in templates/states.yml, so sync --check reports no corruption and the export says Applied anyway. Column-aligned cells also come back single-spaced. Before adopting an export, diff it against the file it replaces:

node tracker.mjs export | diff data/applications.md -

The full command reference, including sync, query and history, is in the core repo's scripts guide.

Gotchas

Status lives in the Status column of the tracker (data/applications.md), not in the report file. Changing it by hand skips data/status-log.tsv: funnel-velocity still sees the new status, but not when it happened, so the change is missing from the stage-velocity timings, and a row that later ends in Rejected loses the stages it passed through. Use set-status.mjs, the chat, or the Go TUI dashboard's status picker, which runs the same command.

On this page