mirror of
https://github.com/fabro-sh/fabro.git
synced 2026-08-28 05:27:41 +00:00
359306569a
Roadmap: replace placeholder items with current shipped/building/planned features. Use real dates for sorting instead of manual sortOrder. Fix UTC timezone rendering for date display. Terminology: replace all standalone "DOT" references with "Graphviz" or "Graphviz DOT" across docs, marketing, README, AGENTS.md, and OpenAPI spec. Changelogs left unchanged as historical records. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
76 lines
2.4 KiB
Text
76 lines
2.4 KiB
Text
---
|
|
title: "Variables"
|
|
description: "Using variables in workflows"
|
|
---
|
|
|
|
Fabro supports `$variable` placeholders that let you parameterize workflows without editing the Graphviz 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.fabro"
|
|
|
|
[vars]
|
|
repo_name = "fabro"
|
|
repo_url = "https://github.com/fabro-sh/fabro"
|
|
language = "rust"
|
|
```
|
|
|
|
These variables are expanded into the Graphviz source **before** the graph is parsed. You can use `$variable` anywhere in the Graphviz file — goals, prompts, labels, scripts, or any other attribute:
|
|
|
|
```dot title="check.fabro"
|
|
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 `fabro run run.toml`, Fabro replaces `$repo_name`, `$repo_url`, and `$language` with their values before parsing the graph.
|
|
|
|
### Undefined variables
|
|
|
|
If a `$variable` in the Graphviz file has no matching entry in `[vars]`, Fabro 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, Fabro automatically expands `$goal` to the workflow's `goal` attribute. This happens at runtime, after graph parsing:
|
|
|
|
```dot title="example.fabro"
|
|
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 |
|