Workspaces

Workspaces is Usejarvis’s built-in environment for working on web projects. In the dashboard it lives in the build cluster as the Workspaces room; the underlying config block and API keep the older sites name.

It is not a replacement for your editor or git tooling in every case. It is a product surface that lets Usejarvis operate on projects directly through the dashboard with an opinionated workflow around previews, files, git state, and project chat.

What Workspaces Includes

• the Workspaces room in the dashboard navigation
• project tabs
• dev server lifecycle management
• file tree and file editing views
• project-scoped chat
• git-aware project status
• GitHub connection support
• project scaffolding from templates: vite-react, vite-vue, vite-svelte, vite-vanilla, next, bun-react

Previews are proxied through the daemon, so you do not need to expose each dev server port.

Agent Tools

Usejarvis can drive projects itself, not only through the UI. The agent has project tools to create projects, read, write, delete, and list files, run commands in the project directory, commit, and push to GitHub. You can ask it to build or change a project end to end from chat.

What a Project Tracks

Each project tracks data such as:

• name
• path on disk
• framework
• dev server status and port
• current git branch
• dirty/clean working tree state
• GitHub URL if connected

Typical Workflow

1. Open the Workspaces room
2. Create or open a project
3. Let Usejarvis start the dev server
4. Use the file tree and project chat together
5. Preview the running project
6. Inspect git status and project changes

Configuration

The workspace is controlled by the sites config block:

sites:
  enabled: true
  projects_dir: "~/.jarvis/projects"
  port_range_start: 4000
  port_range_end: 4999
  max_concurrent_servers: 3

File edits made through Usejarvis are auto-committed to the project’s git history, so changes are always recoverable.

Good Use Cases

Workspaces is especially useful when you want:

• Usejarvis to work on a contained web project
• a built-in preview workflow
• project chat tied to a specific project context
• a quick way to inspect dev server and git state in one place

Use Workspaces when the work should stay attached to a single web project and its files; use the main conversation surface for everything else.