-
Notifications
You must be signed in to change notification settings - Fork 339
Expand file tree
/
Copy pathtoolset-working-dir.yaml
More file actions
29 lines (26 loc) · 1.06 KB
/
toolset-working-dir.yaml
File metadata and controls
29 lines (26 loc) · 1.06 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
#!/usr/bin/env docker agent run
# Example: using working_dir for MCP and LSP toolsets
#
# Some language servers and MCP tools must be started from a specific directory.
# For example, gopls must be started from the Go module root. Use `working_dir`
# to configure the launch directory for any MCP or LSP toolset.
#
# `working_dir` is:
# - Optional (defaults to the agent's working directory when omitted)
# - Resolved relative to the agent's working directory if it is a relative path
agents:
root:
model: openai/gpt-5-mini
description: Example agent demonstrating working_dir for MCP and LSP toolsets
instruction: |
You are a helpful coding assistant with access to language server and MCP tools
launched from their respective project directories.
toolsets:
# LSP server started from a subdirectory (e.g. a Go module in ./backend)
- type: lsp
command: gopls
working_dir: ./backend
# MCP server started from a specific tools directory
- type: mcp
command: my-mcp-server
working_dir: ./tools/mcp