What's new

September 15, 2026

• The Dashboard reads the search as a job. Three new sections. Where they go: the funnel from postings seen through scored, matched at your floor, drafted, applied, screen or beyond, and closed — each step as a share of the one above. Hit rate by search: the share of each search’s postings that reached your floor, the free way to tell a thin market from a weak query. What it has cost this cycle: credits spent, per match found and per application sent, from the same reading your plan’s meters use.
• Resumes: every document by application, yours beside ours. The Resumes page now groups every document by application — the tailored resume, cover letter and prep packet Jobably wrote (ours) beside the final you actually sent (yours: upload it on the group under your own filename). Diff a draft against your master, or against your final to see what you changed by hand. Revise reopens the studio with your decisions kept; Re-draft from scratch discards them and queues a fresh draft. A final you actually sent can be marked an exemplar, and later drafts learn its voice and structure — a draft nobody sent cannot.
• A Screen stage, and what came back is its own axis. The Board gains a Screen column between Applied and Interview for the recruiter screen or phone call (optional — straight to Interview is fine). From Applied on, every card has an “ended:” row — rejected, withdrawn, accepted — because their decision is a different fact from how far you got. An ended application leaves the columns for a Closed list under the board that says both: rejected · reached interview. The Dashboard’s new “What came back” tiles tally still open, rejected, withdrawn, accepted, the average days to hear back and the share answered at all.
• Pursuing: everything between “I want this” and “I sent it”, in one place. A new Pursuing screen, between Matches and Resumes in the navigation. Each posting you are pursuing shows its stage — Queued → Drafted → Reviewed → Final → Applied — worked out from what actually exists, and one button that changes with the stage: Tailor resume, Review & finalize, Decide & build, Mark applied. Drop returns it to Matches. Expand a row for the reasoning behind the score and what the posting is buying, the full description, and your documents. The Board’s Pursuing and Tailored columns now mirror this screen instead of carrying their own controls.
• Profile moves onto the left navigation, with Master Resume and Your Bio under it. Profile is now the first section in the left navigation — folding open to Master Resume, Targeting, Interview, Exclusions, Accomplishments and a new page, Your Bio — instead of hiding behind the avatar menu. Your master resume lives under Profile (it is who you are); Resumes keeps your tailored drafts. Your Bio is a few sentences in your own voice that your cover letters speak in and that doubles as a draft for your LinkedIn About; “Propose a draft from my record” writes one from your resume and interview answers, and saving runs the same no-fabrication check as a tailored line — a number that is not in your record is refused by name.
• Tailoring now leads with what the posting is buying. Every score now reads the posting’s orientation from its responsibilities — is the employer buying a leader (own, define, build the team), a doer (execute, coordinate, maintain), or an analyst (model, forecast, report)? A Director title on a doer description is a doer posting. The why-this-score panel shows the reading; it never moves the score. Tailoring and the studio order the bullets within each role to lead with it — order and emphasis only, never a changed claim — and every draft says what the posting reads as, what the draft reads as, and flags a mismatch for you to consider.
• An application that has gone quiet shows its age, not a nudge. Five days after you mark a posting applied with nothing back, its Board card and the Dashboard now say how long it has waited instead of asking you to follow up — on most application portals there is nothing to send, and the count is for knowing when to write one off. The Dashboard section is now “Waiting on a reply”.
• Matches opens by stating what the scan is looking for. A panel above your matches says, in plain words, what your searches fetch — the roles and seniority, where, the employer size floor, and the score a match must clear to be shown — and expands to each search’s title phrases, description filter, how many postings it has found and when it last ran, plus the employers and titles you never see. It is read from your saved searches, so it always describes what actually runs.

September 4, 2026

• One tailored resume is one tailoring credit. Tailoring a long resume takes many model calls, and each call was counting as a credit — so a plan’s monthly tailoring allowance ran out after a handful of resumes. A tailored resume now costs exactly one credit: the one-shot tailor, or a studio session including its build and any revision. Your usage history is unchanged, and your credit count has been reset so the earlier over-counting does not carry into this cycle.

