Skip to content
agentusehub

Code in the terminal with an agent

The poster uses Grok as a terminal coding agent that reads, edits, runs tools and spawns sub-agents.

Time saved
Not reported
Setup time
Not reported
Running cost
Not reported
Cost range
Not reported

Use case overview

The poster uses Grok as a terminal coding agent that reads, edits, runs tools and spawns sub-agents.

Reported experience

  1. What they did

    The poster says they built agenc-core as a terminal agent harness where Grok drives the work directly in a CLI/TUI: it reads files, edits code, runs tools, and can spawn parallel sub-agents with separate context, tools, and token budgets. In the example they watched it split a divisible job into eight workers to build eight separate C terminal games at once, while the main orchestrator integrated and verified the results and a human handled approval prompts for tool calls.

  2. How it went

    The post presents it as working well enough to be the author’s showcase, including the eight-game parallel build and integrations like Ledger actions gated by on-device approval. It does not give benchmark numbers, failure rates, or a detailed comparison against other coding agents.

  3. Worth knowing

    The main catch is the permission model: tool calls can require human approval, and any Ledger action that moves value needs physical confirmation on the device.

Example prompts

Try with Grok Bot
In the project at [path to repo], I want you to [describe feature or bug fix]. Read the relevant code first, make the edits, and run [test or build command] to check that it works. Show me a summary of the changes when you're done, and ask before deleting any files or running anything destructive.
Software & DevOps

Port a Chrome extension to Safari

The author had ChatGPT take the Session Buddy extension source from Chrome, port it to Safari and install it, taking about 20 minutes.

ChatGPT