What's new

Agent notes: your agent stops repeating its mistakes

Coding agents forget everything between sessions, and what they do remember stays on one machine and in one tool. Now an agent saves a short lesson when it corrects a mistake of its own or learns an unwritten rule of the repository — and every session on that repository starts with it, on any machine, in any harness.

• Notes belong to the repository (its git remote), so Claude Code on your laptop and Codex on your desktop share them.
• Encrypted with a key per repository; credentials and anything our security scanner flags are refused, because notes are replayed into every session.
• On a team repository, an agent's note reaches teammates only after a person approves it.
• Read, edit, pin and retire notes in Dashboard → Notes. Stock keeps 10 notes for one repository; Stage 1–3 keep 50, 200 and 500 per repository.

@codexguild/mcp 1.8.0

The local MCP server reads the repository's git remote (dropping any credentials in the URL first) and sends it with codexguild_sync and the note tools, so notes follow the repository. npx may keep running a cached older version: use @codexguild/mcp@latest in your MCP config's args to get it right away.

Pull request checks on GitHub

Every push to a pull request in an imported repository is checked: added and updated dependencies against the package registries and OSV. A package that doesn't exist, was never published or is malicious — or a new critical/high advisory — fails the CodexGuild check; other findings are flagged for a look.

• Reads only manifests and lockfiles, at the PR's base and head commits.
• If the vulnerability database can't be reached, the check says so instead of passing.
• Make it a required check to block merges on a failure.

Measured: the same agent with and without CodexGuild

Two rounds of 20 tasks per configuration, Claude Code with Sonnet, shell and web off for everyone, deterministic graders. On API changes newer than the model's training data, the agent solved 5 of 26 tasks without CodexGuild and 25–26 of 26 with it — at a lower cost per solved task.

Analyze a project, then let your coding agent fix it

A project's analysis checks every dependency version against OSV advisories, APIs deprecated or removed in the versions you run, new major lines and verified advisories. "Fix with coding agent" turns it into a brief your agent fetches over MCP; when it submits the fixed versions, CodexGuild re-validates them: verified or needs work.

Deprecated APIs in your own code, and upgrade plans

codexguild_scan_code finds APIs deprecated or removed in the versions you run — in your code, with file, line and the replacement — and runs after every sync. codexguild_upgrade_plan lays out the releases, breaking changes and removed APIs between your version and the target.

Stages, teams and GitHub projects

Four stages from Stock (free) to Stage 3. Track your projects' stacks from pasted manifests or GitHub (manifests and lockfiles only), get CVE and major-release alerts, and share projects with a team on Stage 3.