September 3, 2026

• The tailoring studio: tailor your resume with Jobably beside you. Tailor resume now opens a studio instead of running in the background. Jobably reads the posting, then walks your resume line by line and role by role, proposing rewordings and additions from your accomplishment bank with the reason each one serves this posting. You accept, reword or keep every line; any line can be edited or left out of the draft. On your own connected model you also get structure and layout recommendations and a headline aimed at the role. Every proposal is checked against your record before you see it, and anything held back says why. Build the document when you are done: your own Word file, a matching cover letter, and the same read-before-you-send step. Reach it from Resumes → Tailor for a job in the left navigation, or from any match or board card.
• Jobably Swipe: review your matches from your phone. A small installable app at swipe.jobably.com, for one job: every posting your searches found and you have not judged yet, dealt as a card that reads like a profile — company, role, pay, the score and why. Swipe right to keep it under Matched on your board (even one that scored below your floor), left to pass with a reason that tunes future scores; undo is one tap. The Searches tab lets you change threshold, cadence, location and pause from your phone. Signs in with your Jobably account, including Google and Microsoft. Everything else stays in the full app.
• Installing Swipe is one tap, and the deck shows you the gesture. Where your browser offers to install, a banner at the top of Jobably Swipe adds it to your home screen in one tap; the Account tab has the same button, and the exact steps for your phone when the browser offers none (Safari: Share → Add to Home Screen). The ✕ and ♥ buttons now stay on screen whatever the card’s length, the pass-reason picker slides over the card instead of replacing them, and the first card of a session nudges right and left with its Keep and Pass stamps so the swipe shows itself. Swipe also has its own place on jobably.com — first in the menu.
• Every score explains itself. Click any score — on Matches, the Board, a card’s drawer, or the Dashboard — and a panel shows the written rationale, what the scorer found on seniority, location and pay, and where to change the things that produced it: your interview answers, targeting and exclusion lists, a search’s threshold, or your Matches floor. Re-score the posting from the same panel once you have.
• Your searches now look like they are searching. The Dashboard and the Searches page show the work as it happens: what is scanning right now, when the last sweep ran, when the next one is due, how many postings today’s sweeps checked and how many were new — and a feed of the recent sweeps themselves. Every search carries its own “last scan / next in” line, and the page keeps itself current without a reload.
• Search and notification settings are yours to set. Settings → Notifications now holds a Matches score floor of your own (one number for every search, or leave each search’s threshold in charge), the email alert level, how often match emails arrive (as they are scored, once a day, or off), and how often the pipeline summary is sent (daily, weekly, or off).
• Dismissed postings leave the list. On Matches, a posting you dismissed while the status filter was on “All” stayed in the list until the filter changed, which read as the dismissal not taking. “All” now means every live status; dismissed postings have their own filter. The card drawer on the Board also names each status change correctly in its history.
• Connected assistants can run the studio too. Seven MCP tools open a tailoring session, run the review, read every proposal with its reason and guard verdict, save your decisions (accept, reword, keep, leave out, headline, section order), build the document, or start over — the same session the app shows, so you can switch between Claude and the page at any point. tailor_resume still queues the one-shot background draft.
• Numbers on a line can no longer drift. In the studio, a reworded line must carry exactly the numbers it had — a headcount, a team size, a count of suppliers — not only the dollar amounts and percentages the provenance check already protected. A proposal or an edit that changes one is refused with the reason.

September 2, 2026

• A section kept in your own words now says why. When a tailored draft leaves a section exactly as you wrote it, the reason is shown beside its name: there was nothing to tailor, the time budget ran out before that section’s turn, or every rewrite failed the no-fabrication guards. A section skipped on purpose and one that ran out of time are different facts, and they are no longer shown as the same one.
• Long sections on your own model no longer come back untailored. On a connected frontier model, a dense section could hit the output limit mid-sentence, and every retry hit it the same way — the draft then kept your original wording and said only that the reply was invalid. The limit now scales with the model and the section, a cut-off reply is retried with more room, and the reason beside the section says it was cut off rather than blaming the reply. If nothing at all could be tailored, the run fails with a try-again instead of handing your own resume back as a draft.
• Review items can carry a caution, and the revision is held to it. When a suggested phrase can go in only so far, the review panel names what must not be claimed. Approving the item applies that limit to the revision as well: the rewrite is bound by the caution, not just informed by it. A revision that drops a line you already approved now restores it and tells you.

