Repository navigation
1.4.0
What's changed
Highlights
web_fetch: the agent reads a public web page or API and checks versions, releases, and dates against the official source instead of answering from memory. HTML comes back as Markdown without navigation; long results are bounded with the full text saved in the workspace. No key needed; private, loopback, and link-local addresses are refused, including through redirects.- OCI sandbox on nerdctl, Podman, or Docker: mikan detects the engine (nerdctl → Podman → Docker);
CONTAINER_ENGINEpins one. - Sandbox image follows mikan:
--sandbox=ociwithout an image usesghcr.io/geminixiang/mikan-sandbox:<mikan version>. mikan pulls it in the background at startup, replaces a stopped office's container when the image changed, and after any replacement removes the previous image once no container uses it, keeping an image that still has another name.
Notable changes
--sandbox=image:<image>is renamed--sandbox=oci:<image>.image:still works with a deprecation warning until the next major release.- Container tools run through Pi's
pi-envdaemon: operations take about 1 ms instead of 40–180 ms, and commands end when mikan disconnects. String commands usebashwhen available. - Each office with a running container keeps one
<engine> exec -iclient process on the host for itspi-envconnection. - Containers get the host's time zone; the sandbox image no longer hardcodes
Asia/Taipeiand is about 390 MB smaller (novim,nano,less, and similar interactive tools).
Security
- With a vault resolver, a tool call that arrives before the conversation's environment is resolved fails instead of running on the host.
- Container credentials travel over the
pi-envconnection, not command arguments or a host-side env file.
Upgrade steps
- Existing containers are recreated once on first use. Workspace and vault mounts are kept; packages installed inside the container are not.
- On a host running more than one container engine, mikan may switch engines; set
CONTAINER_ENGINE=dockerto keep Docker. - Replace
image:withoci:in PM2 ecosystem files or start scripts, or use--sandbox=ocito follow mikan's version. - Deployments that reach the web only through an HTTP proxy cannot use
web_fetch.
Verification
- CI passes on the release commit; the Slack E2E suite passed on the 1.4.0-beta.0 commit.
- 1.4.0-beta.0 ran on a production deployment: no new errors or restarts;
web_fetch, the browser tool, codemode with MCP, and sandbox commands completed in real conversations. web_fetch: 10 current-fact questions with a real model went from 2 correct to 10 correct.- Sandbox: Pi environment conformance and real-container tests pass on Docker, Podman, and nerdctl.
See CHANGELOG.md for details.