August 6, 2026
AI search that runs the search it shows you
Type a prompt into cord's AI candidate search and it reads your brief back as filter chips. The chips and the search running underneath them had drifted apart in a few places. This release lines them up.
Fixes
- Keyword search: The public search showed a quoted phrase in the chip and ran the unquoted words underneath. "Account Based Marketing Manager" returned 17,034 people that way, against 1 for the phrase itself. Both now run the phrase, so expect lower and more honest counts.
- Skills and job titles: AI search was losing any skill or title spelled differently from cord's own list. Ask for "typescript" and it landed in the keyword box as loose text, because cord stores it as "Typescript". Matching is now case-insensitive, and titles resolve from the label you see on the chip, so "full stack developer" finds Full Stack.
- Refining a search: Adding one skill to a search built on "any of these skills" used to turn it into "must have this one", and the other skill chips disappeared from the readback. A new skill now joins the existing list instead.
- Search names: Short prompts could pick up a stray fragment in the search name, so "engineer" read back as "Software Engineers 77db840e". It was an internal safety token sitting at the end of the prompt. Measured live, "engineer" leaked in 11 of 12 runs before the fix and 0 of 12 after.
- Demo feeds: A demo opened from the hiring page had no sort set, so it fell back to whoever had logged in most recently instead of the best matches. It now opens on recommended score.