ViberglassViberglassDocs
← Back to site

Viberglass Documentation

How to use Viberglass with your team, and how to run it. Viberglass is a self-hosted workspace where people and coding agents work on the same tasks: someone asks for a change, an agent writes a plan, the team discusses it, and the agent builds it as a GitHub pull request. For work that isn't code, a space can keep shared files instead of a repository, and the agent delivers documents and presentations there.

Using Viberglass

For product managers, support and QA leads, designers, reviewers and engineers.

  • Getting started: the words Viberglass uses, what you see when you sign in, and what your role lets you do.
  • Tasks: asking for something from the web, Slack or an issue tracker, and the task's thread.
  • Plans and reviews: asking for a plan, commenting on it, answering the agent's questions and bringing people in.
  • Building and pull requests: building the plan, plans in parts, pull requests and finishing a task.
  • Files and artifacts: spaces without a repository, their shared files, and the documents and presentations agents make there.
  • Steering the agent: pausing, interrupting, taking over the branch yourself and handing it back.
  • Home and notifications: what needs you, Overview, Slack DMs and email.
  • Slack: starting and following tasks from a Slack thread.
  • Schedules: agent work that runs on a timer.
  • Chrome extension: creating a task from the page you're on, with a screenshot and the page's details.
  • MCP server: working with Viberglass from Claude, Cursor or another MCP client.

Running Viberglass

For whoever installs and looks after the workspace.

Next
Getting started