Skip to main content

Key Concepts

An organization has projects. A project holds an agent's files in Git, its tools, its triggers, its runs and the people who can change it.

Organization
People
Users, groups, SSO and organization settings
Projects
One for each team, with its own members and roles
in each project
Who starts a run
A person
Web app, Assistant or CLI
A trigger
An event, a schedule or a set time
starts
Project
Git repository
Agents and skills, one commit for each change
agents/pr-review/agent.yamlskills/review-rules/SKILL.md
Integration Connections
Tools, and the sign-in for CLIs in the sandbox
GitHubSlackCustom MCP
the agent and its tools
Run
Transcript, result and artifacts

A run reads the agent's files from the project's Git repository. It gets its tools from the project's Integration Connections. A person or a trigger starts it. A second team gets its own project, and it can import an Integration Connection that another project shares.

Where things are in the app​

The column at the left edge of the app has four zones, the Assistant and the settings. All of them show the project that you select in the project picker.

TileZoneWhat you do thereWhat it has
WorkWorkRun agents and see what they foundMy work, Runs, Artifacts, Alerts
AgentsAgent StudioBuild, test and change agentsThe branch button, Agents, Skills, Templates, Editor, Triggers
ContextContext GraphDescribe your systems, and review what agents learnedGraph, Memories, and the setup pages Sources, Blueprints and Labels
InsightsInsightsSee how your agents are doingRuns, estimated spend and token use
AssistantAsk Autoheal to build, run or explain somethingA panel that opens on every page
SettingsSet up the projectIntegrations, tools, agent policies, secrets and access

The words used in these docs​

WordWhat it isWhere you find it
OrganizationYour company's Autoheal account: users, groups, SSO and org settingsOrg settings
ProjectA team's workspace. It has its own Git repository, Integration Connections, triggers and members. Every organization starts with a Default Project.The project picker, at the top left
AgentA folder agents/<id>/ with an agent.yaml file: instructions, model, tools and skillsAgent Studio → Agents
SkillA folder skills/<id>/ with a SKILL.md file: know-how that an agent loads when it needs itAgent Studio → Skills
Integration ConnectionOne connected system, such as a GitHub organization or a Grafana instanceSettings → Integrations
ToolOne action that an agent can do. System tools come with Autoheal. Integration tools come from Integration Connections.The run transcript
TriggerA rule: when this event occurs, run this agent with this promptAgent Studio → Triggers
RunOne execution of an agent, with its transcript and resultRuns
ArtifactA file that a run makes, such as a reportArtifacts
BranchA separate line of changes in the project's repository. Use it to try a change before other people use it.The branch button at the top of the Agent Studio sidebar

Where an agent's behavior comes from​

The agent's...Comes fromChange it in
Job and rulesinstructions in agent.yaml, or a Markdown file it namesThe editor, or autoheal agents push
Modelmodel in agent.yaml. If you leave it out, the organization's default model.agent.yaml
Know-howSkills in the project, or skills in the agent's own folderskills/<id>/SKILL.md
ToolsSystem tools and the tools of the project's Integration Connections, limited by the system_tools and integration_tools filters. The shell, with CLIs such as gh signed in for the project's connections, is always available and filters do not limit it.agent.yaml, and Settings → Integrations
StartA person (web app, Assistant or CLI) or a triggerAgent Studio → Triggers

If you used Autoheal before​

Incident response is now an agent, Incident Response, that you can read, run and change like every other agent. The steps you followed before are now its instructions and skills.

Next steps​