-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathconfig.yaml
More file actions
61 lines (55 loc) · 2.09 KB
/
Copy pathconfig.yaml
File metadata and controls
61 lines (55 loc) · 2.09 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
# Multi-Claude Orchestra — Session Configuration
# Copy this file and customize for your project.
orchestrator:
# Shared filesystem path (if available across hosts)
shared_fs: ""
# How often to run automatic sync (used by cron/loop)
sync_interval: 6h
# Tools to auto-approve when permission polling is enabled
auto_approve: [Read, Glob, Grep, "Bash:ls", "Bash:cat"]
# SSH ControlMaster socket directory
ssh_socket_dir: ~/.ssh/sockets
# Seconds between health check polls
poll_interval: 5
# Lines to capture from tmux pane for health checks
capture_lines: 50
# Session definitions
# Each session represents one Claude Code instance working on a project.
#
# Fields:
# host: user@hostname (omit for local sessions)
# path: project working directory on the target host
# tmux: tmux session name on the target host
# role: semantic role (pipeline, analysis, visualization, orchestrator, etc.)
# env: shell setup commands run before claude (optional)
# blocked_by: list of session names this depends on (optional)
# ssh_opts: extra SSH options like ProxyJump (optional)
# claude_args: extra arguments passed to claude command (optional)
sessions:
# --- Example sessions (replace with your own) ---
# example_remote:
# host: user@server
# path: /home/user/my-project
# tmux: claude_project
# role: pipeline
# env: "export PATH=$HOME/.local/bin:$PATH"
# claude_args: "--allowedTools Edit,Write,Bash"
# example_local:
# path: ~/my-local-project
# tmux: claude_local
# role: analysis
# example_viz:
# host: user@viz-server
# path: /home/user/visualization
# tmux: claude_viz
# role: visualization
# blocked_by: [example_remote]
# Dependency triggers
# Automatically brief a downstream session when an upstream event is detected.
#
# Fields:
# when: "<session> completes <pattern>" — pattern matched in tmux output
# then: "brief <session> <prompt>" — action to take
dependencies: []
# - when: "example_remote completes step 7"
# then: 'brief example_viz "Data ready at /share/output"'