Runs with brush chart
A week of runs, with the moment that matters in focus.
Definition · Updated Nov 2, 2026
A runs with brush chart shows run counts and success rate over a week, with a brush outline on today and markers for deploys and incidents. You see the day against the whole week on one card. Use it for agent runs, jobs and pipelines.
Pay once. Every update included.
Live preview
Sample data: agent runs and success rate, Oct 10 to Oct 16, 96.2% today, one deploy and one incident marked
- Data shape
- Runs and success rate per hour, events
- Good for
- Agent runs, jobs, pipelines
- Avoid when
- There are no events to explain changes
- Sizes
- XS, S, M and L, re-laid out from the data
Anatomy
Inspect it like the Figma file.
The same layers, names and tokens as the component. Select one to read its size, fill and style.
Layers
104 / Runs with brush
- Layer
- last week
- Type
- Vector
- Size
- 668 × 35
- Stroke
- text/unselected
- Group
- Marks · 178
Layers
104 / Runs with brush
- Layer
- last week
- Type
- Vector
- Size
- 415 × 18
- Stroke
- text/unselected
- Group
- Marks · 94
Layers
104 / Runs with brush
- Layer
- brush · runs
- Type
- Vector
- Size
- 275 × 12
- Fill
- text/unselected
- Group
- Marks · 66
Sizes
Re-laid out, never scaled.
The same data at XS, S, M and L. Every size is redrawn from the data, so text and line weights never shrink.
M against S
Width360 px480 px
Plot328 px440 px
Labels79
Marks6694
Height212 px246 px
Same tokens at every size: text styles, 1 px lines and mark radius stay put.
When to use
Overview and detail.
Three signs it fits, and three signs another type fits better.
Do events explain the changes?
Just the trend.
Yes: Keep the runs with brush
Is a week the right range?
A few hours against a target.
Yes: Keep the runs with brush
Code and Figma
One name in Figma and in code.
Every Figma property is a prop with the same name and values. One command installs it.
Figma
chart/104-runs-with-brush
npx shadcn add @chartory/runs-with-brushimport { RunsWithBrush } from "@/components/chartory/runs-with-brush"import { agentRuns } from "./agent-runs"export function AgentRuns() { return ( <RunsWithBrush data={agentRuns} size="m" legend={true} /> )}Hearth widget
Runs with brush as a widget.
The chart in a Hearth card with a hero number and two blocks. One token set, light and dark.
EmberPreset
ChartoryDefault preset
Pick the blocks, the size and the preset for your own widget.
Read the Hearth widget docsFAQ
Runs with brush questions.
What people ask before they put a runs with brush in a dashboard.
Something else?
hello@usechartory.comAny dated event you pass, drawn as a labelled pin (DEPLOY #2041, INCIDENT in the sample). Keep it to a few per range so the pins stay readable.
Today's stretch of the week. The day's success rate (96.2 % in the sample) reads against the rest of the week, which stays in view.
One data object in the sample’s shape: runs and success rate per hour, events. The docs page lists every field and links its JSON Schema; the sample data comes with the component, so you can start from it and swap in your own.
Series take the preset’s data colours in order, and states such as up, down or warning take its status colours. Change the preset in Figma or in code to recolour every chart at once.
XS, S, M and L, in light and dark. Each size is laid out again from the data, so text and lines keep their size.
Yes. It plays in when it scrolls into view, and when the data changes every mark moves from its old place to its new one. With reduced motion on, it does not move.
Yes. The Figma component comes with Figma and Complete, the React component with Code and Complete.
Ask for it by name. The MCP server tells the agent what data it needs and runs the same command: npx shadcn add @chartory/runs-with-brush. You review the diff.
Related types
Other ways to show change over time.
The same question, a different shape of answer. Every type ships in Figma and in code.
Same family
Change over time
Trends, levels and seasons across days, months or years.