All stories
AgenC Core Ecosystem Community reports

AgenC fixes the dead end when a coding agent needs network approval

Version 0.19.9 lets sandbox-blocked package installs and clone commands seek an approved retry instead of telling the model that approval is unavailable.

By AITrending2 min read
Sources (4)

Why now The original release was published October 17 at 10:24:43 UTC and documents a specific execution fix, not just repository activity or an older benchmark score.
Author-published AgenC terminal demonstration showing test execution and read-before-edit checks in a checkout service.
Still from the demonstration embedded in the v0.19.9 English README. It illustrates the terminal interface, including its displayed never-asks mode; it is not a demonstration of the new default-mode network approval retry or an AITrending test. Full frame preserved. Source: tetsuo-ai / AgenC Core contributors

A blocked install can now ask for the next step

AgenC Core 0.19.9 addresses a frustrating coding-agent failure: a command loses network access inside the sandbox, but the model is told that approval is unavailable. The October 17 release says the default permission mode now supports one retry with the user’s approval for cases such as npm install, git clone and pip install.

Previously, the developer says, the model could give up or request narrower permissions that still failed. The update also recognizes less obvious network failures: silent curl -s and wget -q output, plus npm’s ENOTFOUND error on macOS. These are the project’s stated fixes; AITrending has reviewed the release and documentation but has not reproduced them across operating systems.

The distinction is between requesting permission and assuming it. The release says that when an operator has explicitly selected --bypass-approvals, the model is instead told that the retry will run without asking. That setting should not be confused with the ordinary approved path or a general guarantee of confinement.

The agent harness remains separate from the model

AgenC is the standalone agenc runtime, with a local daemon serving its terminal interface, headless commands and background sessions. It can use different hosted providers or configured local models; the selected provider supplies inference. The MIT software license does not include that provider’s access or usage charges.

Existing standalone installations update with agenc update; npm installations can select npm install -g @tetsuo-ai/agenc@0.19.9. The release then asks users to run agenc daemon restart. The documented npm runtime requirement is Node.js 26.5 or later within the 26.x line, while standalone packages include their own runtime. Installation routes cover macOS, Linux and Windows.

Platform support has an important boundary: the Windows guide says native restricted sandboxing is not implemented. Its interactive setup asks whether to continue without that sandbox; approvals still apply. A network-retry fix does not remove that limitation or certify arbitrary commands as safe.

Two smaller changes round out this release: the first Browser call can open its page when the model names tab 1 before any tab exists, and /status gives a clearer message when git is missing. The main practical improvement is a recoverable approval step where an agent previously reached a dead end.

Related reading