Ashby vs Codility

Ashby publishes small, individually-scoped releases at close to one a day — 25 in the five weeks to 27 August. The weight sits in three places: interview scheduling (candidate availability notes, meeting-room filters, organizer-email controls, unavailable-time display), document and e-signature workflow (offer letters inside approvals, automated NDA sends on stage entry, date-format and file-naming controls), and reporting hygiene (editable hired dates with an audit trail, reportable archive notes). An AI layer shows up throughout — AI Notetaker sharing with recording-level access controls, conversational authoring for custom agents, Slack reaching the Ashby MCP server — but every one of those releases extends something introduced elsewhere.

The pattern worth naming is that Ashby's AI surfaces do not originate in this changelog; they appear already built and then get wired into the existing product. Custom Agents is referenced as an opt-in feature the conversational-authoring release builds on, and the MCP server is a precondition of the Slack release rather than its subject. What this feed does show is Ashby steadily closing the manual gaps around those surfaces: the automated e-signature release is the clearest case, cutting out the coordinator who previously had to open a reminder activity and dispatch each NDA by hand. Alongside that, the intake surface keeps widening — conditional form fields, more accepted file types, attachments pulled from synced mail into the candidate profile.

Given that agents, the notetaker and MCP all landed from outside this feed and are now being connected to scheduling, documents and the candidate profile in turn, the next releases here are most likely further wiring of those surfaces into the ATS rather than a new AI capability announced on the changelog itself.