furst/coding-with-ai
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Align prose with STYLE.md across modules 01-07 and top-level README

Browse source 
Replace residual em-dashes, arrow-notation shorthand, and a handful of
filler intensifiers; fix two small typos. Add .gitignore to keep the
working CHANGES.md audit out of the repo.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
Eric Furst 2026-05-29 08:47:19 -04:00
commit 4194680475
9 changed files with 102 additions and 82 deletions
Download patch file Download diff file Expand all files Collapse all files

6
05-agentic-workflow/README.md
View file

@ -6,6 +6,8 @@ An agentic tool is an AI that takes actions on its own (reading files, running c
This section is about *using* agentic tools as an engineer or scientist (for modeling, data analysis, simulations, or coursework), not building production software for end users. For how tool use works under the hood, see the [llm-workshop](https://lem.che.udel.edu/git/furst/llm-workshop) section on tool use and agentic systems.
> **A note on overlap with [section 04](../04-conversations/):** the boundary between conversation and agentic work is fuzzy in practice. The same in-project chat panel becomes an agent the moment you give it a multi-step goal it executes on its own. This distinction is behavioral, not a separate tool to launch, and you will routinely cross between the two modes within a single session. This section focuses on what changes once the model is taking actions, but expect the framing to apply to many of your existing chat sessions too.
## Key goals
- Recognize when you have moved from in-project chat into agentic territory, and what changes when you do
@ -18,7 +20,7 @@ This section is about *using* agentic tools as an engineer or scientist (for mod
## What an agent actually does
An agentic tool wraps a chat model in a *loop* that lets it take actions in your environment. In practice, the same in-project chat panel you use for a one-shot question ([section 04](../04-conversations/)) becomes an agent the moment you give it a multi-step goal. There is no separate "agent app" to launch. One step in the loop:
An agentic tool wraps a chat model in a *loop* that lets it take actions in your environment. One step in the loop:
1. The model receives your goal and the current state (files, terminal output, etc.)
2. The model decides on the next action: read a file, run a command, write an edit
@ -87,7 +89,7 @@ Rule of thumb: **destructive or remote-affecting actions deserve confirmation.**
### Working directory and damage control
An agent pointed at a fresh sandbox can experiment freely. An agent pointed at your home directory can do real damage. Before starting:
An agent pointed at a fresh sandbox can experiment freely. An agent pointed at your home directory can do real damage! Before starting:
- Be sure you are in the right directory
- Have a clean git state (or know what's uncommitted) so you can see what the agent changed