Erik is the founder of Cloud Posse and creator of Atmos. With over a decade of experience helping teams adopt Terraform at scale, he is passionate about open-source infrastructure tooling and developer experience.
Atmos Pro joins Slack's agent picker, putting infrastructure answers a click away. Open Atmos Pro from the picker or the app's Messages tab to start a private conversation. Suggested prompts help you check drift, investigate deployment failures, or manage your notifications.
Direct messages now support infrastructure questions alongside personal settings. Ask why a deployment failed, follow up with questions about its logs, or request a PDF or Markdown report. Your conversation history stays private to your linked account. You can still mention @Atmos Pro in a channel to investigate with your team.
As the agent works, an expandable progress card shows actual steps such as checking infrastructure or reading workflow logs. Steps update as they finish, and the card stays above the answer in the same reply. You can see which steps completed and which were unavailable without a stream of separate status messages. Atmos Pro also displays Slack's green online indicator so it is easy to spot.
Atmos ProAGENTPrivate conversation
RH
richard9:41 AM
Why did the last staging VPC deployment fail?
Atmos ProAGENT9:41 AM
Check deployments and workflow runs
Read execution output and workflow logs
Read repository information
The plan could not acquire the state lock
vpc · plat-use2-staging
The plan job stopped before apply. Check whether the lock-owning workflow is still running before deciding how to retry.
Plain text
Error: Error acquiring the state lock
Operation: OperationTypePlan
Path: staging/vpc/terraform.tfstate
No apply job ran in this deployment. I can inspect the workflow history next.
Illustrative conversation
Follow the investigation in one expandable progress card.
The agent uses your linked Atmos Pro permissions. Infrastructure questions support investigation; applying or approving infrastructure changes remains in Atmos Pro. Private conversations use the same AI plan requirements and workspace credit balance as channel chat.
Answers can include compact summary cards with resource icons and sortable, paginated tables for comparing instances or deployments. Native code blocks keep short Terraform output and configuration excerpts readable, with language-specific highlighting where supported. Table links come from the resources the agent reads, so you can open the supporting details. A plain-text version keeps the answer available in notifications and conversation history.
For an existing installation, a workspace owner or admin selects Reauthorize in Workspace Settings → Integrations → Slack and approves the added agent permission for the same Slack workspace. Then refresh Slack and link your personal account from the app's Home tab if needed. Slack administrators may need to enable the agent experience.
|
Atmos Pro