Setting
One setting as a card, in a settings drawer or on a project’s card: a heading with its title and an optional helper line, then the setting itself, such as a project’s Objective, its Instructions or its Check-ins. Drawn on the same card as every other block, but it doesn’t fold, and its heading has no icon, caret or count.
A setting is a field people fill in, not a view of a record, so it has no version in chat.
Installation
import { Setting } from "@o/pipeline/experimental/blocks/setting";
Usage
What done looks like. The instructions below say how to get there.
Pass the setting as children. A text setting is an Editor, borderless and growing with its text, set in the body’s own type: the text is always the field, with nothing to click into first. The block owns no state; the app reads the editor’s changes and saves them.
title names the setting in the title type every block shares. description is the helper line under it: the same gray, one size down, at the regular weight.
Instructions
Instructions take Markdown, so their editor uses the markdown preset: lists, bold and links read as themselves.
What the agent should watch for, how it should judge signals, and when it should speak up.
Empty
With no text yet, the editor’s placeholder stands in its place, such as “What does done look like?”.
What done looks like. The instructions below say how to get there.
Saved note
headerEnd sits at the heading’s end, on the title’s line: a setting that saves as you type says “Saved” there once it has.
What done looks like. The instructions below say how to get there.
Long title
A title too long for its line wraps. It stops short of the note, which keeps its place at the end of the first line. The helper line under it keeps the card’s full width.
What done looks like. The instructions below say how to get there.
Without description
The helper line shows only where the title isn’t enough; leave out description and the heading is the title alone.
Control
A text body sits 12px in from the card, as the heading does. A control, such as a full-width ToggleGroup, sits 6px in with inset="control", closer to the card’s edge.
The agent posts daily summaries here: what's stuck, what's gone quiet, and what it would do next.
Connect a source
Values people copy, such as a webhook’s endpoint and body, stack 20px apart. Each has its label in small gray type with a copy IconButton at its end, then the value in monospace below.
Send signals from other tools into this project with a webhook.
https://api.example.com/v1/workstreams/ws_123/signals
{
"type": "zapier.form.submitted",
"payload": {
"email": "someone@example.com"
}
}Loading
Inside a loading SkeletonGroup with no body, placeholder lines stand where the setting will be, until it replaces them.
What done looks like. The instructions below say how to get there.
A line or two of the setting, set as text while it loads.