Skip to content

OctoShell v0.3.1

Choose a tag to compare

@github-actions github-actions released this 06 Oct 02:13

This release fixes how OctoShell holds the output of commands an agent runs over ACP.

Long command output was trimmed at the wrong end. When a command produced more output than the byte limit, OctoShell kept the start and dropped the rest, so a build or test run that printed its progress and then failed showed the progress and not the failure. The oldest output is dropped now, and the end, where the error is, stays.

Output is also decoded correctly across read boundaries. Greek text and the symbols test runners print no longer turn into question marks when they happen to fall on the edge of a read.

A command's output stays visible after the agent finishes with it, instead of the block emptying out.

Download the build for your machine, then:

macOS — open the .dmg and drag OctoShell to Applications. The build is for Apple Silicon (M1 and later); there is no Intel build.
These builds are unsigned, so the first launch is blocked with "Apple could not verify OctoShell is free of malware". Open System Settings → Privacy & Security, scroll to Security, and click Open Anyway next to OctoShell, then launch it again. (Control-click → Open no longer works for unsigned apps on macOS 15 Sequoia and later.) From a terminal, xattr -dr com.apple.quarantine /Applications/OctoShell.app does the same thing in one step.

Windows — run the installer. SmartScreen will warn because the build is unsigned: More info → Run anyway.