Large Update: Rate Limit Radar, Project Hooks, and Safer Shells #218
zemaj
announced in
Announcements
Replies: 2 comments 2 replies
-
|
Oh, one thing we didn't mention - there's now an |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
In the current Validation harness, can we outsource the checks to a MCP? I have a custom MCP for Odoo that uses Jetbrains's Inspection interface. This is due to a few of the tools I have in PyCharm being able to work with Odoo's dynamic system. BTW, great work, I am a fan. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Since September 16, 2025 we’ve poured a mountain of improvements into Code - and as of the latest main build (September 22) they’re all live.
Terminal
Code’s terminal overlay has grown into a true command cockpit. Type
$ <command>to run it instantly in a dedicated shell window, or use$$ <task>when you want Code to draft the command first so you can approve, edit, or reject it. The overlay keeps native scrollback, mirrors every run into history, and still pipes through Code’s guardrails so you get human-level control with AI-level safety./limitsThe
/limitscommand evolved into a full dashboard that actively looks out for you. It renders synchronized hourly and weekly gauges, stores the official reset timestamps on disk so sessions resume accurately, and keeps the session footer in lockstep with reality. As you cross each threshold (50%, 75%, 90%), Code now raises in-chat alerts - “Hourly usage exceeded 75% of the limit. Run /limits for detailed usage.” - so you can throttle or swap models before the API responds with errors.RateLimitSnapshotEventand refresh automatically in the background, so the gauges stay correct even during long-lived sessions.Hooks
Project automation became dramatically more capable. In
config.tomlyou can declare hooks forsession.start,session.end,tool.before,tool.after,file.before_write, andfile.after_write. Each hook runs in the same sandbox as your session, outputs to its own exec cell, and receives rich metadata viaCODE_HOOK_EVENT,CODE_HOOK_PAYLOAD,CODE_SESSION_CWD, and more. Failures are surfaced but never block your main task.apply_patch, post notifications when a session shuts down) and specify per-hook timeouts, custom working directories, or environment overrides./cmd <name>now show up right in the slash menu, giving you one-keystroke access to smoke tests, migrations, bootstrap scripts, or deploy pipelines tailored to each repo.Validation
The validation harness received a full control panel. The
/validationcommand now exposes a polished interface where you can toggle the entire patch harness or specific tools - including the newcargo checkvalidator - without editing config files. If Code detects that a required validator (say,shellcheckoractionlint) is missing, it launches the terminal overlay with the recommended install command prefilled, so you can accept it, watch progress, and retry immediately.cargo checkpath works out of the box.TUI & Performance
Rendering in the TUI feels dramatically faster and clearer. History cells cache layouts and parsed metadata, wait-tool chatter collapses into the final exec output, and every run stamps its duration so you can skim outcomes at speed. The
statuspanel clears spinners once final answers land, bottom overlays clamp to the viewport, and the/updateworkflow now surfaces notices plus echoes the exact command that ran on your behalf./limitshas a refreshed layout with aligned color palettes, synchronized headings, and off-main-thread refresh logic to keep the UI smooth.CLI & Automation
Command-line ergonomics leveled up.
code resumeonce again restores paused sessions perfectly, shell completion scripts now reference thecodeshim everywhere, andscripts/wait-for-gh-run.shcan follow any GitHub Actions run - optionally dumping logs for failed jobs with a single flag. Logging defaults were tuned (WARNon file logs) to reduce noise without losing signal.code mcpsubcommand exposes the MCP server directly, withcode acpacting as a friendly alias for the same functionality.code-mcp-serverbinary automatically, so installing@just-every/codegives you the full MCP/ACP toolchain straight away.protocolVersionfields, making it easier for other clients to connect without fiddly patches.ACP + Zed
ACP integration is officially live. The Rust MCP server advertises
acp/new_sessionandacp/promptalongside Code’s classic tools, so Zed (or any ACP-capable IDE) can drive Code without touching the terminal. The new CLI aliases (code acp,code mcp) make setup trivial, and the documentation now covers minimal configs for Code, Coder, and Zed.docs/integration-zed.mdand the refreshed ACP docs walk through wiring Zed’s MCP transport into Code, including environment variables, permission flows, and launch commands.Ready to experience all of this?
Whether you’re spinning up the terminal overlay, exploring
/limits, or driving Code from Zed via ACP, we can’t wait to see what you build next!Beta Was this translation helpful? Give feedback.
All reactions