Your task page is now a conversation

Paperclip v2026.824.0, released August 24, changes the default. The task page is now both a conversation with the agent doing the work and the place where you steer that work. The release also adds in-product Claude and Codex sign-in and managed runtime previews over Tailscale HTTPS. The changelog covers the rest of the release’s 172 commits, from the sandbox capability contract to resumable company imports.

Chat-style tasks are the default

The previous release shipped the chat-style task view as an experiment. This release makes the updated task detail page the default for everyone.

The new view is conversational and easier to scan. Human comments use bubbles, agent comments remain unboxed, and agent calls nest inside the thread. Progressive disclosure keeps the sub-task tree out of the way until needed. A right sidebar keeps task properties, plans, and artifacts close.

The thread carries live state. A blocked task links its blockers and shows each blocker’s work in order. A live run shows an in-flight notice instead of a false alarm.

Onboarding is chat-first too. The wizard ends inside your first task’s conversation, where the agent greets you, asks clarifying questions, and proposes a plan that you approve item by item.

The Classic Task Interface remains available under experimental features, but chat-only features are unavailable there. We expect to sunset the Classic interface as we continue improving the new version.

Sign in to Claude and Codex from inside Paperclip

A conversation needs a signed-in agent on the other side. Creating that agent used to stall at sign-in. On both Test lanes, the new-agent page now offers Claude subscription login before the agent exists. Your first exchange with a new agent is now work, not setup.

The login runs in an isolated sandbox. Only the person who started the login can finish it. The flow delivers the token once.

Codex follows the same pattern. Its sandbox device login promotes the credential only after readiness checks, then deletes the sandbox.

On a managed platform edge where proxy peer addresses cannot be reliably allowlisted, set CLAUDE_LOGIN_EDGE_TLS_TERMINATED=true to declare that the platform edge terminates TLS. The promoted device-login credential survives managed-home re-seeding.

Managed runtime previews over Tailscale HTTPS

Steering from the thread breaks down at a link you cannot open. A managed worktree runtime used to listen on loopback HTTP. The preview an agent started was real, but a phone or second computer could not reach it.

Paperclip can now expose that preview at a real HTTPS URL on your tailnet. The device where you read the conversation can open the preview, too.

A least-privilege broker on the host authorizes every mapping, confines previews to a fixed port range, refuses protected ports, and records every grant in an append-only audit log.

One issue’s preview cannot collide with or adopt another issue’s preview. Any mismatch fails closed and names the conflict. When the host broker is available, eligible Paperclip-managed worktree runtimes default to HTTPS. Unmanaged and custom services do not change.

Before you upgrade

Migrations run automatically on startup. Four changes deserve attention:

1. If you prefer the pre-chat page, set enableClassicTaskInterface. This preference replaces enableTaskChatRedesign.
2. Eligible Paperclip-managed worktree runtime previews default to Tailscale HTTPS when the host broker is available; unmanaged and custom services do not change. Use PAPERCLIP_MANAGED_RUNTIME_HTTPS=off to opt out; use force to fail closed without the broker. API callers must handle the two new 409 conflict responses on runtime control routes.
3. The removed keys are inert; delete them when convenient: streamAgentSessionOutput, Daytona’s useSessions, and Daytona’s useLogStream. Paperclip now bases streaming and sessions on each provider’s verified capabilities and falls back to polling.
4. The default agent run JWT TTL now matches the documented 48 hours. If you relied on the implicit one-hour TTL, set PAPERCLIP_AGENT_JWT_TTL_SECONDS.

Where to start

Upgrade, open a task with an agent on it, and reply in the thread. The page that kept the record is now built for the back-and-forth.