Dashboard, Chat, Terminal, and Files

The dashboard is the main browser view for checking on an agent and managing it without leaving the product.

Use it when you want visibility into the agent and a stable place to open the controls around it.

Chat gives you a direct way to work with the agent inside the app. Terminal sessions are there when you need hands-on setup, debugging, or command execution.

Most work should feel simple from chat and dashboard views, but the terminal is available when you need lower-level control.

Open Vassal lets you view the workspace, upload inputs, and download outputs without bouncing between separate tools.

That makes it easier to keep the agent, its files, and the work product in one operational flow.

This matters because a lot of practical agent work depends on reference files, draft outputs, logs, and other artifacts that need to stay close to the runtime.

Keeping those files in the same operational surface reduces handoff friction and makes it easier to understand what the agent actually used.

The dashboard is usually the first stop for visibility. Chat is the fastest path to day-to-day work. The terminal is what you use when you need hands-on control. Files are how the runtime stays grounded in actual inputs and outputs.

Those tools are not separate products. They are different levels of access around the same hosted agent.

That is why they matter for operations: you can move from high-level work to lower-level inspection without switching systems or losing context.