Terminal workflow

The terminal side was part of the product. So it gets its own page.

You were right to call out the original terminal setup. It mattered. The repo is not just a browser dashboard — it is also a command-driven system for scans, batch work, PDF generation, and a proper TUI pipeline view. This page puts that value back on the table.

Open browser pipeline See all product features

Why keep it

Fast pipeline triage when a web dashboard feels too slow or too decorativeA natural home for scans, batch evaluation, and repo-native workflowsBetter fit for high-volume review and ops-style cleanupMatches the spirit of the original project instead of flattening it into a simple brochure site

Positioning

The browser UI is the clean front door. The terminal workflow is the power lane when you want speed, volume, and less chrome.

Key terminal flows

These come from the actual repo and fork, not from me inventing hacker wallpaper.

Command

Terminal dashboard

The original repo ships a real Go TUI for browsing and updating the pipeline. That should be treated like a premium operator surface, not buried in docs.

cd dashboard
go build -o career-dashboard .
./career-dashboard

Command

Sample Telegram intake

Good for smoke testing the Kody-specific intake flow and verifying the artifact bundle path without touching a real listing.

npm run telegram:intake:sample

Command

Real URL intake

This is the CLI/operator version of what the browser intake page now does for you.

node scripts/kody-telegram-intake.mjs --url='https://jobs.example.com/role' --company='Company' --role='Account Executive'

Command

Resume render only

Useful when you want to check the document engine separately from the full job evaluation flow.

npm run render:resume:ae
npm run render:cover:sample

Slash-command layer

The original repo is built around career-ops modes. Those are part of the product story.

Mode/career-ops — show commands and entry points

Mode/career-ops scan — search configured portals for new roles

Mode/career-ops pdf — generate ATS-oriented resume output

Mode/career-ops batch — process multiple offers in parallel

Mode/career-ops tracker — inspect pipeline status

Mode/career-ops apply — support application prep without blind submission

How it fits the site

Browser and terminal should complement each other, not compete.

Use the browserWhen you want a clean intake form, pipeline overview, or shareable bundle view.

Use the terminalWhen you want scans, batch processing, quick artifact work, or dense pipeline review.

Use bothRun intake and generation through whichever surface is faster, then review and decide from the UI that fits the moment.