Aiden for DevOps, Slack App, Workspace Chat, and GitHub Knowledge
The July 2026 v2026.7.11 Aiden release introduces Aiden for DevOps (MVP) so you can assign work from Linear or Jira and have Aiden triage it against your workflows and skills. It also brings early-access Slack app interaction (tag Aiden in channels), a workspace chat experience that is not limited to the SRE or DevOps app, and GitHub as a Knowledge Hub source (similar to Confluence).
Explore the sections below to see what's new in this update.
| Feature | Link | |
|---|---|---|
| What's New | DevOps | Aiden for DevOps |
| Integrations | Slack App Early Access | |
| Chat | Workspace Chat Outside Apps | |
| Knowledge Hub | GitHub Knowledge Hub Source |
What's New
Aiden for DevOps
Click to view
Aiden for DevOps is an MVP first release. Ticket-driven triggering works with Linear and Jira in this cut. Treat workflow matching, inbox triage, and related UX as early and validate in a non-production workspace before you rely on it for customer demos or production work. Contact support@stackgen.com or your Customer Service Manager for enablement and guidance.
We've added Aiden for DevOps so teams can assign infrastructure and platform work to Aiden from the tools they already use, then review, approve, and run those requests against trained workflows and skills.
Previously, DevOps-style agent work was harder to demo and consume in one place, and customer expectations for automated ticket-driven work were scattered. Now, Aiden can ingest tickets into a DevOps inbox, triage them against your workspace workflows, and wait for you to approve and execute the matching workflow.
Key Features
- Ticket-Driven Requests - Connect a tracker (this MVP: Linear or Jira), give Aiden an API key, choose the team, and define which tickets Aiden should pick up (for example tickets assigned to Aiden, with label filters).
- Inbox and Triage - New tickets appear in the DevOps inbox. Aiden tries to match each request to a workflow in the workspace (matching uses the workflow description; keep descriptions clear and distinct).
- Approve and Execute - Review the suggested workflow, approve it, and execute so Aiden fulfills the request with the skills and integrations you configured.
- Train with Workflows and Skills - Define how Aiden should accomplish work (for example provision or tear down a cloud resource, create compliant Terraform modules and open a PR, or run cloud-to-code style flows) using the same workflow and skill model you already use in Aiden.
Example flow (Linear)
- Connect Linear to the DevOps app with an API key and team selection.
- Create a ticket such as provisioning a storage account in a named resource group.
- Aiden ingests the ticket into the inbox and attempts workflow match.
- Approve and execute the workflow. Aiden completes the work and records fulfillment detail for follow-up.
Current Constraints
- MVP quality. Expect polish work on matching, enablement UX, and related surfaces.
- Triggering for DevOps ticket intake in this release is Linear and Jira only.
- Similar workflow descriptions can confuse triage. Prefer unique, specific descriptions.
Why It Matters
You can assign Aiden work inside existing Linear or Jira processes, see what the agent is doing in one UI, and reuse the same workflows and skills you train for demos and day-to-day automation.
Read more in Skills, Tasks, Jira, and StackGen integration.
Slack App Early Access
Click to view
The Slack app is early access. The enablement UX is still being polished and is not always obvious from the main Integrations page. Contact support@stackgen.com or your Customer Service Manager if you need help connecting Slack.
We've added an interactive Slack app so you can work with Aiden in Slack channels, not only send outbound notifications.
Previously, v2026.7.7 shipped outbound Slack notifications only, and called out that a fuller Slack application was still in progress. Now, you can add the Slack app to a workspace and tag Aiden in channels so it can investigate alerts and answer follow-up questions interactively.
Key Features
- Platform-Level Slack App - Slack is a workspace-level capability. It is not limited to the SRE app or the DevOps app alone.
- Cross-Signal Context - A workspace can combine infra-related and SRE-related integrations, so Slack conversations can draw on that combined context.
- One Workspace, Multiple Channels - You can connect the same Aiden Slack app to more than one channel in the same workspace.
- Tag Aiden - In a connected channel, tag Aiden on an alert or question to start an investigation or keep asking follow-ups in thread.
How to enable (current path)
Enablement is under workspace settings for admins (connected accounts), including Add to Slack. If the Integrations URL does not show the control you need, open workspace settings (admins may need the settings path rather than the Integrations path). Exact navigation is still being polished.
Current Constraints
- Early access. Setup UX needs improvement.
- Give Aiden a clear indication when you want a specific workflow from a channel conversation.
Why It Matters
Teams can bring Aiden into the Slack channels where alerts and ops discussion already happen, without waiting for a separate product surface.
Read more in Manage Workspaces.
Workspace Chat Outside Apps
Click to view
We've added a chat experience in Aiden that is not tied only to the SRE app or the DevOps app.
Previously, chat-style interaction was easy to treat as app-specific (for example only inside an SRE or DevOps flow). Now, you can chat with Aiden directly in the workspace about general questions, map the conversation to an existing Persona agent or workflow, or let Aiden choose how to handle the request.
Key Features
- Workspace Chat - Chat with Aiden outside a single specialized app context.
- Persona or Workflow Mapping - Point the chat at an existing Persona agent or workflow when you want a specific behavior.
- Help and General Questions - Use chat for product help and other questions that are not limited to one app.
Why It Matters
You get a single place to talk to Aiden for general work, while still routing to the agents and workflows you already trained when you need them.
Read more in Access Aiden and Functional Agents.
GitHub Knowledge Hub Source
Click to view
We've added GitHub as a Knowledge Hub source, in the same pattern as Confluence.
Previously, Knowledge Hub content commonly came from text, file upload, URL fetch, discovery, and sources such as Confluence. Now, you can connect GitHub, attach it to an agent, and let Aiden pull repository content as knowledge nodes so agents better understand your processes and workflows.
Key Features
- GitHub Knowledge Source - Connect GitHub from Knowledge Hub (GitHub icon / connect flow).
- Attach to an Agent - Bind the GitHub knowledge source to the agent that should use it.
- Repository Context as Nodes - Aiden pulls data from the connected repository so answers and workflows can use that process and workflow context.
Why It Matters
Teams that keep runbooks, standards, and process docs in GitHub can feed that context into Aiden the same way they already can with Confluence-backed knowledge.
Read more in Knowledge Hub and GitHub.