August 30, 2026

• Review a draft before you send it: approve, decline, or reword each change. Beside every tailored resume, Jobably now lists what the posting asks for that the draft doesn’t say — sorted by whether your own record can support it, with the evidence quoted. Approve the items you stand behind (or supply your own wording), and only those lines change; everything you didn’t touch comes back exactly as it was. Changes that can’t be made truthfully are declined with the reason, and any edit you didn’t ask for is reverted automatically. Available on Matches and the Board, and to connected assistants as revise_tailored.
• Drafts tell you everything they did — and did not — do. A tailored resume now shows which sections kept your original wording, advisory style notes (observations, never silent corrections), and its mechanical scorecard summary — so a partly-tailored draft can never pass for a fully tailored one.
• A tailored resume tells you which layout it was rendered with. Drafts are normally rendered into your own Word master so your fonts and layout carry through. When that is not possible — the master could not be read, or was not a Word file — the draft is built from a clean generic layout instead, and the Matches and Board pages now say so beside the download, with the reason. Before, both cases looked identical.
• Every change to a search is recorded — including who paused it. Creating, editing, pausing, resuming or archiving a search now leaves a record of what changed, whether you did it from the app or through a connected assistant, and when — and Jobably’s own automatic pauses are recorded alongside. Ask for a search’s history at GET /v1/searches/{id}/audit. Resuming a search also clears its old automatic-pause note.
• Score threshold and email alert level are named apart. A search’s score threshold decides what appears on Matches; the email alert level in Settings decides which of those you are emailed about. Both places now say which number they are and point to the other, so a change to one is never mistaken for the other.

August 27, 2026

• Matches below your score threshold are counted, never silently hidden. When your search’s score threshold keeps matches off the Matches page, a strip now says exactly how many — “N matches scored below your search’s score threshold” — with a Show them link that reveals every one in place, badged “below threshold” so you can tell them apart. Nothing was ever deleted; now nothing is invisible either. The Board’s Matched column shows the same count and points to Matches, and connected assistants get the count on every list_matches call plus an includeBelowThreshold option to read the hidden ones.

August 12, 2026

• The accomplishment bank is now a pill editor. Profile → Accomplishments shows every entry as its own pill, so you can see exactly where one accomplishment ends and the next begins. Press Enter to add one, paste a whole list to add one entry per line, and remove any entry with a click. Commas never split an entry — “Negotiated $4.8M savings, 20% on $24M of spend” stays one accomplishment, exactly as tailoring will use it. Each entry is stored individually, and the count on screen is the count that is saved.
• Tailoring handles competency sections that span multiple lines. A Core Competencies block that wraps across several lines — the way most resumes format it — now reorders cleanly toward the posting. Every term keeps your own spelling, terms never merge across line breaks, and the no-fabrication guard reads the list term by term.
• Adding accomplishments from an AI assistant is more forgiving. The add_accomplishments MCP tool now accepts the bank as a proper list, as a pasted block with one accomplishment per line, or as a JSON-encoded list — whichever shape your assistant sends. Entries are never split on commas, duplicates are skipped, and unusable input gets a clear error instead of a silent guess. The tool reference shows worked examples for every argument shape.

August 11, 2026

