<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Explyt on Medium]]></title>
        <description><![CDATA[Stories by Explyt on Medium]]></description>
        <link>https://medium.com/@explyt.ai?source=rss-47f532e94dc8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fqo4L8unHKjQRXk7K9MEAA.png</url>
            <title>Stories by Explyt on Medium</title>
            <link>https://medium.com/@explyt.ai?source=rss-47f532e94dc8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 06:37:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@explyt.ai/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Tests Are Green. The Agent Solved the Wrong Task.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@explyt.ai/the-tests-are-green-the-agent-solved-the-wrong-task-db749618c34e?source=rss-47f532e94dc8------2"><img src="https://cdn-images-1.medium.com/max/1225/1*dhPvaebENqM6PXBkyB0Nxg.jpeg" width="1225"></a></p><p class="medium-feed-snippet">Three anti-patterns that burn hours of agent work, and a free one-task methodology that closes them, from the Explyt webinar on working&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@explyt.ai/the-tests-are-green-the-agent-solved-the-wrong-task-db749618c34e?source=rss-47f532e94dc8------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@explyt.ai/the-tests-are-green-the-agent-solved-the-wrong-task-db749618c34e?source=rss-47f532e94dc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/db749618c34e</guid>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[python-programming]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Explyt]]></dc:creator>
            <pubDate>Wed, 30 Sep 2026 07:12:32 GMT</pubDate>
            <atom:updated>2026-09-30T07:12:32.251Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The CTO caps releases at the team’s speed of understanding, not the agents’ speed of generation.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@explyt.ai/the-cto-caps-releases-at-the-teams-speed-of-understanding-not-the-agents-speed-of-generation-61309259ee52?source=rss-47f532e94dc8------2"><img src="https://cdn-images-1.medium.com/max/1203/1*EQHj1e6sv4mWttrR000z6Q.jpeg" width="1203"></a></p><p class="medium-feed-snippet">The author wants to ship at generation speed. The CTO ships at comprehension speed. The CTO is right, and the gap only grows.</p><p class="medium-feed-link"><a href="https://medium.com/@explyt.ai/the-cto-caps-releases-at-the-teams-speed-of-understanding-not-the-agents-speed-of-generation-61309259ee52?source=rss-47f532e94dc8------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@explyt.ai/the-cto-caps-releases-at-the-teams-speed-of-understanding-not-the-agents-speed-of-generation-61309259ee52?source=rss-47f532e94dc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/61309259ee52</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Explyt]]></dc:creator>
            <pubDate>Fri, 25 Sep 2026 10:59:52 GMT</pubDate>
            <atom:updated>2026-09-25T10:59:52.313Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Explyt 5.20: stop waiting in the chat — a background task panel and notifications outside the IDE]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@explyt.ai/explyt-5-20-stop-waiting-in-the-chat-a-background-task-panel-and-notifications-outside-the-ide-b1768608a3c8?source=rss-47f532e94dc8------2"><img src="https://cdn-images-1.medium.com/max/968/1*d0MKzrB_C5WYg7Wjfb21gw.png" width="968"></a></p><p class="medium-feed-snippet">Past releases</p><p class="medium-feed-link"><a href="https://medium.com/@explyt.ai/explyt-5-20-stop-waiting-in-the-chat-a-background-task-panel-and-notifications-outside-the-ide-b1768608a3c8?source=rss-47f532e94dc8------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@explyt.ai/explyt-5-20-stop-waiting-in-the-chat-a-background-task-panel-and-notifications-outside-the-ide-b1768608a3c8?source=rss-47f532e94dc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1768608a3c8</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[java]]></category>
            <dc:creator><![CDATA[Explyt]]></dc:creator>
            <pubDate>Thu, 24 Sep 2026 15:38:50 GMT</pubDate>
            <atom:updated>2026-09-24T15:38:50.439Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why the agent needs access to the environment, not a human’s retelling of it]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@explyt.ai/why-the-agent-needs-access-to-the-environment-not-a-humans-retelling-of-it-b7aece933c61?source=rss-47f532e94dc8------2"><img src="https://cdn-images-1.medium.com/max/1920/1*Ct-eFa4xTQa0klNCXZPXdw.jpeg" width="1920"></a></p><p class="medium-feed-snippet">A retold log is a filtered log. The agent should query the database, read the broker, hit the endpoint itself&#x2013;and record what it saw.</p><p class="medium-feed-link"><a href="https://medium.com/@explyt.ai/why-the-agent-needs-access-to-the-environment-not-a-humans-retelling-of-it-b7aece933c61?source=rss-47f532e94dc8------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@explyt.ai/why-the-agent-needs-access-to-the-environment-not-a-humans-retelling-of-it-b7aece933c61?source=rss-47f532e94dc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7aece933c61</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ideas]]></category>
            <dc:creator><![CDATA[Explyt]]></dc:creator>
            <pubDate>Tue, 15 Sep 2026 13:39:56 GMT</pubDate>
            <atom:updated>2026-09-15T13:39:56.331Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The agent wrote the code, and you lost the model]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@explyt.ai/the-agent-wrote-the-code-and-you-lost-the-model-48d8f8274204?source=rss-47f532e94dc8------2"><img src="https://cdn-images-1.medium.com/max/1920/1*sm4-IqgcGXnuPvd6_zTNog.jpeg" width="1920"></a></p><p class="medium-feed-snippet">Green tests and a clean linter don&#x2019;t prove you understand the code.</p><p class="medium-feed-link"><a href="https://medium.com/@explyt.ai/the-agent-wrote-the-code-and-you-lost-the-model-48d8f8274204?source=rss-47f532e94dc8------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@explyt.ai/the-agent-wrote-the-code-and-you-lost-the-model-48d8f8274204?source=rss-47f532e94dc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/48d8f8274204</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <dc:creator><![CDATA[Explyt]]></dc:creator>
            <pubDate>Tue, 15 Sep 2026 13:22:22 GMT</pubDate>
            <atom:updated>2026-09-15T13:22:22.577Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why the agent needs access to the environment, not a human’s retelling of it]]></title>
            <link>https://medium.com/@explyt.ai/why-the-agent-needs-access-to-the-environment-not-a-humans-retelling-of-it-09a3a2100bcd?source=rss-47f532e94dc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/09a3a2100bcd</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[kotlin]]></category>
            <dc:creator><![CDATA[Explyt]]></dc:creator>
            <pubDate>Thu, 10 Sep 2026 18:43:28 GMT</pubDate>
            <atom:updated>2026-09-10T18:43:28.070Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A retold log is a filtered log. The agent should query the database, read the broker, hit the endpoint itself — and record what it saw.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3S9uIGxcbOnGEYzLdgXqNA.png" /></figure><p>There is a moment in almost every debugging session with an AI agent where the developer stops being a developer and becomes a clipboard. The agent asks for the error. The developer runs the command, scrolls, selects the part that looks relevant, pastes it. The agent asks for the row in the database. The developer opens a SQL client, runs a query, pastes the result. The agent asks what the endpoint returned. Another terminal, another paste.</p><p>Each paste is a decision about what matters, made by the person who does not yet know what matters.</p><p>I am the product manager at Explyt, where we build an AI agent for JetBrains IDEs. I have written before about a session in our own agent where the developer pasted SQL results, Kafka and Spring logs, HTTP responses and Kubernetes messages by hand while the agent’s terminal use was limited to git (<a href="https://explyt.ai/en/blog/one-symptom-ten-problems-kafka-invariant">One symptom, ten problems</a>). That session sent me looking for how common the pattern is outside our own logs. The issue trackers are full of it, and Anthropic’s engineering posts describe the fix while the same company’s prompt examples still say “[paste error]”.</p><h3>TL;DR</h3><ul><li>Public issues on Claude Code and Copilot, plus Reddit threads about Cursor and Claude Code, document the same loop: the agent cannot see the terminal, the database or the CI logs, so the human copies output into the chat, and the agent reasons about the copy.</li><li>The copy passes through several filters: what the human chose to run, what they chose to select, what the tooling truncated without saying so, and what the agent’s own compaction later summarized away. Each filter removes the kind of detail that debugging turns on.</li><li>When the agent does have access, it often leaves it unused. Issues show agents guessing column names with SSH access available, confirming a production config without checking, and asking the human to run a query the agent’s own MCP server could run.</li><li>Anthropic’s engineering guidance says agents need “ground truth” from the environment at each step. The instruments to get it exist as MCP servers for databases, Kafka and Kubernetes, most with read-only modes.</li><li>Direct access is half of the fix. The other half is a record of what the agent queried, what came back, and which conclusion rests on which observation.</li></ul><h3>The relay loop, in the words of the people stuck in it</h3><p><a href="https://github.com/anthropics/claude-code/issues/69360">anthropics/claude-code #69360</a> (June 2026): “Claude Code (VS Code extension) cannot read the existing terminal output. When a user runs a command that produces errors, they must manually copy-paste the output into the chat. This adds friction to the debugging workflow and breaks the natural “run → see error → ask Claude” loop.”</p><p><a href="https://github.com/anthropics/claude-code/issues/13865">anthropics/claude-code #13865</a> (December 2025) spells out the steps and names the consequence: “Currently, if I want to debug a runtime issue, I have to: 1. Manually ask Claude to add print/log statements. 2. Manually run the app/script. 3. Copy/paste the terminal output back into Claude Code. 4. Ask Claude to analyze it. 5. Ask Claude to remove the logs afterwards. This manual “human-in-the-loop” data transfer is slow and error-prone, often leading to “shotgun debugging” where the model guesses the solution without concrete runtime evidence.”</p><p>The Copilot side has the same report from the other direction. In <a href="https://github.com/microsoft/vscode-copilot-release/issues/10778">microsoft/vscode-copilot-release #10778</a> (May 2025): “The agent fails to see the output from the terminal so it starts to run another command in a different way repeatedly failing to see the output. If I select the terminal output and select add to chat, it can see the output.” An agent that cannot see the result of its own command reruns it and still sees nothing; in that thread the paste was the only channel that worked.</p><p>Reddit adds the texture. A Cursor user in <a href="https://www.reddit.com/r/ClaudeAI/comments/1psuh3t/can_claude_code_create_automation_loops_better/">r/ClaudeAI</a> (December 2025): “Cursor also can’t directly read and make use of the error logs in the PowerShell console. It feels broken for me to manually copy paste the logs to the Cursor agent.” Another in <a href="https://www.reddit.com/r/cursor/comments/1u3kvp6/open_in_terminal_pane_removal_is_breaking_the/">r/cursor</a> (June 2026), after a tooling change: “Only option is copy the command and re-run it yourself, which kind of defeats the whole point of having an agent run things!”</p><p>These are personal accounts with low vote counts, and I cite them as such. What they share with the GitHub issues is the shape: for everything outside the repository, the human carries the data.</p><h3>Four filters between the environment and the agent</h3><p>A retold log is filtered whether or not anyone intends it.</p><h3>1. What to run</h3><p>The first filter is the choice of what to run. The developer decides which command, which query, which endpoint. If the hypothesis in their head is wrong, the evidence they collect is evidence for or against the wrong hypothesis, and the query that would have tested the right one never runs.</p><h3>2. What to select</h3><p>The second is the choice of what to select. Nobody pastes a 4,000-line log. They scroll to the stack trace or the last twenty lines and paste that. The warning three seconds earlier and the second exception in a different thread stay in the terminal.</p><h3>3. Truncation by tooling</h3><p>The third is the one nobody chooses: truncation by tooling. A <a href="https://www.reddit.com/r/ClaudeCode/comments/1spiy8t/token_optimizers_for_ai_coding_agents_are/">r/ClaudeCode thread</a> (April 2026) tested a popular token-saving wrapper. On a package listing: “The remaining 314 packages are invisible. There is no truncation indicator. The output looks complete.” In a separate example on log levels, the same author describes the downstream effect: “An AI agent doing incident triage reads the logs, sees one error (a transient retry), and concludes it’s a minor blip. It applies a small fix and closes the investigation.” Truncation is also the default in the agent itself: “For Claude Code, we restrict tool responses to 25,000 tokens by default”, from Anthropic’s <a href="https://www.anthropic.com/engineering/writing-tools-for-agents">Writing effective tools for AI agents</a>.</p><h3>4. Compaction</h3><p>The fourth looks like memory. Anthropic’s <a href="https://www.anthropic.com/engineering/effective-context-engineering-for-ai-agents">context engineering post</a> describes compaction as “summarizing its contents, and reinitiating a new context window with the summary”, where “the model preserves architectural decisions, unresolved bugs, and implementation details while discarding redundant tool outputs or messages.” The word “redundant” is doing a lot of work there. In a debugging session, the tool output that looked redundant at the time of compaction is often the one you need two hours later.</p><p>Stack the four and the agent is reasoning about a document written by a human with a hypothesis, cut to fit a chat box, truncated by a wrapper, and then summarized. It is a wonder it gets anything right.</p><h3>When the agent has access and still asks you</h3><p>Direct access turns out to be necessary and, on its own, insufficient, because agents with access often leave it unused.</p><p><a href="https://github.com/anthropics/claude-code/issues/43387">anthropics/claude-code #43387</a> (April 2026) is the sharpest example I found. The agent “Wrote 1,700 lines of PHP with 28 database actions using completely guessed column names — never ran SHOW COLUMNS or any test query against the real database.” The reporter adds: “Claude has SSH access to the server and could run SHOW COLUMNS, curl endpoints, or test queries — but never does before saying “done”.” Thirty of forty-six queries referenced columns that did not exist while the SSH session sat unused.</p><p><a href="https://github.com/anthropics/claude-code/issues/60107">anthropics/claude-code #60107</a> (May 2026, a report the user had the agent itself write up) moves the same failure to production: “Claude Code confirmed a Postgres dialect option (statement_timeout) as valid for a Heroku-hosted production app when I explicitly asked &quot;are you sure this is a valid option?&quot;. The agent answered &quot;yes&quot; without verifying against the actual prod environment. The change passed all local tests (local Postgres in Docker has no pgbouncer), shipped to production, and crashed every dyno at boot.&quot; Local and production gave different answers to the same question, and the agent queried neither.</p><p><a href="https://github.com/anthropics/claude-code/issues/86718">anthropics/claude-code #86718</a> (August 2026) is the near-miss: the agent “without verifying, concluded that a database record … had been overwritten/corrupted … and stated this as fact”, and “had already suggested deleting the affected database record before I stopped it.” The agent guessed that data was damaged and proposed deleting it before anyone had checked.</p><p>And from the MCP side, a <a href="https://www.reddit.com/r/cursor/comments/1loojez/serverpostgres_mcp_still_working_for_anyone/">r/cursor user</a> (July 2025) with a Postgres MCP server connected: “Tried 4 different models to try to get it to query my dev database, all attempts fail with the model just asking me to run the query myself.” A <a href="https://www.reddit.com/r/ClaudeCode/comments/1ux854f/significant_drop_in_intelligence_today_on_opus_48/">r/ClaudeCode user</a> (July 2026) on CI: “it tried a bunch of local builds before then asking me to paste in the logs from the failed CI deployment. It has access to the CI logs, and has used them in the past.”</p><p>So the instruments have to be there, and the agent has to be held to using them. The second part is a harness and prompting problem, and I come back to it below.</p><h3>What Anthropic says the agent should do</h3><p>Anthropic, <a href="https://www.anthropic.com/engineering/building-effective-agents">Building effective agents</a>: “During execution, it’s crucial for the agents to gain “ground truth” from the environment at each step (such as tool call results or code execution) to assess its progress.”</p><p>Anthropic, <a href="https://code.claude.com/docs/en/best-practices">Claude Code best practices</a>: “Claude stops when the work looks done. Without a check it can run, “looks done” is the only signal available, and you become the verification loop: every mistake waits for you to notice it.” The same page defines the check as “anything that returns a signal Claude can read in the conversation: a test suite, a build exit code, a linter, a script that diffs output against a fixture, or a browser screenshot compared against a design”.</p><p>The same page also, in its prompt-example table, recommends writing “[paste error]” to the agent. I mention it because it shows how deep the relay habit runs: even the document that tells you to make the agent its own verification loop assumes the human will hand it the error.</p><p>The context engineering post gives the alternative, and the alternative is many small retrievals made by the agent itself: “Letting agents navigate and retrieve data autonomously also enables progressive disclosure”, and “The model can write targeted queries, store results, and leverage Bash commands like head and tail to analyze large volumes of data without ever loading the full data objects into context.”</p><p>The research on long contexts points the same way. <a href="https://arxiv.org/abs/2307.03172">Lost in the Middle</a> (Liu et al., 2023) found that “performance can degrade significantly when changing the position of relevant information”, and Chroma’s <a href="https://research.trychroma.com/context-rot">Context Rot</a> report (2025), across 18 models, concludes that “models do not use their context uniformly; instead, their performance grows increasingly unreliable as input length grows.” A bigger paste makes the second problem worse while leaving the first four filters in place.</p><h3>The instruments exist</h3><p>“Query the database, read the broker, hit the endpoint” sounds like a wish list. As of September 2026 it is a list of MCP servers, most with a read-only switch. Star counts and dates are from the GitHub API on 2026–09–08.</p><h3>Databases</h3><p>For databases: <a href="https://github.com/crystaldba/postgres-mcp">crystaldba/postgres-mcp</a> (3.3k stars) has a “Restricted Mode” that “Limits operations to read-only transactions and imposes constraints on resource utilization” and is described as “suitable for production environments”. <a href="https://github.com/bytebase/dbhub">bytebase/dbhub</a> (3.5k stars, release 2026–09–02) covers Postgres, MySQL, SQL Server, MariaDB and SQLite with “Read-only mode, row limiting, and query timeout to prevent runaway operations”. Google’s <a href="https://github.com/googleapis/mcp-toolbox">MCP Toolbox for Databases</a> (16k stars) ships “Prebuilt generic tools for instant data exploration (e.g., list_tables, execute_sql)”. The original reference Postgres server from the Model Context Protocol project is archived; the current reference set is filesystem, git, fetch, memory and a few others.</p><h3>Kafka</h3><p>For Kafka: <a href="https://github.com/confluentinc/mcp-confluent">confluentinc/mcp-confluent</a> (v1.5.0, July 2026) exposes list-topics, consume-messages and list-consumer-groups, and also produce-message, create-topics and delete-topics. It has no read-only flag, but its --allow-tools and --block-tools options let you start it with the write tools removed, which is how I would run it for debugging.</p><h3>Kubernetes</h3><p>For Kubernetes: <a href="https://github.com/containers/kubernetes-mcp-server">containers/kubernetes-mcp-server</a> (2.1k stars, actively maintained) has --read-only, which &quot;will not allow any write operations (create, update, delete)&quot;, plus --disable-destructive, and a pods_log tool that does the obvious thing.</p><h3>HTTP</h3><p>For HTTP: the reference <a href="https://github.com/modelcontextprotocol/servers/tree/main/src/fetch">fetch server</a> converts pages to markdown, so it fetches web pages and does no API work. For “hit the endpoint itself” you want the agent’s terminal with curl, or a purpose-built server.</p><p>Each of these servers exposes access the developer already has, behind a permission model.</p><h3>The other half: record what it saw</h3><p>I disagree with the simplest version of my own thesis. Give the agent a terminal, a database and a broker, and you have replaced a filtered log with an unfiltered stream that nobody reads. The developer stops being the clipboard and becomes the person who has to trust a conclusion with no visible chain of evidence.</p><p>The fix is the one that works for human engineers: a record. Which query ran, against which environment, what came back, and which conclusion rests on which result. Anthropic’s tooling post recommends the reviewer’s version of this: “Review the raw transcripts (including tool calls and tool responses) to catch any behavior not explicitly described in the agent’s CoT.” The agent’s version is to keep that record itself, in the open, as it works.</p><p>In practice I now hold any agent I use for debugging to a short set of rules.</p><ol><li>Every claim about the environment carries the observation it came from: the query, the environment and the timestamp next to the value, so “the row has status = PENDING&quot; arrives with &quot;query at 14:02 against staging&quot;.</li><li>The environment is named every time, because #60107 above is what happens when local and production are treated as one.</li><li>And the record survives compaction: if the agent summarizes its own context, the observations stay in a file that the summary links to.</li></ol><p>The problem sits in the harness as much as in the model. #43387 and the two MCP stories above show models with access declining to use it. A rule in the repository’s agent instructions that says “before stating anything about database, broker or runtime state, query it and quote the result” is blunt. In my own sessions it removed most of the guessed claims.</p><h3>Where Explyt stands</h3><p>Explyt is our agent for JetBrains IDEs, and I want to state what its documentation does and does not cover on this topic.</p><p>The <a href="https://explyt.ai/docs/explyt-test/tools">tools documentation</a> frames the goal in the same terms as this article: tools “give the agent facts about your project and let it perform actions without you manually copying long logs and search results into the chat.”</p><p>Two of those sources come from the IDE itself, not from anything a database or a broker exposes, and I start with them because they are the ones a paste cannot replace.</p><p><a href="https://explyt.ai/docs/explyt-test/tools/run-configurations">Run configurations</a>: the agent runs a configured test, build or application through the IDE and “returns the result to the agent: console output, test results, compilation errors.” That closes the “copy the terminal output back” loop from #13865 for anything the IDE knows how to run. The docs are explicit that in Rider the tool currently does not build the project and does not collect coverage.</p><p>[IMAGE 2: images/run-configurations.gif] <em>An Explyt session running a test through an IDE run configuration and reading the result back, from an earlier article on this blog. A different project from anything quoted above.</em></p><p>The <a href="https://explyt.ai/docs/explyt-test/tools/debugger">Debug mode documentation</a> states the principle for the runtime case in one line: “The cause is confirmed by breakpoints, variable values, and the call stack, not just by a guess based on the code or the log.” Replace “the log” with “the pasted log” and you have this article. A variable read at a breakpoint is an observation no log contains, pasted or not; an agent without a debugger is back in the relay loop for that class of bug, whatever else it can query.</p><p>[IMAGE 3: images/debug-workflow.gif] <em>Explyt Debug mode on a Spring integration test, from an earlier case on this blog: breakpoint, variable values, then the fix. A different case from the issues quoted in this article.</em></p><p>The rest of the environment comes through the two channels any agent has. The terminal tools, per the <a href="https://explyt.ai/docs/explyt-test/configuration/reference/tools-reference">tools reference</a>: “The terminal tools run commands and manage processes. You need them when there is no suitable IDE configuration or when the task involves an external utility.” The same page lists what to check before a command runs, because “A command can change files, a database, the environment or a remote system.” This is the tool that runs psql or kubectl when you allow it.</p><p>MCP: “Once an MCP server is connected, its tools appear in the Tools menu as a separate group. The names, parameters and consequences of a call are defined by the server itself.” The <a href="https://explyt.ai/docs/explyt-test/tools/mcp">MCP page</a>, in its GitHub example, suggests to “Test the connection with a safe read operation first”, and notes that each MCP result block “contains the outcome and diagnostic details of the call, which are useful when verifying a result or investigating an error.”</p><p>What the documentation does not describe is any built-in Kafka, SQL or Kubernetes access. Those come through the terminal or through an MCP server you connect and scope, and they land in the same session as the run configurations and the debugger, so one transcript holds the test result, the variable value and the query result side by side. And pasting remains supported: the <a href="https://explyt.ai/docs/explyt-test/agent/chat">chat documentation</a> says large pastes become attachments and “The agent receives the complete text.” Pasting should stay available as the fallback; the agent’s own query should be the default.</p><h3>Limits</h3><p>The GitHub issues above are individual reports; I have not measured how often the relay loop occurs or how often agents with access decline to use it. Reddit threads are personal accounts with low scores. MCP server statistics are a snapshot from one day and the read-only behavior comes from the READMEs; I have not audited the servers myself. The Explyt claims are limited to what the documentation says; the session I referenced is described in the linked article and its details are not published.</p><h3>One thing to try this week</h3><p>Pick the next runtime bug where you would normally paste a log. Connect one read-only source the agent can query itself, a database MCP in restricted mode or the terminal with kubectl logs, and add one line to your agent instructions: state nothing about the environment without quoting the query and the result. Then read the transcript and count how many of the agent&#39;s claims come with an observation attached. I expected the count to be low the first time I did this, and it was.</p><p>If you work in a JetBrains IDE, <a href="https://plugins.jetbrains.com/plugin/27979-explyt-ai-agent">Explyt on the Marketplace</a> gives the agent the two sources a paste cannot replace, the IDE run and the debugger, and takes MCP servers for the rest.</p><p>What did your agent last ask you to paste that it could have fetched itself, and what happened when you gave it the access? Drop a comment; I am collecting the cases where the query the human never ran turned out to be the one that mattered.</p><h3>Related reading</h3><ul><li><a href="https://explyt.ai/en/blog/one-symptom-ten-problems-kafka-invariant">One symptom, ten problems: a Kotlin + Spring Boot + Kafka debugging case</a>, the session where the developer was the agent’s only sensor.</li><li><a href="https://explyt.ai/en/blog/agent-commit-created-but-it-isnt">“Commit created” — but it isn’t</a>, on checking an agent’s side-effect claims outside the chat.</li></ul><p>Follow for more on how agents debug in JetBrains IDEs, with the transcripts and issue reports behind each claim.</p><h3>Sources</h3><p><strong>Issue reports and threads</strong></p><ul><li><a href="https://github.com/anthropics/claude-code/issues/69360">anthropics/claude-code #69360, terminal output not readable</a></li><li><a href="https://github.com/anthropics/claude-code/issues/13865">anthropics/claude-code #13865, Debug Mode feature request</a></li><li><a href="https://github.com/anthropics/claude-code/issues/43387">anthropics/claude-code #43387, guessed column names with SSH access available</a></li><li><a href="https://github.com/anthropics/claude-code/issues/60107">anthropics/claude-code #60107, production config confirmed without checking</a></li><li><a href="https://github.com/anthropics/claude-code/issues/86718">anthropics/claude-code #86718, guessed data corruption</a></li><li><a href="https://github.com/microsoft/vscode-copilot-release/issues/10778">microsoft/vscode-copilot-release #10778, agent cannot see terminal output</a></li><li><a href="https://www.reddit.com/r/ClaudeCode/comments/1spiy8t/token_optimizers_for_ai_coding_agents_are/">r/ClaudeCode, token optimizers drop lines silently</a></li><li><a href="https://www.reddit.com/r/ClaudeCode/comments/1ux854f/significant_drop_in_intelligence_today_on_opus_48/">r/ClaudeCode, agent asks for CI logs it can access</a></li><li><a href="https://www.reddit.com/r/cursor/comments/1loojez/serverpostgres_mcp_still_working_for_anyone/">r/cursor, Postgres MCP connected, agent asks human to run the query</a></li><li><a href="https://www.reddit.com/r/cursor/comments/1u3kvp6/open_in_terminal_pane_removal_is_breaking_the/">r/cursor, terminal pane removal</a></li><li><a href="https://www.reddit.com/r/ClaudeAI/comments/1psuh3t/can_claude_code_create_automation_loops_better/">r/ClaudeAI, copy-pasting PowerShell logs to Cursor</a></li></ul><p><strong>Vendor and research</strong></p><ul><li><a href="https://www.anthropic.com/engineering/building-effective-agents">Anthropic, Building effective agents</a></li><li><a href="https://code.claude.com/docs/en/best-practices">Anthropic, Claude Code best practices</a></li><li><a href="https://www.anthropic.com/engineering/effective-context-engineering-for-ai-agents">Anthropic, Effective context engineering for AI agents</a></li><li><a href="https://www.anthropic.com/engineering/writing-tools-for-agents">Anthropic, Writing effective tools for AI agents</a></li><li><a href="https://arxiv.org/abs/2307.03172">Liu et al., Lost in the Middle (2023)</a></li><li><a href="https://research.trychroma.com/context-rot">Chroma Research, Context Rot (2025)</a></li></ul><p><strong>MCP servers</strong></p><ul><li><a href="https://github.com/crystaldba/postgres-mcp">crystaldba/postgres-mcp</a></li><li><a href="https://github.com/bytebase/dbhub">bytebase/dbhub</a></li><li><a href="https://github.com/googleapis/mcp-toolbox">googleapis/mcp-toolbox</a></li><li><a href="https://github.com/confluentinc/mcp-confluent">confluentinc/mcp-confluent</a></li><li><a href="https://github.com/containers/kubernetes-mcp-server">containers/kubernetes-mcp-server</a></li><li><a href="https://github.com/modelcontextprotocol/servers/tree/main/src/fetch">modelcontextprotocol/servers, fetch</a></li></ul><p><strong>Explyt documentation</strong></p><ul><li><a href="https://explyt.ai/docs/explyt-test/tools">Tools and integrations</a></li><li><a href="https://explyt.ai/docs/explyt-test/tools/run-configurations">Run configurations</a></li><li><a href="https://explyt.ai/docs/explyt-test/configuration/reference/tools-reference">Tools reference (terminal, MCP)</a></li><li><a href="https://explyt.ai/docs/explyt-test/tools/mcp">MCP</a></li><li><a href="https://explyt.ai/docs/explyt-test/agent/chat">Chat (paste handling)</a></li><li><a href="https://explyt.ai/docs/explyt-test/tools/debugger">Debugging with Debug mode</a></li><li><a href="https://explyt.ai/en/blog/one-symptom-ten-problems-kafka-invariant">Explyt blog, One symptom, ten problems</a></li><li><a href="https://plugins.jetbrains.com/plugin/27979-explyt-ai-agent">Explyt on JetBrains Marketplace</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=09a3a2100bcd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Three coding agents, one subscription key: what Explyt 5.19 changes]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@explyt.ai/three-coding-agents-one-subscription-key-what-explyt-5-19-changes-740fa4ab47bc?source=rss-47f532e94dc8------2"><img src="https://cdn-images-1.medium.com/max/1693/1*QHh5e-1rLX8W1bNIw0mKeA.png" width="1693"></a></p><p class="medium-feed-snippet">Claude Code, Cursor, Codex, Cline, OpenCode and Kilo Code can now run on Explyt minutes through an OpenAI-compatible gateway. The&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@explyt.ai/three-coding-agents-one-subscription-key-what-explyt-5-19-changes-740fa4ab47bc?source=rss-47f532e94dc8------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@explyt.ai/three-coding-agents-one-subscription-key-what-explyt-5-19-changes-740fa4ab47bc?source=rss-47f532e94dc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/740fa4ab47bc</guid>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ai-agent]]></category>
            <dc:creator><![CDATA[Explyt]]></dc:creator>
            <pubDate>Wed, 09 Sep 2026 15:49:37 GMT</pubDate>
            <atom:updated>2026-09-09T15:49:37.806Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[One symptom, ten problems: a Kotlin + Spring Boot + Kafka debugging case]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@explyt.ai/one-symptom-ten-problems-a-kotlin-spring-boot-kafka-debugging-case-29c47451f617?source=rss-47f532e94dc8------2"><img src="https://cdn-images-1.medium.com/max/1672/1*SIe5CtIYNNkBeMQWtLokAQ.png" width="1672"></a></p><p class="medium-feed-snippet">A single visible symptom led to many defects, half unrelated to it but all tied to one invariant about async TID processing. Debugging is&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@explyt.ai/one-symptom-ten-problems-a-kotlin-spring-boot-kafka-debugging-case-29c47451f617?source=rss-47f532e94dc8------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@explyt.ai/one-symptom-ten-problems-a-kotlin-spring-boot-kafka-debugging-case-29c47451f617?source=rss-47f532e94dc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/29c47451f617</guid>
            <category><![CDATA[ai-product-management]]></category>
            <category><![CDATA[ideas]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Explyt]]></dc:creator>
            <pubDate>Tue, 08 Sep 2026 13:14:38 GMT</pubDate>
            <atom:updated>2026-09-08T13:14:38.740Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[“Commit created” — but it isn’t: why the agent’s word needs external verification, and what the…]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@explyt.ai/commit-created-but-it-isnt-why-the-agent-s-word-needs-external-verification-and-what-the-0379bc4adfcd?source=rss-47f532e94dc8------2"><img src="https://cdn-images-1.medium.com/max/1203/1*3HaFvK7lH8oeMKLc1oKu_Q.jpeg" width="1203"></a></p><p class="medium-feed-snippet">Agents report actions they never completed. Any claim about a side effect &#x2014; commit, file, build &#x2014; must be confirmed by an independent&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@explyt.ai/commit-created-but-it-isnt-why-the-agent-s-word-needs-external-verification-and-what-the-0379bc4adfcd?source=rss-47f532e94dc8------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@explyt.ai/commit-created-but-it-isnt-why-the-agent-s-word-needs-external-verification-and-what-the-0379bc4adfcd?source=rss-47f532e94dc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/0379bc4adfcd</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ai-revolution]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Explyt]]></dc:creator>
            <pubDate>Mon, 07 Sep 2026 11:10:15 GMT</pubDate>
            <atom:updated>2026-09-07T11:10:15.966Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Superpowers vs Plain Old Debugger in Explyt]]></title>
            <link>https://pub.towardsai.net/superpowers-vs-plain-old-debugger-in-explyt-11544a921541?source=rss-47f532e94dc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/11544a921541</guid>
            <category><![CDATA[debugger]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ai-agent]]></category>
            <dc:creator><![CDATA[Explyt]]></dc:creator>
            <pubDate>Fri, 04 Sep 2026 19:01:01 GMT</pubDate>
            <atom:updated>2026-09-04T19:01:01.157Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Same bug, same model, same prompt. One debugging workflow burned 132k tokens and produced a patch I discarded; the other used 67k and shipped.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_eXQka7SrEqTvC9mlwfUpA.png" /></figure><p>An AI agent can follow a debugging checklist and still miss the bug.</p><p>The question I kept coming back to was simple: who ran the experiment?</p><p>I interviewed our users, mostly senior developers. In those interviews, debugging a hard problem came up most often. In practice, the investigation is still manual: a developer supplies logs, sets breakpoints, tests a theory, and pastes the result back into the chat.</p><p>A systematic debugging method gives the work a clear order: gather facts, form a hypothesis, run an experiment, then change the code. The order is right. What I wanted to see was whether an agent that follows it on paper also runs the experiment in practice.</p><h3>TL;DR</h3><ul><li>One real bug, one model (Opus 5), one prompt, two runs. The only variable was the debugging workflow: the <a href="https://github.com/obra/superpowers">Superpowers</a> systematic-debugging skill in one run, Explyt&#39;s built-in Debug skill in the other.</li><li>The Superpowers run found the right line in the stack trace, stated a plausible root cause, and then patched without ever observing the failing execution. The fix hid a distinction the product needed and left a test-only seam in the production constructor. I discarded it.</li><li>The Explyt run set a breakpoint on the same line, ran a reproducer under the JetBrains debugger, and read the runtime values before editing. The narrow fix passed review and is in production.</li><li>Token use: 67k for Explyt, 132k for Superpowers. The gap came from where the key fact arrived: early from the debugger, or late after speculative code, tests, and refactoring.</li><li>This is one controlled case, not a benchmark of either product. JetBrains’ own A/B tests on “token-saving” skills point to the same lesson: measure the whole agent run, not the skill’s self-reported counter.</li></ul><h3>Where Superpowers comes from</h3><p><a href="https://github.com/obra/superpowers">Superpowers</a> was created by <a href="https://blog.fsck.com/">Jesse Vincent</a> and the <a href="https://primeradiant.com/">Prime Radiant</a> team. Matt Pocock helped popularize it. The collection includes a <a href="https://www.skills.sh/obra/superpowers/systematic-debugging">systematic-debugging skill</a> that encodes the sequence above: gather facts, form a hypothesis, run an experiment, then change the code.</p><p>I ran Opus 5 on the same real bug and the same prompt twice. The only thing I changed was the debugging workflow: Superpowers in one run, Explyt’s built-in Debug skill in the other. It is one controlled case, not a benchmark of either product. The transcripts below show where the two runs parted ways.</p><h3>The bug: one protected Windows directory, one crashed coroutine</h3><p>The test case came from a Kotlin project on Windows. The IDE log contained:</p><pre>java.nio.file.AccessDeniedException: C:\Config.Msi<br>    at java.nio.file.Files.list(Files.java:3422)<br>    at FacadeMentionCandidates.listDir(FacadeMentionCandidates.kt:83)<br>    at FacadeMentionCandidates.listChildren(FacadeMentionCandidates.kt:69)<br>    at MentionSuggestionMapperKt$suggestionsFor$2.invokeSuspend(MentionSuggestionMapper.kt:36)</pre><p>The relevant code first checked whether a path was a directory and then enumerated it with Files.list. The exception came from a protected Windows Installer directory. FacadeMentionCandidates makes filesystem roots available to the @ mention flow, so a user navigating through a path such as @/C:/ can eventually reach a directory that the IDE process cannot enumerate.</p><p>The error was not handled at the flow boundary. It escaped the suggestion flow and was reported as an unhandled coroutine exception in WorkspaceBootstrap, with the IDE blaming the plugin. The same listing path is also used while searching around the focused file, so this was a small function with more than one way to fail.</p><h3>Run one: a plausible patch from Superpowers</h3><p>The Superpowers run started well. It searched the log instead of reading the whole file, followed the stack into FacadeMentionCandidates, found the unguarded Files.list, and stated a plausible root-cause hypothesis.</p><p>Then the investigation stopped before the experiment. The run never set a debugger breakpoint or inspected a value from the failing execution. The proposed fix was to wrap the directory listing in a try/catch, log the exception, and return emptyList().</p><p>That choice made the failure disappear from the call stack, but it changed the meaning of the result. An empty directory and a directory denied by ACL became the same value; other I/O failures still had no user-facing outcome. The mention UI could not tell the developer what happened, and the option to mention the directory remained indistinguishable from a normal empty-folder case.</p><p>The regression test followed the same assumption. It asserted that an unreadable directory produced no children. On Windows, the first version could not create the required POSIX permission state and was skipped. To force the exception, the agent then added a readDirectory function to the production constructor so the test could inject a throwing fake. That seam existed for the test, not for the product behavior.</p><p>The run finished with seven passing tests, but those tests established that the workaround returned an empty list. They did not establish that the user-facing behavior was correct, or that the error had been verified against a real paused execution. I discarded the patch: it hid the distinction we needed and left a test-only abstraction in the production API.</p><p>That is how a checklist turns into a ritual. Every step appears in the transcript; the experiment never does. A plausible local edit stands in for evidence.</p><h3>Run two: Explyt puts the hypothesis inside the IDE</h3><p>With Explyt’s built-in debugging skill, the model started from the same log and source files, but it could use the JetBrains debugger as part of the investigation.</p><p>It created a minimal reproducer, set a line breakpoint on the Files.list call, and ran the test under the debugger. When execution stopped, the value was concrete:</p><pre>dir                     = C:\Config.Msi<br>Files.isDirectory(dir)  = true<br>Files.isReadable(dir)   = false<br>Files.list(dir)         -&gt; throws java.nio.file.AccessDeniedException</pre><p>The call stack matched the production trace: listDir → listChildren → MentionSuggestionMapper.suggestionsFor, inside the coroutine that builds mention suggestions. The debugger turned &quot;a protected path probably causes this&quot; into a verified statement about the running program:</p><blockquote><em>The directory check passes, the process cannot read the directory, and the unguarded enumeration kills the suggestion flow.</em></blockquote><p>The evidence kept the fix at the filesystem boundary, with focused regression coverage and the normal listing path left intact. The mention protocol and runtime model stayed unchanged, and debug prints were unnecessary.</p><p>The narrow fix passed review and is now in production. A try/catch was enough here. What mattered was choosing it after observing the failing execution, instead of using it as the first explanation for the failure.</p><h3>The practical difference</h3><p>Both runs started from the same log and the same source. Everything after that diverged.</p><ul><li><strong>Investigation channel.</strong> Superpowers: text, stack trace, and tests. Explyt: the JetBrains debugger plus source and tests.</li><li><strong>Key fact.</strong> Superpowers: inferred from AccessDeniedException. Explyt: observed at a breakpoint, with the directory, its permissions, and the throw.</li><li><strong>Token use in this run.</strong> Superpowers: 132k. Explyt: 67k.</li><li><strong>First implementation.</strong> Superpowers: swallow the error as emptyList(). Explyt: keep the fix at the proven failing boundary.</li><li><strong>Test signal.</strong> Superpowers: passing tests for the fallback. Explyt: runtime evidence first, then a focused regression test.</li><li><strong>Result.</strong> Superpowers: patch discarded as technical debt. Explyt: reviewed minimal fix deployed to production.</li></ul><p>I could see the cleanup cost in the diff. The discarded patch carried a workaround-driven test seam. The shipped patch stayed at the failing boundary and left the normal listing path intact.</p><p>For a runtime bug, a coherent explanation from a log is still only a theory. I want one fact captured from the running program: a variable value, a call stack, an execution path, or the exact branch that contradicts the model’s theory.</p><h3>What Explyt did in this run, and where the claim stops</h3><p>Explyt is an AI agent for JetBrains IDEs. In this run, it used a supported JetBrains IDE and run configuration. Its Debug workflow started the code under the JetBrains debugger and inspected breakpoints, variable values, call stacks, and execution paths before editing. The IDE supplies the evidence; the developer still decides whether the hypothesis and the resulting diff are acceptable.</p><p>What I can say from these transcripts is limited. Superpowers can be combined with a debugger, and Explyt’s debugger depth depends on the IDE, language, and run configuration. Check the <a href="https://explyt.ai/docs/explyt-test/feature-matrix">feature matrix</a> for the supported combinations.</p><p>The token count points in the same direction. The debugger gave the model the fact it needed before more speculative turns accumulated, which is a different effect from adding one more tool to the menu.</p><h3>Measure the run, not the skill’s counter</h3><p>JetBrains has been running paired A/B tests on “token-saving” skills, with a useful warning against reading too much into their README claims.</p><ul><li>In the <a href="https://blog.jetbrains.com/ai/2026/07/speak-to-ai-agents-like-cavemen-tosave-tokens/">Caveman test</a>, the advertised 65% reduction became 8.5% fewer output tokens on real agentic tasks, with activation forced.</li><li>In the newer <a href="https://blog.jetbrains.com/ai/2026/07/rtk-claude-code-token-savings/">rtk test</a>, the with-rtk arm cost a median 7.6% more per task at low reasoning effort, and showed no saving at high effort.</li><li>The latest <a href="https://blog.jetbrains.com/ai/2026/07/ponytail-skill-claude-tested/">Ponytail test</a> found a 10.3% cost reduction on its own benchmark.</li></ul><p>The results are mixed; the consistent lesson is to measure the whole agent run, not a skill’s self-reported counter. My 67k-versus-132k figure is one such whole-run measurement, for one bug, with n = 1. Treat it as a reason to run your own comparison, not as a verdict.</p><h3>Try the first useful task</h3><p>If you already work in a JetBrains IDE, <a href="https://explyt.ai/t/l/edit">install Explyt from the Marketplace</a>, open a reproducible failing test, and let the agent inspect the first runtime value that contradicts its theory. Then review the diff before accepting the fix.</p><h3>Sources</h3><ul><li>Superpowers repository: <a href="https://github.com/obra/superpowers">https://github.com/obra/superpowers</a></li><li>Superpowers systematic-debugging skill: <a href="https://www.skills.sh/obra/superpowers/systematic-debugging">https://www.skills.sh/obra/superpowers/systematic-debugging</a></li><li>Jesse Vincent’s blog: <a href="https://blog.fsck.com/">https://blog.fsck.com</a></li><li>Prime Radiant: <a href="https://primeradiant.com/">https://primeradiant.com</a></li><li>Explyt feature matrix: <a href="https://explyt.ai/docs/explyt-test/feature-matrix">https://explyt.ai/docs/explyt-test/feature-matrix</a></li><li>Explyt on JetBrains Marketplace: <a href="https://plugins.jetbrains.com/plugin/27979-explyt-ai-agent">https://plugins.jetbrains.com/plugin/27979-explyt-ai-agent</a></li><li>JetBrains AI blog, Caveman test: <a href="https://blog.jetbrains.com/ai/2026/07/speak-to-ai-agents-like-cavemen-tosave-tokens/">https://blog.jetbrains.com/ai/2026/07/speak-to-ai-agents-like-cavemen-tosave-tokens/</a></li><li>JetBrains AI blog, rtk test: <a href="https://blog.jetbrains.com/ai/2026/07/rtk-claude-code-token-savings/">https://blog.jetbrains.com/ai/2026/07/rtk-claude-code-token-savings/</a></li><li>JetBrains AI blog, Ponytail test: <a href="https://blog.jetbrains.com/ai/2026/07/ponytail-skill-claude-tested/">https://blog.jetbrains.com/ai/2026/07/ponytail-skill-claude-tested/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11544a921541" width="1" height="1" alt=""><hr><p><a href="https://pub.towardsai.net/superpowers-vs-plain-old-debugger-in-explyt-11544a921541">Superpowers vs Plain Old Debugger in Explyt</a> was originally published in <a href="https://pub.towardsai.net/">Towards AI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>