Sideshow
for LuumenAI
Read Sideshow sessions and posts, then publish or update surfaces on approval
Connect Sideshow and Luumen can read your workspace the way a teammate would: which sessions exist, what was posted recently, the current surface content of a post and its retained versions, and the comment thread around it. When something needs to change, the agent drafts the post or update, shows you the surfaces it intends to write, and waits for your approval before publishing. Authentication is by API key.
The Sideshow toolbox
10 tools: 5 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet PostGet one post with current surface content and retained version history.
- ReadList CommentsList currently available comments, optionally filtered by session, post, author, or sequence number.
- ReadList KitsList the HTML style and behavior kits available to use in post surfaces.
- ReadList PostsList compact post summaries from one session, or the most recently updated posts across the workspace when session_id is omitted.
- ReadList SessionsList workspace sessions with their post and surface counts so a session can be selected for publishing or post filtering.
- WriteCreate CommentCreate a text comment attached to a post. Approval by default
- WriteDelete CommentPermanently delete one comment by id. Approval by default
- WriteDelete PostPermanently delete one post by id. Approval by default
- WritePublish PostPublish a post with one or more ordered typed surfaces, using an existing session or automatically creating one when session_id is omitted. Approval by default
- WriteUpdate PostUpdate a post title and/or the primary content of one surface while preserving that surface's kind and metadata; creates a retained version. Approval by default
One prompt, start to finish
What a governed Sideshow run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create comment, delete comment, delete post, publish post, and more — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Sideshow — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Sideshow to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.