RTVision T3 Code 0.0.68

RTVision T3 Code 0.0.68

This release brings upstream's new orchestrator to RTVision, with saved message queues, richer thread context, and more ways to recover interrupted work.

• Queued messages are saved on the server. Edit, reorder, or remove them above the composer, or steer a supported running turn. After a server restart, the queue stays held until you choose Resume.
• Attach another thread as context by typing @ and its title, or dragging it from the sidebar. The agent retrieves that thread's history when needed. References stay within the same server.
• Continue interrupted or limited turns with Resume. When a provider reports its reset time, use Resume at reset or enable Auto-resume limited threads in Settings → General. The server must be running to continue work; overdue continuations resume after a restart.
• Follow delegated work in Agents. Subagent questions and approvals appear in the parent thread. Expand activity summaries to inspect commands, status, and tool inputs.
• Add providers from the official ACP Registry in Settings → Providers, including Antigravity. OpenCode 2 is supported, and Cursor can sign in through the app while connected to a remote environment.

RTVision's Gitea reviews and CI tools, PR dependency navigation, diff search, Vim navigation, Neovim terminal editors, WSL/SSH connections, and low-disk warnings carry forward. Windows links and image paths stay intact, and Claude MCP activity shows tool names and icons. Failed background-server upgrades preserve the legacy database and stop an uncertain migration from being reused. Linux downloads include both AppImage and Debian packages.

Update your desktop app and every local or remote server together. Older clients and servers cannot connect across this protocol change. Settings → Connections identifies the machine that needs updating. See the update guide for remote and command-line installations.

Older threads appear automatically; large transcripts may load in stages. Their first new message starts a fresh provider session with selected conversation context. Old checkpoints, diffs, tool activity, approvals, and plans are not carried into the new timeline. The original history is preserved separately, but conversations written after migration do not sync between versions. The desktop app uses a separate browser profile, so embedded websites may require signing in again. Back up important server data and read the thread migration guide before continuing important older threads.

Desktop installers are unsigned. Node installations use @rtvision/t3 from https://npm-registry.rtvision.com/.

On Alpine/musl, manual npm installs need npm_config_build_from_source=true for node-pty. Managed service updates already set it. Linux npm installs retain an existing limitation in native resource telemetry because the bundled monitor lacks execution permission.