nowfound

Alternatives

Products that do what Context Surgeon – Let AI agents edit their own context window does

AI agents accumulate stale tool results — file reads, web fetches, bash outputs — in their context window. Every one sits there for the entire conversation, consuming tokens and degrading quality. The standard fix is auto-compaction: wait until full, then drop content indiscriminately. Context Surgeon gives the agent three operations — evict, replace, and restore — so it can manage its own context. It works as a transparent local proxy that intercepts API requests, assigns IDs to content blocks, and applies eviction directives before forwarding. The agent calls the tools via bash. The proxy…

  1. 1
    Weavable234

    Give every AI agent persistent work context

    May 2026

  2. 2

    Persistent memory for AI coding agents

    Apr 2026

  3. 3
    N71141

    Give all your AI agents one shared context

    Jul 2026 · n71.ai

  4. 4

    Block prompt inject & cut token costs for AI browser agents

    Jun 2026

  5. 5

    Turn your work activity into structured AI context.

    Feb 2026

  6. 6

    The context hub for your agents

    Feb 2026

  7. 7
    tablo124

    A tiny cat that watches your AI coding agents for you

    Jul 2026 · tablo-cat.netlify.app

  8. 8
    SeaTicket146

    Al agent that resolves issues across all your channels

    Jun 2026 · seaticket.ai

  9. 9

    Turn AI-app feedback into agent-ready patch context.

    Jun 2026 · patchrooms.com

  10. 10

    Automate any repetitive task with A.I. agents

    2024

  11. 11

    Models matter. Context matters more. Give your agent a plan.

    Jun 2026 · deepworkplan.com

  12. 12

    Knowledge Sharing for AI Agents

    Mar 2026

  13. 13
    Relay120

    Stop repeating yourself to every AI

    May 2026

  14. 14CC

    agents. Not a custom truncation strategy, not a sliding window, not dropping old messages and hoping for the best. The failure mode is well-understood: your context window fills up, you truncate from the top, and the agent loses the thread. It forgets the task it was working on, the file path it just wrote to, the UUID it needs to reference. The conversation breaks. The problem is everyone keeps solving it by throwing away information instead. Truncation is fast to implement and quietly wrong. The agent appears to work until it doesn't, and debugging context loss in a long-running session is…

    Mar 2026 · github.com

  15. 15

    Your AI agent for automating browsers

    2025

  16. 16

    Cut your AI token costs by 40-60% with one API call

    Feb 2026

  17. 17
    BU138

    Openclaw in the cloud

    Mar 2026

  18. 18

    Run agent workflows the community already built

    Apr 2026

  19. 19

    Your AI agents team, terminals, notes: one infinite canvas

    Jul 2026 · agentgrid.sh

  20. 20

    Connect AI agents to governed metadata via MCP

    Jan 2026

  21. 21

    Another month, another agent-shell update. If you missed the last one, have a look at the 0.63 update. While this post showcases the latest highlights...

    22d ago · xenodium.com

  22. 22

    A directory of Context Plugins, one per API. Each one grounds your coding agent in the API’s real specification, so what it writes is ready for production.

    3d ago · context.apimatic.io

  23. 23OS

    Hello HN, I’ve been building AI agents lately and ran into a common "Context Bloat" problem. When an agent has 20+ skills, stuffing every system prompt, reference doc, and tool definition into a single request quickly hits token limits and degrades model performance (the "lost in the middle" problem). To solve this, I built OpenSkills, an open-source SDK that implements a Progressive Disclosure Architecture for agent skills. The Core Concept: Instead of loading everything upfront, OpenSkills splits a skill into three layers: Layer 1 (Metadata): Light-weight tags and triggers (always loaded…

    Jan 2026

  24. 24AB

    Hi HN, Zidan here. I’ve been experimenting with AI-assisted debugging and noticed a recurring gap: most tools optimize for agent-led exploration (ex: giving claude code a browser to click around and try to reproduce an issue). But in many cases, I've already found the bug myself. What I actually want is a way to hand the agent the exact context I just saw - without retyping steps, copying logs, or hoping it can reproduce the behavior. So we built FlowLens, an open-source MCP server + Chrome extension that captures browser context and lets coding agents inspect it as structured, queryable…

    Nov 2025 · github.com

Ranked by how close each launch is in meaning, then by votes. Refine with a description →