Repository navigation
Pi Agent Platform v1.38.1
v1.38.0 was tagged but never published: its release checks failed on two tests. This is the same release.
Tests
tests/managed-terminal-boundary.test.mjs: the Linux fixture says it is a Linux boundary, as the real one does (the macOS Seatbelt path was taken on Linux and failed).tests/managed-network-approval-web.test.mjs: the approval card gets 30 s to appear on slow runners.
Included from v1.38.0 (tagged, not published)
Piagent becomes an editor: files, terminals, inline review and checkpoints in the dashboard, and Bypass that asks nothing (company conversations too, where the Harness allows it).
Added
- Bypass, as in Codex. A new
bypasspermission mode (/permission bypass,piagent-auto --bypass,PIAGENT_PERMISSION_PROFILE=bypass, or Bypass in the dashboard's access menu) turns every Piagent gate off in a personal session: nothing is asked or blocked, deletes, pushes, migrations, external sends and protected or read-only paths included. Tool output is still redacted and each turn still gets its/undocheckpoint. A policy can forbid it by leavingbypassout ofpermissionProfiles.allowedModes. Full access (trusted-full-access) is unchanged. - Bypass in company conversations, where the Harness allows it. A company conversation now has three levels: Ask first, Full access (what the dashboard called Bypass before: asks only what must be confirmed) and Bypass, which asks nothing (internet, Docker, the member's machine, pushes, deploys, migrations) while plain commands stay in the sandbox. Bypass needs the Harness's
bypass_mode(Agent Studio, on by default; an administrator can turn it off) carried by an Agent Watch that knows the field; without an explicit yes it is not offered, and a conversation left in Bypass after it is turned off applies as Full access./bypass on|full|offin the dashboard and inpiagent studio. - Editor-like workspace. Square 2px edges across the dashboard; file and terminal tabs close with their own ×; the files and terminal panels hide with a × of their own; the editor sits above the terminal and both share the window height.
Fixes
-
A checkpoint that cannot be taken no longer stops the agent's edit. Personal snapshots failed on a submodule, a file over 16 MB, a tree over 64 MB or a file changing mid-snapshot, and every write was then refused. Snapshots now hash the whole tree in one Git call (about 0.5 s instead of 35 s on a 4,000-file repository), include tracked files of any size, skip untracked files over 100 MB and leave submodules out. A turn whose snapshot fails has no checkpoint and ends the history before it; only another live owner of the session's history makes an edit wait. Company checkpoints get the same snapshot.
-
Restoring a turn no longer overwrites a file the member saved from the editor during it. Such files are reported as conflicts by
/undoand Timeline restore. -
Checkpoint snapshots stay out of the project's refs. They live in a private repository inside the Git directory that borrows the project's objects, so
git push --mirrorcannot publish untracked files; conversations untouched for 30 days lose their checkpoints. -
The company explorer, editor and review panels no longer wait behind the agent's running command. Reads run beside it (three at a time) and the editor's permission poll no longer stacks requests.
-
A flood of terminal output no longer drops the dashboard connection. Output is paced at about 4 MB/s, the writer is paused while the browser catches up, output it cannot keep up with is marked as skipped, and a terminal tab never stops rendering for good. Company terminal workers pause instead of exiting when their pipe backs up. A flood of short lines no longer stalls the Gateway: tiny PTY reads are joined before pacing and the replay buffer trims its window once it doubles instead of on every line.
-
Restored files the turn had deleted get a new file's usual mode instead of owner-only.
-
Company terminals work on macOS. The company Gateway creates the PTY and starts only the shell under the agent's offline Seatbelt profile, which gains terminal ioctls and
/dev/tty; opening any other terminal stays denied, and nothing runs on the host. Company terminals also write the project's Git directories and package caches like the agent's offline commands, sogo buildandgitin a worktree work. -
Terminals: background jobs stop with their terminal (the shell's tree is watched while it runs); actions refused before anything ran are reported as refused, not "may have run"; a stale revision is resent instead of dropping queued keystrokes;
@terminalnaming no open terminal attaches nothing instead of blocking the message; the personal shell no longer inherits the Gateway'sPI_*/PIAGENT_*variables. -
Editor: Rename and Delete for the open file, applied only to the version shown; new files get the usual mode and their missing folders; creating a file never replaces one that appeared meanwhile; refusals that changed nothing (oversized file, linked folder) are reported as such. Kept hunks survive a page reload in the same browser.
-
Checkpoints: a restore that stopped midway finishes what is left instead of refusing its own work; a refusal before any file changed is reported as refused; a file ignored since the turn is refused rather than overwritten; folders the turn created and its undo emptied are removed; any shell command not provably read-only takes the turn's checkpoint; a lock or capture left by a process from before a reboot, or whose number was reused, no longer blocks.
-
Company inline review preserves exact agent observations across trusted internal snapshot reads; ordinary shell commands still invalidate attribution.
Added
-
Timeline checkpoint restoration previews affected files, requires confirmation and reverses safe turns until a member-edit conflict. Personal
/undoshares the checkpoint service with company mode; personal history is bounded and pins Git trees without changing HEAD or the index. Browser retries retain the same request across tab reloads. -
Company Session Hub terminals run inside the Linux/WSL bubblewrap boundary through the company Gateway and authenticated relay, with no network, credential masking and sandbox process cleanup. Disconnects reconnect for replay without automatically resending commands. Doctor reports prerequisites. The complete browser workflow is qualified on Linux arm64; native Linux x64 and WSL remain unverified.
-
Personal Session Hub terminals open up to four project shells with lazy xterm tabs, resizing, Ctrl+C and reconnect replay. Session teardown cleans terminal processes. Explicit
@terminal/@terminal:2sends attach bounded redacted output. Optional native PTY failures leave the dashboard usable and appear in Doctor; company terminals never fall back to host execution. -
Session Hub reviews exact observed agent hunks inline, with Keep, preview-confirmed Revert, hunk navigation/counts and current/removed-line comments to the composer. Clean tabs refresh after agent changes; dirty drafts retain conflict handling. Company source review and revert run in the existing sandbox. New untracked agent files support review; deletion through hunk revert remains unavailable.
-
Session Hub edits and atomically saves files with Cmd/Ctrl+S, dirty tabs, new files and digest conflicts (Reload/Compare/confirmed Overwrite). Live permission and protected-path checks apply in personal and company mode. Durable receipts prevent duplicate saves; member edits notify the next agent turn and invalidate stale agent edits.
-
Session Hub opens project files in read-only editor tabs, with Files/Search navigation, Cmd/Ctrl+P, line links from tool calls, source changes and @mentions, and a drawer on smaller screens. Protected files stay locked. Company file reads and searches run inside the session's existing sandbox through its Gateway.