Developers ship Chrome MCP, repo-graph search, and token compression for Claude Code and Codex

• Browser control is getting pulled into the agent toolchain through MCP servers, with LLMpsycho's Chrome MCP post pointing to Chrome DevTools MCP for browser control, console logs, screenshots, traces, and performance debugging.
• Repo context is getting its own preprocessing layer, with LLMpsycho's knowledge-graph post linking to Understand Anything, while the LLMDevs repo-packaging post shows separate demand for exporting repos into Markdown or JSON for agents.
• Token spend is turning into a product surface, not a footnote: vincent_koc's tokenjuice release pushed support to 99 integrations, while steipete's skill-cleaner post and a ClaudeCode Reddit breakdown both framed prompt bloat and cache misses as avoidable costs.
• Developers are also splitting agent workloads by role, with the openclaw advisor-mode thread describing a cheap worker plus expensive reviewer pattern instead of running top-tier models for every turn.

Chrome DevTools MCP is now being passed around as a drop-in way to give Claude Code, Cursor, and Copilot a browser. You can also browse Understand Anything, which turns a repo or docs set into an interactive knowledge graph, and scan tokenjuice, which exists for one unglamorous reason: less terminal sludge for agents. The weirder reveal came from community threads, where a Claude Code cache-cost post quantified how session changes blow up token spend, and an openclaw discussion argued for pairing a cheap worker model with an expensive reviewer only at decision points.

The Chrome MCP pitch is simple: stop treating the browser as a separate manual step. According to LLMpsycho's post, the server exposes browser control, console logs, screenshots, traces, and performance debugging to coding agents through MCP.

That lines up with the project's own framing in the GitHub repo. In practice, it pushes browser verification closer to the same loop as code edits and test runs, which is why this category keeps showing up next to Codex and Claude Code workflows.

Steipete's recent Codex posts show the adjacent pattern: agent runs that already mix repo instructions, VM access, computer vision, and cloud execution. His autotriage setup routes issues through repo-specific guidance and live testing, while his cloud setup offloads Codex into remote Firecracker boxes for longer runs.

The repo-context layer is splitting in two directions.

• Understand Anything, linked by LLMpsycho, builds an interactive knowledge graph from a codebase or docs set, then exposes search and question-answering across Claude Code, Codex, Cursor, Copilot, and Gemini CLI.
• RepoPrompt, surfaced in RepoPrompt's repost and another RepoPrompt repost, sits closer to prompt assembly, packaging repository context so agents can actually consume it.
• The LLMDevs packaging post shows the same problem from another angle: developers want local Markdown or JSON snapshots of a GitHub repo, not just raw file trees.
• A separate LLMDevs thread pushed on the next obvious question, whether the prompt should say what was skipped, stale, or guessed instead of only listing what got packed.

The interesting part is not that any one tool exists. It is that repo ingestion is turning into its own mini-stack: graph the codebase, snapshot the right files, and tell the model what context is missing.

Tooling for coding agents is getting brutally pragmatic about tokens.

tokenjuice, per vincent_koc's release post, now supports 99 integrations including Codex, Claude Code, Cursor, OpenCode, Copilot, Gemini CLI, Devin, and OpenHands. Its whole job is to compress terminal output before it hits the model.

Steipete's post makes the same argument at the instruction layer. Skills that "write books" get loaded into every context window, so he published a cleaner that finds the worst offenders in skill descriptions.

The cost side is not hypothetical. A ClaudeCode Reddit post tied Anthropic's published prompt-caching prices to five cache-busting actions in live sessions, including adding an MCP server mid-session, switching models, editing CLAUDE.md, toggling fast mode, and pasting an image. thsottiaux's Codex note about drained limits then gave the same theme an operational version: a cache-hit-rate regression was enough to burn usage limits faster until OpenAI rolled it back and reset accounts.

The openclaw thread adds one more layer to the stack: model routing inside the agent itself. According to the Reddit post, ClawCodex runs a cheap worker for file reads, edits, and test runs, then calls a stronger reviewer at decision points and returns short "Gaps / Risks / Do-next" guidance. The linked repo is clawcodex.

That thread also claimed two execution modes:

• server-side, using an Anthropic advisor beta header for a single roundtrip
• client-side, intercepting a tool call and making a separate advisor request to any configured provider

The same community is also pushing on longer-lived state. The HuBrIS LocalLLM post described a memory system that separates semantic memory from autobiographical memory, logs compaction effects, and lets the agent recall or close subjects across sessions.

One reason this infrastructure boom matters is that the edge cases are moving out of theory and into reproducible bugs. In a ClaudeCode Reddit report, one developer traced repeated failed MCP tool calls to a single empty-string parameter: if any param value was "", Claude Code allegedly erased all params and invoked the MCP tool with none.

The post included both a repro repo and a filed Anthropic issue. Once agents depend on browser MCPs, repo packers, compression layers, and advisor calls, small protocol bugs start looking expensive fast.