Skip to content

[0.1.4] - Enhanced abilities

Latest

Choose a tag to compare

@lordprime lordprime released this 09 Nov 22:25
6bb35f1

Added

  • Six more CLI agents. Seats can now also run on GitHub Copilot CLI (copilot-cli),
    Kiro CLI (kiro-cli), Qwen Code (qwen-cli), opencode (opencode-cli), Goose
    (goose-cli) and Mistral Vibe (vibe-cli). They work like Claude Code, Codex and the Gemini
    CLI:

    • each CLI's own tools are turned off, by flags, environment, or a root-owned policy file in the
      runner image that users cannot override;
    • the runner stops any turn where a CLI reports tools of its own;
    • sessions are resumed, and usage limits trigger the seat's fallback.

    How each one signs in:

    • Copilot, Kiro and opencode sign in from Connections > CLI agents with device codes:
      • Kiro with AWS Builder ID, Google or GitHub;
      • opencode with GitHub Copilot or ChatGPT.
    • Qwen Code, Goose and Vibe use per-user API keys. For Qwen Code, opencode and Goose you also
      choose which model provider the key is for (migration 0023 adds cli_credentials.provider).

    The new CLIs are off until an operator lists them in ARGUS_CLI_AGENTS_ALLOWED. The runner
    image pins:

    • @github/copilot 1.0.108, @qwen-code/qwen-code 0.27.1 and opencode-ai 1.19.5;
    • Kiro CLI 3.1.0 and Goose 1.57.0, by SHA-256;
    • mistral-vibe 3.1.0, hash-pinned.

    Cursor CLI, Amazon Q Developer CLI, Charm Crush and Amp were evaluated and left out (see
    docs/cli-agents.md).

  • Sign CLI agents in from the web UI. Connections > CLI agents has Sign in and Sign out
    for Claude Code, Codex and the Gemini CLI.

    • The runner starts the CLI's own login in your runner HOME. The page shows only the vendor link
      and one-time code the CLI prints, and passes a pasted authorization code straight to the CLI.
    • Tokens stay in the runner as before. Argus never contacts the vendors' sign-in services or reads
      the login.
    • Only you can sign in your own CLIs: interactive sessions only, rate-limited, audited.
    • No sign-in when ARGUS_CLI_AGENTS_ALLOW_SUBSCRIPTION=false.
    • ./scripts/agent-login.sh remains for operators.
  • Live browser. Agents can browse the web read-only in a real browser, and you can watch each
    agent's browser live in the run view. Install it with ./scripts/deploy.sh --with browser.
    The browser runs in its own container on an internal network, and its only way out is a new
    egress proxy that refuses private, loopback and link-local addresses. A new Browser view
    keeps a screenshot of each page opened (up to 50 per agent), and browser use is recorded in the
    ledger as protocol browser. Form submissions and downloads are blocked; the threat model
    (TM-13) lists what is left. Councils created before the browser was available (before 0.1.4) do
    not get browse automatically, since saved seats keep their tools: add browse to the Tools
    of each seat that should browse, in the council's seat editor.
    Chrome's own calls to Google services (search preconnect, network time, autofill, captive
    portal checks) are turned off by switches and a managed policy in the image, so egress sees only
    the pages agents open. ARGUS_BROWSER_LOG_LEVEL=DEBUG logs the browser's per-page CDP trace.

  • Skill trace. See which agent loaded or read which skill, exactly what it received, and the
    tool calls made with it. Skill use is recorded in the ledger.

  • Feature switches. Install the live browser and CLI agents with one command,
    ./scripts/deploy.sh --with browser,cli-agents, and remove them with --without (containers
    stopped and removed, volumes such as users' CLI sign-ins kept). Admins then turn each one on or
    off in Settings → Features, at any time and without a restart; the switch is stored in the
    database, on by default, and recorded in the audit log. The server settings stay the ceiling.
    Switching a feature off applies from its next use, in running runs too: browse is refused, and
    a CLI seat's turn is refused so its fallback route takes over. Each card shows whether the
    feature is installed and its service answers, and the command to install it when it is not. New
    admin endpoints GET /api/v1/admin/features and PATCH /api/v1/admin/features/{key}; a
    migration adds the feature_switches table.

Security

  • The egress proxy (used only by the browser) resolves each host itself, refuses non-public
    addresses and serves only ports 80 and 443. It cannot be told to allow private addresses.

Changed

  • ACP removed. It was merged into A2A; connect remote agents over A2A. Saved ACP remote agents are deleted on upgrade; external ACP clients must move to A2A or MCP.
  • Updating a remote agent now rejects unknown fields (HTTP 422) instead of ignoring them.
  • scripts/deploy.sh now deploys the published release by default (ARGUS_VERSION in
    deploy/.env, latest unless pinned) instead of building the checkout. Add --local to build
    and run the code you have checked out, as plain deploy.sh did before.
  • deploy.sh and update.sh now set ARGUS_BROWSER_URL, ARGUS_BROWSER_TOKEN,
    ARGUS_CLI_AGENTS_ENABLED and ARGUS_RUNNER_TOKEN in deploy/.env from COMPOSE_PROFILES
    and log each change: the compose profile is the only server-side switch. With
    COMPOSE_PROFILES set in the environment, --with and --without refuse to run.

Removed

  • ACP (the Agent Communication Protocol): the /acp routes, the ACP client and ACP remote agents.
    Migration 0022 deletes saved ACP remote agents (logging their names) and drops
    remote_agents.agent_name. Older ledger entries with protocol acp are kept and shown as
    ACP (removed).

Full Changelog: v0.1.3...v0.1.4