-
Notifications
You must be signed in to change notification settings - Fork 5
Expand file tree
/
Copy pathampere.example.yaml
More file actions
132 lines (122 loc) · 4.32 KB
/
ampere.example.yaml
File metadata and controls
132 lines (122 loc) · 4.32 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
# Ampere Team Configuration
# ==========================
# Copy this file to ampere.yaml and customize for your project.
#
# The CLI will automatically load configuration from:
# - ampere.yaml (current directory)
# - ampere.yml (current directory)
# - .ampere/config.yaml
# - .ampere/config.yml
#
# Or specify explicitly: ampere --config path/to/config.yaml
# AI Provider Configuration
# -------------------------
# Choose your AI provider and model. Backups will only be used if the preferred provider fails.
ai:
provider: anthropic # Options: anthropic, openai, gemini
model: sonnet-4 # See the model list below
# Optional: Fallback providers (tried in order if primary fails)
backups:
- provider: openai
model: gpt-4.1
- provider: gemini
model: flash-2.5
# Available Models:
# -----------------
# Anthropic (Claude):
# opus-4.5, opus-4.1, opus-4
# sonnet-4.5, sonnet-4, sonnet-3.7
# haiku-4.5, haiku-3.5, haiku-3
#
# OpenAI (GPT):
# gpt-5.1, gpt-5.1-instant, gpt-5.1-codex-max
# gpt-5, gpt-5-mini, gpt-5-nano
# gpt-4.1, gpt-4.1-mini
# gpt-4o, gpt-4o-mini
# o4-mini, o3, o3-mini
#
# Google (Gemini):
# pro-3, pro-2.5
# flash-2.5, flash-2.5-lite
# flash-2, flash-2-lite
# Team Composition
# ----------------
# Define the agents that will work together on your goals.
# Each agent has a role and optional personality traits.
team:
# Product Manager: Coordinates work, breaks down tasks, makes decisions
- role: product-manager
personality:
directness: 0.8 # 0=diplomatic, 1=very direct
thoroughness: 0.7 # 0=concise, 1=thorough
formality: 0.6 # 0=casual, 1=formal
# Engineer: Writes production-quality code
- role: engineer
personality:
creativity: 0.7 # 0=conventional, 1=creative
risk-tolerance: 0.4 # 0=conservative, 1=risk-taking
thoroughness: 0.8
# QA Tester: Tests code and finds edge cases
- role: qa-tester
# Uses default personality
# Available Roles:
# ----------------
# - product-manager: Coordinates work and makes product decisions
# - engineer: Writes production-quality code
# - qa-tester: Tests code and finds bugs
# - architect: Designs system architecture and APIs
# - security-reviewer: Reviews code for security issues
# - technical-writer: Creates documentation
# Personality Traits:
# -------------------
# All values range from 0.0 to 1.0
# - directness: How direct vs diplomatic (0=diplomatic, 1=very direct)
# - creativity: How creative vs conventional (0=conventional, 1=creative)
# - thoroughness: How thorough vs concise (0=concise, 1=thorough)
# - formality: How formal vs casual (0=casual, 1=formal)
# - risk-tolerance: How risk-tolerant vs conservative (0=conservative, 1=risk-taking)
# MCP Servers (optional)
# ----------------------
# Connect to external MCP (Model Context Protocol) servers to give agents
# access to tools like GitHub, databases, code analysis, etc.
#
# Each server exposes tools that agents can discover and invoke dynamically.
# Tools inherit the server's autonomy level for access control.
#
# mcp:
# servers:
# # Local MCP server via stdio (spawns a child process)
# - id: github
# name: GitHub CLI
# protocol: stdio
# endpoint: /usr/local/bin/github-mcp-server
# autonomy: act-with-notification
#
# # Remote MCP server via HTTP
# - id: database
# name: Database Query Service
# protocol: http
# endpoint: https://db-mcp.example.com/api
# auth-token: your-secret-token
# autonomy: ask-before-action
# timeout-ms: 60000
#
# # Streaming MCP server via SSE
# - id: code-analysis
# name: Code Analysis
# protocol: sse
# endpoint: https://analysis.example.com/mcp
# autonomy: fully-autonomous
# auto-reconnect: true
#
# Supported protocols: stdio, http, sse
# Supported autonomy levels:
# - ask-before-action: Agent proposes, waits for human approval
# - act-with-notification: Agent acts immediately, notifies human
# - fully-autonomous: Agent acts independently, logs for audit
# - self-correcting: Agent acts, self-reviews, and iterates
# Initial Goal (optional)
# -----------------------
# Set a default goal for the team. Can also be passed via CLI:
# ampere --goal "Build a user authentication system"
goal: "Build a user authentication system"