Getting Started
Sign in
Open app.viberglass.io and sign in with the credentials your admin gave you. Viberglass uses email/password auth with optional Remember me sessions.
The dashboard
The left sidebar has two sections: Platform (global navigation) and Projects (your linked projects).
Core concepts
- Project — a workspace bound to one source code repository. Tickets, claws, jobs, prompt templates, and integration links all live inside a project.
- Ticket — a unit of work: a bug, feature request, or task. Tickets can be created from the web UI, from Slack, from a webhook (GitHub, custom), or by scheduled claws.
- Workflow Phase — every ticket moves through up to three phases: Research, Planning, and Execution. Each phase produces a document that you can review, revise, and approve.
- Job — a single execution of an agent against a ticket or claw. Jobs have a duration, a status (queued, running, completed, failed), and a kind (research, planning, execution, claw).
- Clanker — a saved configuration for an AI worker. A clanker bundles together an agent (Claude Code, Codex, Gemini CLI, etc.), a deployment target (Lambda, ECS, Docker), and the secrets the agent needs.
- Claw — a scheduled task. A claw combines a task template (the instructions to run) with a schedule (interval or cron) so the platform can run the same job over and over.
- Secret — an API key or token managed in the Secrets page. Secrets are stored in AWS Systems Manager Parameter Store and injected into worker containers at runtime.
- Integration — a connection to an external system: GitHub for ingesting issues and pushing PRs, Slack for tickets and approvals, custom webhooks for everything else.
Your first run
- Open a project from the sidebar (or create one).
- Create a ticket — write a description, pick a severity and starting phase.
- Watch it run — a clanker is dispatched and the ticket page shows live progress through Research → Planning → Execution.
- Review the plan — when planning finishes, read the document, revise it if needed, and approve it.
- Approve and execute — the agent commits its changes and opens a pull request.
See Ticket Lifecycle for the full phase, revision, and approval flow.