• Import your career history from LinkedIn. Profile → Accomplishment bank now takes your LinkedIn data export. Ask LinkedIn for your archive under Settings → Data privacy → Get a copy of your data, choose the full archive, and upload the zip they email you. Every role description you wrote comes in as accomplishments the tailor can draw on — usually far more than fits on a resume, which is what lets a tailored draft reach for the right result instead of the one that happened to be on the page. Nothing is replaced: entries are added, duplicates skipped, and the count is reported.
• Tailored resumes carry your name and contact details. Your name, email and phone now come straight from your master resume and appear at the top of every tailored draft, exactly as you wrote them.
• Tailored resumes tell you what they could not cover. Beside a finished draft you now get the list of things the posting asks for that your record does not evidence. The draft never claims them, and knowing them before you apply is the point — it is also the fastest guide to what is worth adding to your accomplishment bank.
• Core competencies stay true to your record. A tailored resume now only lists competencies that appear in your own master resume, ordered by what the posting cares about. A skill the record cannot back never appears, so nothing on the page is a claim you would have to defend cold in an interview.
• More of the engine is tunable without waiting for a release. The models behind resume parsing, saved-posting capture and interview prep, along with the prep research budget and tailoring retry limits, are now operator settings.

August 9, 2026

• New searches get time to find their footing. A new search now has a couple of days to find its first matches before it can pause itself, and a search that has already found matches keeps running through quiet periods rather than pausing at all.
• Searches that had been inactive resume reliably. A search you had paused for a while now picks up where it left off on its next run.
• Filters behave the same everywhere. Every filter is available in the app, over the API and through a connected assistant, and behaves identically in each.

August 8, 2026

• Every search filter now has a control. Under “More filters” when you create or edit a search: years of experience, work type, company size, industries, companies to include or skip, and title keywords to skip. Years of experience is the one worth setting — it is the level filter most company career sites use, and those are where most of your matches come from. Job-board levels are individual checkboxes now, so you can pick exactly the levels you want.
• Search for contract and part-time work. Searches are no longer limited to full-time roles. You can also choose whether to include staffing agencies, and set a maximum company size as well as a minimum.
• A comma between search terms means “or”. Write your target titles as a list — procurement lead, sourcing director, vendor manager — and the search looks for any of them. The query helper shows you how your query was read, and flags a stray word beside an “or” list, which is usually not what you meant. Capitals make an operator: type OR, AND or NOT to combine terms.
• The simple editor leaves complex queries alone. A query with brackets now opens in the advanced editor rather than being simplified into chips, so what you wrote is what runs.
• Clearer answers when a search cannot work. Description filters are checked when you save, and you can see how yours will be read. If a search cannot return a result, you are told why — during setup too, which also now uses the locations you gave rather than assuming a country.
• Results say when there are more to see. A one-off search that hits its limit says so, with a total where we can get one, and you can choose which supply to search: company career sites, job boards, or both. Connected assistants can use every filter, and your exclusions apply automatically.
• Editing a search keeps all of its filters. Filters that have no control on the page — including any set for you by an assistant — survive an edit untouched.

August 7, 2026

• Board and Matches are one workflow. Tailor a resume straight from any board card, move cards back to Matched from Pursuing or Tailored (before you apply, every move is reversible), and sort columns by score or recency.
• The dashboard navigates. Score-distribution bars link to Matches at that score and up, pipeline chips open the board, “new since your last visit” survives a refresh, and scan results say “X new, Y already known”. Green / amber / red across search cards and credit meters.
• Archive searches. Done with a search? Archive it — hidden from the working list, restorable any time with its scan history intact. Searches are still never deleted.
• One-click re-score after profile changes. Saving your profile offers “Re-score my matches” on the spot — existing scores reflect the old rubric until you do. Example text in form boxes is now clearly marked “e.g.”, and the seniority menu is grouped by track.
• Onboard by chatting. A new AI-interviewer path through onboarding: answer in plain language, one question at a time, skip anything. It covers every topic the form covers and ends in the same place — your rubric in your words and your first search running. Switch to the form any time without losing answers.
• Searches fetch smarter, not wider. United States by default (blank the Location filter for worldwide), senior-only on job boards unless you say otherwise, your excluded titles dropped before scoring ever pays for them, plus company-size and description filters on the search form. First scans look back a full week.
• Work arrangement on every card. Remote, Hybrid, or On-site shown right below the job title — with the location beside it when it isn’t remote. Unknown stays blank rather than guessed.
• Search thresholds now truly gate. A match scoring below its own search’s threshold stays out of the default view, exactly as that search’s settings promise. Jobs you’ve acted on, unscored jobs, and extension saves are never hidden — set the score filter to 0 to see everything.
• The Chrome extension is on the Web Store. One-click install, automatic updates. Save any job page you open in Chrome to your matches — parsed, deduped, and scored against your rubric. Find it by searching “Jobably” or via the install link in the docs.
• Your intake powers your searches. The first-search query arrives pre-filled from your title keywords, and the Searches page suggests ready-to-run searches built from your questionnaire — your own words, one click to create, or Customize to adjust anything first.
• Resume-aware onboarding defaults. Your resume headline pre-fills the seniority floor and target titles — clearly marked as guesses, editable on the spot, and your edits always win. Threshold, cadence, and sources are editable during onboarding too.

