You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: "How agents can operate in different modes"
4
+
---
5
+
6
+
Agents can provide a set of modes they can operate in. Modes often affect the system prompts used, the availability of tools, and whether they request permission before running.
7
+
8
+
## Initial state
9
+
10
+
During [Session Setup](./session-setup) the Agent **MAY** return a list of modes it can operate in and the currently active mode:
11
+
12
+
```json
13
+
{
14
+
"jsonrpc": "2.0",
15
+
"id": 1,
16
+
"result": {
17
+
"sessionId": "sess_abc123def456",
18
+
"modes": {
19
+
"currentModeId": "ask",
20
+
"availableModes": [
21
+
{
22
+
"id": "ask",
23
+
"name": "Ask",
24
+
"description": "Request permission before making any changes"
25
+
},
26
+
{
27
+
"id": "architect",
28
+
"name": "Architect",
29
+
"description": "Design and plan software systems without implementation"
30
+
},
31
+
{
32
+
"id": "code",
33
+
"name": "Code",
34
+
"description": "Write and modify code with full tool access"
Optional description providing more details about what this mode does
68
+
</ResponseField>
69
+
70
+
## Setting the current mode
71
+
72
+
The current mode can be changed at any point during a session, whether the Agent is idle or generating a response.
73
+
74
+
### From the Client
75
+
76
+
Typically, Clients display the available modes to the user and allow them to change the current one, which they can do by calling the [`session/set_mode`](./schema#session%2Fset-mode) method.
The ID of the mode to switch to. Must be one of the modes listed in `availableModes`
96
+
</ParamField>
97
+
98
+
### From the Agent
99
+
100
+
The Agent can also change its own mode and let the Client know by sending the `current_mode_update` session notification:
101
+
102
+
```json
103
+
{
104
+
"jsonrpc": "2.0",
105
+
"method": "session/update",
106
+
"params": {
107
+
"sessionId": "sess_abc123def456",
108
+
"update": {
109
+
"sessionUpdate": "current_mode_update",
110
+
"modeId": "code"
111
+
}
112
+
}
113
+
}
114
+
```
115
+
116
+
#### Exiting plan modes
117
+
118
+
A common case where an Agent might switch modes is from within a special "exit mode" tool that can be provided to the language model during plan/architect modes. The language model can call this tool when it determines it's ready to start implementing a solution.
119
+
120
+
This "switch mode" tool will usually request permission before running, which it can do just like any other tool:
121
+
122
+
```json
123
+
{
124
+
"jsonrpc": "2.0",
125
+
"id": 3,
126
+
"method": "session/request_permission",
127
+
"params": {
128
+
"sessionId": "sess_abc123def456",
129
+
"toolCall": {
130
+
"toolCallId": "call_switch_mode_001",
131
+
"title": "Ready for implementation",
132
+
"kind": "switch_mode",
133
+
"status": "pending",
134
+
"content": [
135
+
{
136
+
"type": "text",
137
+
"text": "## Implementation Plan..."
138
+
}
139
+
]
140
+
},
141
+
"options": [
142
+
{
143
+
"optionId": "code",
144
+
"name": "Yes, and auto-accept all actions",
145
+
"kind": "allow_always"
146
+
},
147
+
{
148
+
"optionId": "ask",
149
+
"name": "Yes, and manually accept actions",
150
+
"kind": "allow_once"
151
+
},
152
+
{
153
+
"optionId": "reject",
154
+
"name": "No, stay in architect mode",
155
+
"kind": "reject_once"
156
+
}
157
+
]
158
+
}
159
+
}
160
+
```
161
+
162
+
When an option is chosen, the tool runs, setting the mode and sending the `current_mode_update` notification mentioned above.
0 commit comments