Skip to content

Commit 689c00d

Browse files
yotsudaclaude
andcommitted
Replace AI agent examples with ProcessDrive-specific operations
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent b112053 commit 689c00d

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -172,10 +172,10 @@ dir Proc:\ -Recurse | Export-Csv processes.csv
172172

173173
ProcessDrive works with [PowerShell.MCP](https://www.powershellgallery.com/packages/PowerShell.MCP), enabling AI agents (Claude, GitHub Copilot, etc.) to explore processes through natural conversation:
174174

175-
- "What processes are using the most memory?" → `dir Proc:\ | Sort-Object MemMB -Descending | Select-Object -First 10`
175+
- "What child processes does chrome have?" → `dir Proc:\chrome_21236`
176176
- "Show me chrome's network connections" → `dir Proc:\chrome_21236\Network`
177-
- "What DLLs does devenv have loaded?" → `dir Proc:\devenv_24032\Modules`
178-
- "Kill all notepad processes" → `dir Proc:\ -Include notepad* -Recurse | Remove-Item`
177+
- "Which services are hosted by svchost PID 1804?" → `dir Proc:\svchost_1804\Services`
178+
- "Find all processes that loaded gdi32.dll" → `dir Proc:\ | % { dir "Proc:\$($_.PSChildName)\Modules" -EA Ignore } | ? Name -like '*gdi*'`
179179

180180
The typed DTO output (`ProcessInfo`, `ModuleInfo`, `ThreadInfo`, etc.) makes it easy for AI agents to parse and reason about process data.
181181

0 commit comments

Comments
 (0)