<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tool-Use on CS2680 Student Blog</title><link>https://blog.cs2680.com/tags/tool-use/</link><description>Recent content in Tool-Use on CS2680 Student Blog</description><generator>Hugo</generator><language>en</language><copyright>&amp;copy; 2026 The President and Fellows of Harvard College</copyright><lastBuildDate>Tue, 06 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.cs2680.com/tags/tool-use/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Claude Code Kept Reaching for Bash</title><link>https://blog.cs2680.com/2026/assignment1/why-bash/</link><pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.cs2680.com/2026/assignment1/why-bash/</guid><description>&lt;p&gt;If you built a trajectory viewer for Assignment 1, you probably watched a lot of Bash go by.
Many students built careful renderers for Read, Edit and Write, expecting those tools to fill their
interfaces. Most of the file work arrived as &lt;code&gt;cat&lt;/code&gt;, &lt;code&gt;sed -n&lt;/code&gt;, heredocs and small Python patch
scripts, all wrapped in Bash cards. In one case described in our &lt;a href="https://blog.cs2680.com/2026/assignment1/agentic-coding-lessons/"&gt;lessons from the
assignment&lt;/a&gt;, an agent completed an entire bug fix through
the shell without ever lighting up the student&amp;rsquo;s edit view.&lt;/p&gt;
&lt;p&gt;We initially suspected the model or the way students prompted it. The submitted session logs
pointed mostly to Claude Code itself: it told the agent to use the shell and removed the Bash
tool&amp;rsquo;s usual warning against file operations. Most installations also lacked dedicated search
tools.&lt;/p&gt;</description></item></channel></rss>