Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions agentctl/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,11 +12,13 @@ Agents. The Rust workspace version is a build detail and is not tracked here.

## [Unreleased]

## [0.1.0-preview.13] - 2026-10-26

### Added

- Agents' instructions now start with a short Agent sandbox section from `agentd`, listing the Agent's CPUs, memory and disk, harnesses, secrets and their hosts, network, access, and whether nested Agents can run. An instruction file from the image or `spec.home` keeps its text below it. Every Agent also gets an `agentctl` skill for driving Agents, including nested ones. ([#284](https://github.com/digdir/digdir-agents/pull/284))
- Agent images that run nested Agents can copy `agentctl` and `agentd` from `ghcr.io/digdir/agentctl`, tagged by release, `main` or `sha-<commit>`, instead of building them. ([agentctl image](https://github.com/digdir/digdir-agents/tree/main/images/agentctl), [#282](https://github.com/digdir/digdir-agents/pull/282))
- `spec.sandbox.resources.nestedSandboxes` lets an Agent run Sandboxes of its own, such as nested Agents: `required` fails on a host that cannot provide them, and `preferred` runs without them there. With Microsandbox they need Linux x86_64 with nested KVM, or an Apple M3 or newer with macOS 15 or newer. Agent setup lets the `agent` user open `/dev/kvm`, so images no longer need to grant it. The self-dev Agents prefer them. ([#231](https://github.com/digdir/digdir-agents/pull/231))
- `spec.sandbox.resources.nestedSandboxes` lets an Agent run Sandboxes of its own, such as nested Agents, on Linux x86_64 with nested KVM or an Apple M3 or newer with macOS 15 or newer. `required` fails on other hosts, and `preferred` runs without them there. Images no longer need to let the `agent` user open `/dev/kvm`. ([#231](https://github.com/digdir/digdir-agents/pull/231))
- Sessions know where they run: `AGENT_NAME`, `AGENT_SESSION_NAME`, `AGENT_HOST`, `AGENT_SOURCE_DIRECTORY` and `AGENT_HARNESS` are set for the harness, so instructions can ask an agent to name itself and tools can suit its model. ([#206](https://github.com/digdir/digdir-agents/pull/206), [#263](https://github.com/digdir/digdir-agents/pull/263))
- Images built on the base images can add Podman, the `docker` command and Docker Compose, usable by the agent user from boot, with `agent-feature install containers`. ([features](https://github.com/digdir/digdir-agents/tree/main/images/agentctl-base#features), [#266](https://github.com/digdir/digdir-agents/pull/266))
- The tmux status bar in a session shows its name and the keys to detach, open a shell beside it and move to the next window. ([#206](https://github.com/digdir/digdir-agents/pull/206))
Expand Down Expand Up @@ -45,8 +47,11 @@ Agents. The Rust workspace version is a build detail and is not tracked here.

- Large builds in new Agents built on the base images can use the available disk space in `/tmp`. Existing Agents need an updated image, removal of any `/tmp` tmpfs mount, and recreation after saving work. ([temporary files](https://github.com/digdir/digdir-agents/tree/main/images/agentctl-base#temporary-files), [#329](https://github.com/digdir/digdir-agents/pull/329))
- `agentctl tui` no longer searches every folder below the current one for manifests to create an Agent from when it is not run inside a git repository, which was slow from a home directory and offered manifests from every checkout. Outside a repository it offers `agent.yaml` and `agents/*/agent.yaml` in the current folder, with their variants. ([#283](https://github.com/digdir/digdir-agents/pull/283))
- Under WSL, `agentctl claude login` opens the sign-in page in the Windows browser instead of appearing to hang, and `agentctl` opens addresses there too. Where no browser would reach you, such as over SSH, the login shows the sign-in link to open on any device and asks you to paste the token, even when it wraps over several lines; `AGENTCTL_OPEN=copy` asks for that anywhere. A browser sign-in that does not complete within 5 minutes stops instead of hanging. ([#270](https://github.com/digdir/digdir-agents/pull/270))
- In Agents with Podman, `podman` and `docker` run by the agent user use the Agent's shared Podman everywhere, such as in systemd units and cron, not only in Sessions, `agentctl exec` and SSH logins. Elsewhere they fell back to rootless Podman, which fails. Those no longer get `CONTAINER_HOST`; Podman's configuration in the agent's home points at the shared Podman instead. ([#266](https://github.com/digdir/digdir-agents/pull/266))
- `agentctl claude login` no longer appears to hang: ([#270](https://github.com/digdir/digdir-agents/pull/270))
- under WSL, it opens the sign-in page in the Windows browser, as `agentctl` now does for every address
- where no browser would reach you, such as over SSH, it shows a link to open on any device and asks you to paste the token. `AGENTCTL_OPEN=copy` asks anywhere
- a browser sign-in that does not complete within 5 minutes stops
- In Agents with Podman, `podman` and `docker` run by the agent user use the Agent's shared Podman everywhere, such as in systemd units and cron, instead of failing outside Sessions, `agentctl exec` and SSH logins. Those no longer set `CONTAINER_HOST`. ([#266](https://github.com/digdir/digdir-agents/pull/266))
- Node.js programs in an Agent, such as `npm`, `corepack` and Pi, no longer fail with `self-signed certificate in certificate chain` in Sessions, `agentctl exec` and SSH logins. Restart a running Agent with `agentctl stop` and `agentctl start` to fix its Sessions. ([#235](https://github.com/digdir/digdir-agents/issues/235))
- In Agents, Claude Code in bypass permissions mode no longer stops to ask before running Bash commands such as `rm`, whether in a Session, T3 Code or `agentctl ssh`. Other prompts still appear, and so do Bash prompts in modes that ask for approval. ([#237](https://github.com/digdir/digdir-agents/pull/237), [#292](https://github.com/digdir/digdir-agents/pull/292))
- Claude Code in an Agent no longer deletes conversations after 30 days. Before, running it outside a Session, such as in T3 Code, deleted old conversations, including those of Idle Sessions. ([#292](https://github.com/digdir/digdir-agents/pull/292))
Expand Down
Loading