Agent sessions
Every turn arrives as structure you can read — messages, reasoning, plans, tool calls, process detail and changed files — and sessions stop, fork or resume without losing the thread.
Your agents. Your workspace. Your control—from prompt to commit, desktop to mobile.
Pair your phone once, then review progress, answer permission requests, and continue the conversation away from your desk. The desktop still owns the work.
Trace the runtime handoff for worktree merges and tighten the timeline rendering.
A character-grid client ships beside the desktop app, in the package you already installed. It draws the same transcript, the same approvals and the same session list — over SSH, in tmux, on a machine with no display server.
Nine surfaces of one native workspace: ask an Agent to change code, watch the turn stream in, run the project, review the diff, and keep the session wherever you are.
Every turn arrives as structure you can read — messages, reasoning, plans, tool calls, process detail and changed files — and sessions stop, fork or resume without losing the thread.
Browse the project tree, search file names or file contents, and read or write with revision checks — encoding, line endings and large-file limits stay explicit.
Status, history, diffs and blame sit beside the conversation, with staging, commits, branches, fetch and push — and isolated worktrees whose merges stay guarded.
Native PTYs with ANSI emulation, tabs, resize, scrollback and search run next to the session — and Markdown, images, PDFs and Office files open in the same workbench.
Privileged actions pause for your decision with the command and its working directory in front of you, and agents can collect structured answers with typed forms mid-turn.
Discover Agent runtimes, enable the ones you want, choose models and reasoning depth, and authenticate providers — provider profiles stay separate from the online route.
Import, validate and scope MCP servers and reusable Skills and Prompts from one Config Center, so agent context never scatters across unrelated home directories.
A project is a folder you register; a workspace is how you use it. Work in the current checkout or let Vibex create an isolated Git worktree — each with its own sessions, files, Git and terminals.
Token accounting per session, model and project — requests, input, output, cached reads and hit rate — with desktop notifications and timelines that recover across restarts.