Gist
for LuumenAI
Keep runbook snippets and scratch notes in Gist, read and updated in place
Operations teams keep a lot in gists: one-off recovery scripts, parameter dumps, draft runbook steps. Luumen reads your gists, their revisions, and their comments while it works, so the snippet you wrote last quarter is available mid-incident. When something needs to change, it drafts the edit, shows you the file diff, and waits for your approval before writing.
The Gist toolbox
20 tools: 11 read, 9 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadCheck Gist StarCheck if the authenticated user has starred a specific gist.
- ReadGet GistRetrieve a specific gist by its ID.
- ReadGet Gist CommentGet a specific comment on a gist.
- ReadGet Gist RevisionRetrieve a specific gist revision.
- ReadList Gist CommentsList comments on a gist.
- ReadList Gist CommitsList the commit history of a gist.
- ReadList Gist ForksList forks of a gist.
- ReadList GistsList the authenticated user's gists or all public gists if called anonymously.
- ReadList Public GistsList public gists sorted by most recently updated.
- ReadList Starred GistsList the authenticated user's starred gists.
- ReadList User GistsList public gists for a specified GitHub user.
- WriteCreate GistCreate a new gist with one or more files. Approval by default
- WriteCreate Gist CommentCreate a comment on a gist. Approval by default
- WriteDelete GistDelete a gist. Approval by default
- WriteDelete Gist CommentDelete a comment on a gist. Approval by default
- WriteFork GistFork a gist. Approval by default
- WriteStar a GistStar a GitHub gist. Approval by default
- WriteUnstar a GistUnstar a GitHub gist. Approval by default
- WriteUpdate GistUpdate a gist's description and files. Approval by default
- WriteUpdate Gist CommentUpdate a Gist comment. Approval by default
One prompt, start to finish
What a governed Gist 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.
This connection exposes write actions such as create gist, create gist comment, delete gist, delete gist comment, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 Gist — 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 Gist to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.