Use Development Tools

Start a pod from the current image and workspace seed. Give it a task-oriented title; the title can change without changing the pod’s identity.

Stopping a pod retains its private state. Destroying it removes its writable filesystems, chats, and retained processes, so preserve valuable changes first.

Open a Terminal

Terminals start in /workspace with the pod’s user environment and a live pseudo-terminal. Closing a tab does not guarantee that its process exited.

The Processes view shows supervised commands, lifecycle state, exit results, and captured output. Use the normal terminate action first, then choose a specific signal when needed:

• Interrupt behaves like Ctrl+C.
• Hang up disconnects a terminal-oriented process.
• Terminate requests an orderly shutdown.
• Kill stops it without cleanup.

The same controls are available through podctl processes.

Edit Code

The Code view starts code-server inside the selected pod. It has access to the same workspace, environment, and tools as the terminal. Its workspace-level profile keeps settings and extensions available across pods.

Inspect and Edit Files

The Files view lazily browses /workspace and the pod’s attached shares. Text previews use syntax highlighting, Markdown files offer rendered and source representations, and PDFs and images use dedicated viewers. The view does not follow symbolic links, preventing traversal outside the selected file root or through recursive links.

A link such as [configuration](/workspace/project/config.toml) in an agent message opens the same file viewer over the chat.

For an existing UTF-8 file no larger than 2 MiB, choose Edit in the Files view or chat preview to open the lightweight editor. Tascarrel records a content revision, a fingerprint of the bytes loaded into the editor. A save succeeds only if the file still matches that revision. If an agent or another tool changes the file first, Tascarrel retains the browser draft and requires an explicit reload. Files in read-only shares, binary files, and larger files remain preview-only.

While editing Markdown, switch between Source and Rendered to inspect the current browser draft without saving it first. Switching representations preserves the draft.

Use the Code view when a change requires the full code-server environment, including extensions or language servers.