# Bringing Neo to GitHub and Slack

DevFeed: [Bringing Neo to GitHub and Slack](<https://devfeed.tech/articles/bringing-neo-to-github-and-slack-19015.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/neo-github-slack/>)

Author: Pulumi Neo Team

Published: 2026-05-21T15:00:00Z

Content type: release

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [pulumi-neo](<https://devfeed.tech/topics/pulumi-neo.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [features](<https://devfeed.tech/tags/features.md>), [github](<https://devfeed.tech/tags/github.md>), [product](<https://devfeed.tech/tags/product.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [pulumi-cloud](<https://devfeed.tech/tags/pulumi-cloud.md>), [pulumi-neo](<https://devfeed.tech/tags/pulumi-neo.md>), [slack](<https://devfeed.tech/tags/slack.md>)

## AI overview

Pulumi Neo is now available in GitHub and Slack, extending its existing Pulumi Cloud console and terminal capabilities into team discussion threads. Users can ask Neo to inspect stack state, explain changes, investigate failures, and perform approved actions, with responses and follow-up work recorded in the relevant thread.

## Source excerpt

This week, Pulumi Neo started working in two more places: GitHub and Slack. The agent that already runs Pulumi tasks from the Cloud console and the terminal now participates in the threads where your team discusses changes. Mention @pulumi-neo in a pull request or issue and Neo replies in the thread. Mention @Neo in a Slack channel and Neo starts a task, continuing the conversation as you reply. Neo in GitHub Mention @pulumi-neo in a pull request description, a top-level or inline review comment, or an issue. Neo sees the diff, the stacks linked to the repository, and their current state. Reviewers can ask Neo to walk through what a proposed change does, including resources that change in stacks the PR doesn't touch directly. Responses land in the same thread, so the analysis becomes part of the review record and any follow-up stays with it. Neo in Slack Mention @Neo in any channel where Neo has been added, and Neo starts a task in the thread. The reply lands in the same thread, and follow-up messages continue the conversation there. The rest of the channel can see what was asked and what Neo found. Neo has the same capabilities here as in the Pulumi Cloud console or the terminal: check stack state, investigate failures, walk through what a change will do, or carry out actions the team has approved. Integrations in action A teammate posts in #platform-engineering: "API latency p95 has been climbing for two days, nobody can figure out why." You reply: You: @Neo check the production API stack. Anything change in the last 72 hours? Neo starts a task in the thread, walks the stack history, and finds a configuration change to the load balancer's idle-timeout setting that landed Friday afternoon. It posts the change, who deployed it, and when. The rest of the channel sees the finding without you having to retell it. You: @Neo open a PR to revert idle-timeout to the previous value. Neo edits the stack's Pulumi program, runs pulumi preview to confirm the change touches only