CodexGuild DocsConnect coding agents to CodexGuild — MCP, REST and the codexguild skill
Quickstart Harness setup API reference

Guides

Freshness

Dated releases and breaking-change flags per topic, so your agent can answer "is this still current?" instead of guessing from training data.

Your model's training data has a cutoff. Freshness returns everything that shipped after a date you pick — typically that cutoff — with dates, version tags and a breaking flag.

Query a topic

bash
curl -s "https://api.codexguild.com/v1/freshness?topic=nextjs&since=2026-01-01&version=16" \
  -H "Authorization: Bearer $CODEXGUILD_API_KEY"
ParamRequiredNotes
topicyesnextjs, react, node, prisma, nestjs, typescript, vue, tailwindcss, postgresql, vite, … Package names are normalized.
sinceyesISO date. Use your training cutoff.
versionnoMajor version filter, e.g. 16.
json
{
  "topic": "nextjs",
  "since": "2026-01-01T00:00:00.000Z",
  "changes": [
    { "asOf": "2026-09-12T…", "title": "v16.3.7", "summaryMd": "…", "source": "RELEASE",
      "url": "https://github.com/vercel/next.js/releases/tag/v16.3.7", "versionTag": "v16.3.7", "breaking": false }
  ]
}

MCP: codexguild_freshness {topic, since, version?}.

How breaking is decided

The freshness worker flags a release as possibly breaking when its name or the start of its notes (first 500 characters) mentions breaking, removed or deprecated. It is a signal to read the notes — not a verdict: a major release with quiet notes may be unflagged, and a patch that deprecates one option will be flagged.

Tracked topics

bash
curl -s https://api.codexguild.com/v1/freshness/topics

Missing a library? Ask CodexGuild to track it:

bash
curl -s -X POST https://api.codexguild.com/v1/freshness/topics \
  -H "Authorization: Bearer $CODEXGUILD_API_KEY" -H "content-type: application/json" \
  -d '{"topic":"vite","sources":[{"repoUrl":"https://github.com/vitejs/vite"}]}'

The next worker run pulls its releases.

Tip: Good agent habit: before writing code against an API that might postdate the training cutoff, call codexguild_freshness for that topic. It costs one freshness call and prevents confidently-outdated code.

Deprecations

CodexGuild also pulls out the lines in release notes that deprecate or remove an API, along with the replacement when the notes name one. Browse them at /deprecations. Agents can query them with codexguild_deprecations { topic, q? } or GET https://api.codexguild.com/v1/freshness/deprecations?topic=react&q=hydrate. A sync refresh lists, per stack topic, the deprecations from releases in the window.