Agents overview

Agents are reusable AI automations that you configure with natural language instructions. No code, no workflow builders, no drag-and-drop — just plain English describing what you want done.

How agents work

Each agent has three components:

1. Triggers: When and where the agent should run
   • Scheduled: Run on a recurring schedule (daily, weekly, custom cron)
   • Channels: Where the agent listens for mentions (Slack channels, GitHub repos, Linear teams)
2. Prompt: Regular text instructions describing what the agent should do
3. App restrictions: Control what each agent can access and modify — set default access levels, per-system overrides, and per-resource permissions to follow the principle of least privilege

When triggered, the agent runs in its own canvas, executing the instructions with full access to Stilla's tools and integrations.

Agent runs

Every execution creates a separate canvas — an "agent run" — where you can see exactly what the agent did, what tools it used, and what changes it proposed. This gives you full transparency into automated actions.

Agent runs are stored and searchable, so you can review past executions, debug issues, or audit what happened.

Agent memory

Agents can persist information across runs using a memory canvas. This lets agents track trends, remember decisions, and build up context incrementally rather than starting from scratch each time.

Channel triggers

By assigning an agent to specific channels, you can customize how Stilla responds when mentioned in different contexts. Each channel can have its own agent, so Stilla behaves differently depending on where it's mentioned.

For example:

• An agent for your #support Slack channel that follows specific triage steps
• An agent for GitHub PRs that runs your team's review checklist
• An agent for Linear that categorizes and routes new issues

Use cases

• Weekly standup summaries: Aggregate updates from Linear, GitHub, and Slack into a weekly digest
• Changelog generation: Generate release notes from merged PRs
• Customer feedback triage: Route and categorize incoming feedback
• Incident response: Pull context from PagerDuty, Slack, and logs when incidents fire
• Dependency scanning: Check for outdated or vulnerable dependencies on a schedule
• Meeting prep: Before a recurring meeting, gather relevant updates from all connected tools