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 every file in reports/ and produces a structured summary grouped by stage: applied, evaluated, interview, rejected, discarded. Counts per stage, recent activity, and overdue followups are surfaced in a single response.
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.
# | 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), Interview (an active process), and then a terminal state of Offer, Rejected, Discarded, or SKIP for roles that do not fit. To record a status change, ask for it in the chat or run node set-status.mjs <report#|company> <state> yourself, adding --on YYYY-MM-DD when it happened on an earlier day. 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.
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.
Gotchas
Status lives in the Status column of the tracker (data/applications.md), not in the report file. The Go TUI dashboard's status picker also updates that column, but it does not log the transition in data/status-log.tsv the way set-status.mjs does. funnel-velocity still sees the new status, but not when it happened: the change is missing from the stage-velocity timings, and a row that later ends in Rejected loses the stages it passed through. Use the command for any change you want those figures to include.
Related
project
Builders accumulate ideas faster than they can ship. project mode scores a portfolio project idea against your target roles, your existing portfolio, and the time investment, surfacing whether it is worth building.
patterns
Reads your rejected and discarded applications and surfaces patterns — JD shapes that score high but never convert, archetype mismatches, comp-band issues. The output is a calibration signal for your targeting filter.