context-mode

Have you tried https://github.com/mksglu/context-mode? I prefer it over rtk / headroom (at least in Cursor). The stop hooks seem to work well / prevent the agent from blowing up its context window.

Since this site seems to have an allergy to information density and usability, here's the GH: https://github.com/mksglu/context-mode Some discussion about this from a couple of months ago: https://news.ycombinator.com/item?id=47193064 Similar tools in this space: RTK:CLI proxy that reduces LLM token consumption: https://github.com/rtk-ai/rtk 8v: One CLI for you and your AI agent. Posted here a few days ago: https://news.ycombinator.com/item?id=47914963 Headroom:The Context Optimization Layer for LLM: https://github.com/chopratejas/headroom Of these, it looks like RTK and 8v are somewhat equivalent, while headroom is complementary. Although this does perhaps go further than rtk/v8.

You mean this? https://github.com/mksglu/context-mode Is it actually good or is this an ad?

I assume they mean: https://github.com/mksglu/context-mode

Why? Doesn't have jokey copy. Any thoughts on claude-mem[0] + context-mode[1]? [0] https://github.com/thedotmack/claude-mem [1] https://github.com/mksglu/context-mode

I've setup one on Hetzner. I got it a dedicated email account (via agentmail.to). Installed couple of skills, last30days and context-mode being the most useful so far (https://github.com/mvanhorn/last30days-skill and https://github.com/mksglu/context-mode). The biggest unlock was wiring it up to my agency's whatsapp group - it's now basically a multiplayer chatgpt. Not a "personal" assistant, but more of agency's assistant. It can send ad hoc mails to our clients when asked, but also tells jokes when atmosphere is tense. Each day it checks it's own inbox and once a week it sends me a kind of social listening report, but those are kind of workflows easily reproducible elsewhere. I'm actually so bullish on the potential of openclaw kind of software I've built a desktop app for it, stagewhisper.io. It's like a Granola for your OpenClaw. It l

Six days ago I posted a write-up on Hacker News explaining how Context Mode reduces Claude Code's context consumption by 98%. I expected a handful of comments. I got 565 points, 107 comments, and the kind of feedback that makes you stay up until 4 AM shipping features. What's new: - Five platform adapters: Claude Code, Gemini CLI, VS Code Copilot, OpenCode, Codex CLI - Session Continuity: survives context compactions, restores state automatically (~3h sessions vs ~30 min) - ctx_batch_execute: one call replaces 30+ individual commands - Three-layer fuzzy search: Porter stemming, trigram substring, Levenshtein - FTS5 deduplication, background mode, SSL cert auto-detection Breaking: repo renamed claude-context-mode → context-mode, tools prefixed with ctx_. Install (Claude Code): /install context-mode Install (all platforms):

1st comment: 2 day old account, "is the real story here", summary -> comment -> question, general punchiness of style without saying that much. These llms feel like someone said "be an informal hacker news commenter" so they often end with "Curious how" instead of "I'm curious how" or "Worth building" instead of "It's worth building". Not that humans don't do any of this but all of it together in their comment history, you just get a general vibe. author reply: not as obvious, but for one thing yes literally em dash, their post has 10 em dashes in 748 words, this comment has 2 em dashes in 115 words. Not that em dash = ai, but in the context of a post about AI it seems more likely. And finally, https://github.com/mksglu/claude-context-mode/blob/main/cont... the file the author linked in their own repo does not exist! (https://github.com/m

No magic — standard Unix process inheritance. Each execute() spawns a child process via Node's child_process.spawn() with a curated env built by #buildSafeEnv (https://github.com/mksglu/claude-context-mode/blob/main/cont...). It passes through an explicit allowlist of auth vars (GH_TOKEN, AWS_ACCESS_KEY_ID, GOOGLE_APPLICATION_CREDENTIALS, KUBECONFIG, etc.) plus HOME and XDG paths so CLI tools find their config files on disk. No state persists between calls — each subprocess inherits credentials from the MCP server's environment, runs, and exits. This works because tools like gh and aws resolve auth on every invocation anyway (env vars or ~/.config files). The tradeoff is intentional: allowlist over full process.env so the sandbox doesn't leak unrelated vars.

Author here. I shared the GitHub repo a few days ago (https://news.ycombinator.com/item?id=47148025) and got great feedback. This is the writeup explaining the architecture. The core idea: every MCP tool call dumps raw data into your 200K context window. Context Mode spawns isolated subprocesses — only stdout enters context. No LLM calls, purely algorithmic: SQLite FTS5 with BM25 ranking and Porter stemming. Since the last post we've seen 228 stars and some real-world usage data. The biggest surprise was how much subagent routing matters — auto-upgrading Bash subagents to general-purpose so they can use batch_execute instead of flooding context with raw output. Source: https://github.com/mksglu/claude-context-mode Happy to answer any architecture questions.

Every MCP tool call dumps raw data into Claude Code's 200K context window. A Playwright snapshot costs 56 KB, 20 GitHub issues cost 59 KB. After 30 minutes, 40% of your context is gone. I built an MCP server that sits between Claude Code and these outputs. It processes them in sandboxes and only returns summaries. 315 KB becomes 5.4 KB. It supports 10 language runtimes, SQLite FTS5 with BM25 ranking for search, and batch execution. Session time before slowdown goes from ~30 min to ~3 hours. MIT licensed, single command install: /plugin marketplace add mksglu/claude-context-mode /plugin install context-mode@claude-context-mode Benchmarks and source: https://github.com/mksglu/claude-context-mode Would love feedback from anyone hitting context limits in Claude Code. NOTE: Because of the timezone issue, I’m resurfacing the same content here.

Every MCP tool call dumps raw data into Claude Code's 200K context window. A Playwright snapshot costs 56 KB, 20 GitHub issues cost 59 KB. After 30 minutes, 40% of your context is gone. I built an MCP server that sits between Claude Code and these outputs. It processes them in sandboxes and only returns summaries. 315 KB becomes 5.4 KB. It supports 10 language runtimes, SQLite FTS5 with BM25 ranking for search, and batch execution. Session time before slowdown goes from ~30 min to ~3 hours. MIT licensed, single command install: /plugin marketplace add mksglu/claude-context-mode /plugin install context-mode@claude-context-mode Benchmarks and source: https://github.com/mksglu/claude-context-mode Would love feedback from anyone hitting context limits in Claude Code.