Paperclip

Paperclip adds IBM Bob Shell adapter as managed company agent

Paperclip introduced an adapter for IBM Bob Shell, integrating IBM's enterprise CLI into company organizational rosters with MCP tool support. Native child-agent review handoffs merged with typed reviewer admission, and experimental durable VMs allow environments to survive agent exit.

← Back to homeOriginal source ↗

Paperclip opened PR #13585 on September 17, 2026, contributing a dedicated adapter for IBM Bob Shell (bob run). The integration allows enterprise teams using IBM's developer agent CLI to manage it as an automated employee within Paperclip's company hierarchy, complete with task assignments, server-side session persistence, and Model Context Protocol tool access. In parallel, Paperclip merged PR #13581 to fix native child agent review handoffs, ensuring that assigned reviewers can inspect and approve delegated tasks without invalidating parent locks, and introduced PR #13575 to support persistent virtual machine environments via exe.dev that outlive individual agent execution runs, preventing dev server teardown between task iterations.

The facts

- PR #13585 adds packages/adapters/bob-shell/, bringing IBM Bob Shell CLI agents under Paperclip's multi-agent governance interface. - Supports task ID session persistence, file mentions, and Model Context Protocol tool integrations exposed by the Bob Shell runtime. - Merged PR #13581 establishes typed reviewer admission so native review handoffs complete without transferring primary task ownership away from the assignee. - PR #13575 introduces experimental persistent exe.dev VM environments with dedicated leases, private HTTPS previews, and SSH runner access. - Release v2026.916.0 was published on September 16, 2026, consolidating prior sandbox provider enhancements.

Why it matters

Enterprise agent adoption is converging on multi-agent orchestration frameworks where different specialized agent runtimes—ranging from Anthropic Claude and OpenAI Codex to enterprise tools like IBM Bob Shell—operate within a unified organizational structure. By adding first-class support for Bob Shell and fixing reviewer handoff locks, Paperclip makes it possible for corporations to govern diverse vendor agents under consistent budget, security, and approval rules, bridging proprietary corporate toolchains with open execution platforms.

Current

Inspected on 2026-09-18. The Paperclip stable-channel baseline is v2026.916.0 published 2026-09-16T18:15:11Z. The primary source was open (not merged) when captured. Mainline merges, open proposals and packaged releases are distinct availability states; the release baseline does not establish that a proposal has shipped.

Evidence

Primary evidence: paperclipai/paperclip PR #13585 (https://github.com/paperclipai/paperclip/pull/13585). Supporting context: paperclipai/paperclip PR #13581 (https://github.com/paperclipai/paperclip/pull/13581); paperclipai/paperclip PR #13575 (https://github.com/paperclipai/paperclip/pull/13575). The source bodies and linked context were inspected. Test results quoted from contributors remain attributed reports, not independently reproduced experiments.

Operator take

Adding IBM Bob Shell indicates that enterprise IT departments are looking to integrate proprietary internal tools with open multi-agent management platforms. The review handoff repair is equally critical: in hierarchical agent workflows, delegating a review must not orphan the parent task or strip the original assignee's context. Organizations operating multi-agent swarms require clear separation between assignee authority and reviewer approvals.

Caveat

The IBM Bob Shell adapter requires a functioning local or remote Bob CLI installation and access credentials. The exe.dev persistent VM integration remains behind an experimental feature flag and requires separate infrastructure accounts. Review handoffs still require explicit parent wake subscriptions.

The IBM Bob Shell adapter requires a functioning local or remote Bob CLI installation and access credentials. The exe.dev persistent VM integration remains behind an experimental feature flag and requires separate infrastructure accounts. Review handoffs still require explicit parent wake subscriptions.