Slack

The Slack integration lets you create tickets, advance phases, and approve plans from within Slack.

Launching a job

In any channel where the Viberglass bot is installed, type:

/viberator

A modal opens with four fields:

• Project — pick the Viberglass project the ticket should belong to.
• Clanker — pick the worker that should run the job.
• Mode — research, planning, or execution. This maps directly to the Starting Phase you would pick in the web form.
• Message — what you want done, in plain English.

Click Launch. Viberglass:

1. Creates a ticket in the chosen project.
2. Starts the first agent job for the selected phase.
3. Posts a thread in the channel with a link to the ticket.
4. Streams job progress into the thread and posts the output document when the job completes.

What appears in the thread

While the job runs the bot posts status updates. When it finishes:

• Research or planning job — the bot attaches the completed document (research.md or planning.md) to the thread, followed by a prompt reminding you which keywords move the ticket forward.
• Execution job — the bot posts the pull request URL and a link back to the ticket in Viberator.
• Failed job — the bot posts an error message. Open the ticket in the web UI to read the full job log.

Advancing phases with keywords

Note: The Slack bot needs to be invited to the channel to receive keywords.

Once a job completes, @mention the bot in the thread with a keyword to move to the next phase. Keywords are case-insensitive and punctuation is stripped, so lgtm!, LGTM., and lgtm all work the same way.

Chaining phases

If you say ship it or execute from a research thread, Viberator runs planning to completion and then immediately kicks off execution — you don't need to check in between. The thread will read:

Advancing to planning (will auto-continue to execution)…

followed by the planning document, then the PR link.

Revising

Any @mention that doesn't match a keyword above is treated as revision feedback. The bot queues a new job with your message as the revision instruction and streams the updated document back into the same thread.

Execution is final

Once a ticket is in the execution phase, keyword commands and revision requests are both rejected. If the result isn't right, create a new ticket.

Approval cards

During execution the agent may pause and ask for your sign-off before taking a destructive or irreversible action. The bot posts an Approval Required card with Approve and Reject buttons directly in the thread. These work independently of the keyword system — clicking a button sends the decision back to the running agent.

When the job goes quiet

If nothing new appears in the thread for a while:

• The job may have completed — look for the document attachment or PR link.
• The agent may be in the middle of a slow tool call (cloning a large repo, running a test suite). The bot polls every 2 seconds and will post as soon as the job finishes.
• The job may have failed — look for the error message, then open the ticket in the web UI for the full log.

Resuming after a restart

The ticket ↔ thread mapping is stored in the platform database. When the backend restarts, every active thread is rehydrated automatically — existing approval cards continue to work and keyword commands keep being recognised.

What you can't do from Slack

• Browse the ticket list or filter by status. Use the web UI for triage.
• Edit a phase document directly. Reply with feedback and let the agent revise it.
• Manage clankers, secrets, integrations, or claws. Those live in the web UI.

Tips

• Use threads for everything. Replying to the original thread keeps the ticket in context. Replying in the channel is ignored.
• One ticket per thread. Each /viberator invocation starts a fresh ticket. Don't reuse a thread for unrelated work.
• Use the web UI for long documents. Slack is ideal for quick keyword advances and approvals. The web UI is better for reading full research or planning documents before committing to execution.
• Punctuation doesn't matter. lgtm!, LGTM., and Lgtm all advance the phase. You don't need to type the keyword precisely.