August 6, 2026

• The onboarding interview. Ten open questions in your own words — your story, ideal role, non-negotiables, dealbreakers, what your resume undersells, what you never want to do again. Answers go into your scoring rubric word-for-word and stay editable on the Profile page.
• Location scoring, fixed. A strong-fit role you could not actually take no longer scores high. Wrong-country onsite roles cap at 3, out-of-area at 5, region-locked remote at 4, unstated locations at 5 — still surfaced, ranked honestly, with the gap named in the rationale.
• Compensation floors with teeth. A posting stating pay below your floor now caps at 5 — a consistent number instead of a vague “scored down”.
• Guided search builder. Boolean syntax is optional everywhere: three plain boxes — match ANY, must ALSO contain, must NOT contain — build the query for you, with an Advanced mode for hand-written expressions.
• Matches: filter by search and by date. See which of your searches found each match, and narrow to today or the last 3 / 7 / 14 / 30 days — alongside status, score, source, and engagement filters.
• Re-score any match. A per-match Re-score button with live progress; the fresh score lands on the card the moment it finishes. Finished statuses, including errors, can be dismissed.
• Connect your AI assistant in one paste. After creating an access token, Settings shows the complete connect command for Claude Code, Codex, or Copilot on Windows, macOS, or Linux — token already filled in. Revoked tokens stay visible, dimmed.
• Feedback that reaches us with context. The feedback bubble now sends the exact page you were on — filters and all — so reports can be reproduced first try.
• Onboarding and profile, sharper. Seniority floor covers every function, work arrangement is multi-select, industries to avoid sit beside preferred ones, title keywords you WANT join the rubric, and the resume preview shows the full parsed text. New accounts get a live first-scan card on the dashboard.
• Email, grown up. Branded, readable email throughout: a welcome note when you join, a what-happens-next note after onboarding, a Monday weekly digest (opt out in Settings), trial reminders, and payment notices. Sign-in codes can be resent from the login screen.

August 5, 2026

• Jobably Executive. A second plan for searches where timing decides: hourly scans, new matches scored automatically as they arrive, roughly five times the credits, up to 25 searches. Switch between plans any time from Billing.
• Application packages. Tailoring now produces a matching cover letter alongside the tailored resume — both under the same guarantee that nothing is ever invented about you.
• Tailoring that preserves your document. Tailored resumes are edits of YOUR document, not rewrites: your sections, your dates, your formatting survive, with four independent checks that reject any draft that drifts from the record.
• High-score email alerts. New matches at or above your threshold (default 8) email you right away — one digest per scoring run, never one email per job. Configurable in Settings.
• Interview prep packets. Prep now runs on your own Anthropic key with live web research: company brief, likely interview themes, STAR stories from your verified history, and outreach drafts you send yourself.
• Your own model keys, expanded. xAI and Ollama Cloud join Anthropic, OpenAI, and Google. Keys are verified with the provider before saving, and a Settings picker chooses which model runs your tailoring.
• Pay captured wherever it is stated. Salary ranges on scanned roles and hourly or project rates on contract gigs — never estimated; blank when the posting is silent.
• Credits and status you can trust. Live remaining-credit meters on the dashboard and Billing, persistent operation status on every match, and a public status page fed by real nightly checks.