Classic confinement request: agent-console

store-requests
1

Hello! I’m requesting classic confinement for agent-console (https://github.com/cyl-castillo/agent-console, MIT licensed).

Agent Console is a desktop developer tool (Tauri/WebKitGTK): a minimalist console for supervising AI coding agents (Claude Code, Codex CLIs) working inside the user’s own repositories. It embeds a PTY terminal that runs the user’s login shell, and its core function is launching and supervising CLIs the user has installed on the host — claude, codex, node, git — in arbitrary project directories chosen by the user. It also reads and writes ~/.claude (the Claude CLI’s own config/hooks/session state), which must be the same files the host CLI uses.

Why strict confinement is not viable:

  • The app’s primary function is executing host-installed binaries (claude, codex, the user’s shell, git, node) — not bundleable: they are user-installed, user-updated tools (e.g. the Claude CLI updates through npm and carries the user’s authentication).

  • It must operate on arbitrary project directories the user opens (like an IDE), and share dotfile state (~/.claude, ~/.codex) with those host tools.

This matches the supported classic category of IDEs / developer tools that orchestrate host toolchains (code, goland, etc.).

The snap repacks the same .deb we publish on GitHub Releases (build reproducible from CI: .github/workflows/snap.yml in the repo).

Thanks!

2

This request has been added to the queue for review by the @reviewers team.

3

Hi @cyl-castillo

There might be technical reasons why the snap requires classic confinement to be fully functional. However, classic confinement it is a sensitive matter and it is reserved for mature, well-known applications published by mature, well-known entities. As of today, I believe that agent-console doesn’t meet this criteria because of the following reasons:

  • The project seems to be very fresh, according to the upstream repository

  • The projects seems to have little/none community around according to upstream repository (contributors, issues, PRs, etc.)

  • I could not find evidences that the project has a strong enough user base currently

Considering all these factors, I think agent-console should not get classic confinement as of now.

Thanks

4

Thanks for the review and the clear criteria, @jslarraz — that’s fair. The project is indeed young. We’ll keep building in the open and come back to this request once agent-console has the maturity and community track record you describe. If there are rough milestones the reviewers typically look for (age, contributors, adoption signals), I’d appreciate a pointer so we can return with the right evidence. Thanks again!

1 Like
5

Hey @cyl-castillo

If there are rough milestones the reviewers typically look for (age, contributors, adoption signals), I’d appreciate a pointer so we can return with the right evidence. Thanks again!

There is no concrete thresholds as it may depends on many factors. Some AI applications have become mature and well-known in very reduced period of time, and adoption signals will likely be different for a general purpose tool, such an audio recorder app, than for a niche tool used in a concrete research discipline. Thus, I’m afraid I cannot point to concrete numbers here.