mirror of
https://github.com/fabro-sh/fabro.git
synced 2026-08-28 05:27:41 +00:00
d002aa0b51
* arc(01KK7524KNGTPS4090QMF87FJN): implement (success) Arc-Run: 01KK7524KNGTPS4090QMF87FJN Arc-Completed: 2 Arc-Checkpoint: 1ff03c704805dfe8e7c37b37f97bd06dfa0e5dc5 * Fix: restore trailing newlines stripped by previous commit * arc(01KK7524KNGTPS4090QMF87FJN): simplify (success) Arc-Run: 01KK7524KNGTPS4090QMF87FJN Arc-Completed: 3 Arc-Checkpoint: 21771adfd26283a1d1e6b8a123a83a0c4277db48 --------- Co-authored-by: arc <arc@local> Co-authored-by: Arc Assistant <assistant@arc.dev> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
76 lines
2.4 KiB
Text
76 lines
2.4 KiB
Text
---
|
|
title: "Variables"
|
|
description: "Using variables in workflows"
|
|
---
|
|
|
|
Arc supports `$variable` placeholders that let you parameterize workflows without editing the DOT file.
|
|
|
|
## Run config variables
|
|
|
|
Define variables in the `[vars]` section of a run config TOML file:
|
|
|
|
```toml title="run.toml"
|
|
version = 1
|
|
goal = "Run tests for $repo_name"
|
|
graph = "check.dot"
|
|
|
|
[vars]
|
|
repo_name = "arc"
|
|
repo_url = "https://github.com/qltysh/arc"
|
|
language = "rust"
|
|
```
|
|
|
|
These variables are expanded into the DOT source **before** the graph is parsed. You can use `$variable` anywhere in the DOT file — goals, prompts, labels, scripts, or any other attribute:
|
|
|
|
```dot title="check.dot"
|
|
digraph Check {
|
|
graph [goal="Run tests for $repo_name"]
|
|
|
|
start [shape=Mdiamond, label="Start"]
|
|
exit [shape=Msquare, label="Exit"]
|
|
|
|
clone [label="Clone", shape=parallelogram, script="git clone $repo_url repo"]
|
|
test [label="Test", prompt="Run the $language test suite in the repo/ directory."]
|
|
|
|
start -> clone -> test -> exit
|
|
}
|
|
```
|
|
|
|
When launched with `arc run run.toml`, Arc replaces `$repo_name`, `$repo_url`, and `$language` with their values before parsing the graph.
|
|
|
|
### Undefined variables
|
|
|
|
If a `$variable` in the DOT file has no matching entry in `[vars]`, Arc raises an error. This catches typos early — a misspelled `$langauge` fails immediately rather than passing a literal `$langauge` to the LLM.
|
|
|
|
### Escaping `$`
|
|
|
|
To include a literal `$` in the output, write `$$`:
|
|
|
|
```dot
|
|
test [prompt="The env var is $$HOME"]
|
|
```
|
|
|
|
This produces `The env var is $HOME` without treating `$HOME` as a variable reference. A bare `$` not followed by an identifier character (e.g. `costs $5`) does not need escaping.
|
|
|
|
## The `$goal` variable
|
|
|
|
Inside agent and prompt node prompts, Arc automatically expands `$goal` to the workflow's `goal` attribute. This happens at runtime, after graph parsing:
|
|
|
|
```dot title="example.dot"
|
|
digraph Example {
|
|
graph [goal="Implement the login feature"]
|
|
|
|
plan [label="Plan", prompt="Create a plan for: $goal"]
|
|
}
|
|
```
|
|
|
|
The plan node's prompt becomes `"Create a plan for: Implement the login feature"`.
|
|
|
|
## Variable merging
|
|
|
|
When using server-level run defaults alongside a run config TOML, variables are merged. Task config vars override default vars when keys collide:
|
|
|
|
| Source | Priority |
|
|
|---|---|
|
|
| Run config TOML `[vars]` | Highest — wins on collision |
|
|
| Server defaults `[vars]` | Lowest — provides fallback values |
|