career-ops 2.0 web — beta feedback (RC)

[santifer]

Home base for the 2.0 web RC. Drop bugs / papercuts / ideas here — or use the in-app "Report a bug" (bottom-left), which pre-fills a GitHub issue with no personal data.

Install (separate folder — keeps your real install safe):

git clone --branch 2.0.0-rc.1 https://github.com/santifer/career-ops.git career-ops-rc
cd career-ops-rc/web && npm install && npm run dev

Release notes: https://github.com/santifer/career-ops/releases/tag/2.0.0-rc.1

Reminder: it's an RC — not for your primary search yet; the CLI is unchanged; it never submits for you. 🙏

I.feel.lost.mp4

[bracketouverte]

UX

Background image makes the text difficult to read

[bracketouverte]

UX

User already picked a CLI for his resume (Claude), user should be offered to use the same here, as an option to save time.

[bracketouverte]

UI

Text alignment

[bracketouverte]

UI

Text barely readable

[bracketouverte]

Improvments

12 results, 4 still alive only. Using their API would be easy to verify before presenting to user: Add “Mark as expired”, for CO community?

I added CooperAI to my pipeline, then clicked on pipeline: empty. Came back to “explore” to go back to my search (paid with my tokens) and it’s not available. Work is lost. Very frustrating.

[bracketouverte]

Feature

Analytics doesn’t give any insight on tokens. Tokens consuption understanding is a real thing for the project.

[bracketouverte]

Workflow

Today’s page asks to finish my setup. I already gave my cv. screenshot of “CV” page and assistant asking for CV anyway

[bracketouverte]

UX

Manual eval shows a list of actions = useless for user.
Should give some useful insight (or just say it’s working, or pack the list in a textarea or scrollable box). A timer would be nice, or timestamp in front of each actions if kept. Goal: Ensure it keeps working.

UI

run ended with: 1. The CLI exited with an error — is it installed and authenticated? As a user, I have no clue on what to do next.

[bracketouverte]

Bug

Has been evaluaed, even if CLI exit error. No clue if this is a bug or not, can’t remove it.

Job URL: https://www.zoominfo.com/careers/jr107682/senior-manager-product-management?gh_jid=8581902002

[bracketouverte]

Improvement

Issue with the Explore feature, find 0 result. Same criterias, my scrapper finds 615 jobs

[arungupta1526]

i also face this same issue/bug. if your fork is public with working ui, can you send link for testing?

[santifer]

@bracketouverte — thank you for the thorough pass; this is exactly the kind of beta feedback that makes the web build better. Status on everything you flagged (all reproduced locally unless noted), landing in the next RC build:

Reproduced + fixed

• Readability — text washed out over the hero glow, low-contrast copy, and heading alignment: added a scrim behind the hero text, bumped the muted color tokens to meet WCAG AA, and fixed the alignment. Light and dark both.
• "Added a job, pipeline was empty, came back and my search was gone" — two bugs. Explore results now survive a reload and the mode toggle, and adding to the pipeline refreshes the pipeline view instead of showing a stale snapshot. Your add was never actually lost — it wrote correctly; the view just didn't refresh.
• "Today" asked me to finish setup / the assistant re-asked for my CV — the assistant now reads the same "what's already on file" signal the home screen uses, so it won't re-ask for a CV you've already given.
• The eval run showed a raw action list and looked frozen — steps are now in plain language ("Reading the posting", "Writing the report", "Saving to your tracker"), with a live timer so a multi-minute evaluation visibly progresses, and an auth error now points to a clear next step.
• A job marked Evaluated even though the CLI errored — tightened the check so a run that didn't finish cleanly is flagged for re-run instead of banking a confident score, and you can now remove a bad row from the tracker.
• Explore finding 0 while your scraper found many more — tracked in [web rc] Discover (free) does not have any results for me. I am able to get AI #1152: the UI was wrongly showing "all caught up" when the scan couldn't actually reach the company directories; it now reports honestly what it searched. Default coverage and date-handling improvements are being made in the core scanner, with relevance-ranked search on the roadmap.

Tracked (not in the next RC)

• Token insight in Analytics — per-run token cost now shows on each worker; a fuller Analytics breakdown is on the list.
• "Mark as expired" — good call, tracked as a follow-up.

Genuinely appreciate the time you put into this. 🙏

[bracketouverte]

Hey @santifer Happy to help.
Will test again on next RC.

Best, Mike

[rubicon]

Tried the 2.0 RC, really nice. /api/explore/add → addOffersToPipeline → the canonical scan.mjs writers is exactly the pattern I'd hoped for (no parallel writer), and seeing the providers/*.mjs architecture from #521 land is great.

One small gap I hit: addOffersToPipeline (and appendToPipeline) keep only url/company/title/location/source, so an offer can't carry a ranking signal. Would you be open to a small, generic enhancement that lets the canonical writer preserve an optional note/signal per offer? Nothing source-specific, just a field that survives to pipeline.md so the daily pipeline can see it.

What it unlocks: the highest-signal leads never come through an ATS API or an email alert. They live in the boards' own curated lists (LinkedIn "Top Applicant" + match %). I've been building a browser extension that captures those from my own logged-in session and POSTs them to /api/explore/add as a new source, basically the "browser transport" provider #521 anticipated. The signal field is what lets a Top-Applicant flag ride along. The browser side is ToS-gray depending on the site (e.g., LinkedIn), so I'd keep that entirely separate in my repos. The only thing I'd want upstream is that one generic writer enhancement. Happy to send it as a PR.

Congrats on the RC, this is a big step.

[santifer]

Update: the web UI now lives on main (alpha) — merged in #1451.

The release/2.0.0-rc.1 preview branch is now frozen and superseded: every fix that came out of this beta round is included on main, and the alpha ships with its own isolation infrastructure (own CI and versioning, excluded from the npm package — the CLI is untouched if you never run it).

To try it from main: git pull (or a fresh clone), then cd web && npm ci && npm run dev → http://localhost:3000. Still alpha, still opt-in, still local-first — the local web app runs entirely on your machine, and it never submits an application for you.

Keep the feedback coming right here — the bug reports in this thread directly shaped what landed. Thank you all. 🙏