weave / fleetInstall FleetReal Fleet mods. Seven draw on tool rows (build errors, git status, HTTP status, lint, file sizes, search hits); three, from Fleet 0.51.0, add context to a prompt, queue a follow-up and refuse a push; two, from 0.51.0, add a working button and a pane. Each comes with a prompt you can give an agent.
Every screenshot here is Fleet’s own conversation, running a real OpenCode session on a small invented project, with the real mod. Nothing is mocked up. In Fleet 0.50.0 a mod draws on a tool row: the row’s line, and the body you see when you open the row. The three mods under Beyond tool rows do more than draw: they add context to a prompt (or reword it), queue a follow-up and refuse an agent’s ask. Those hooks, working buttons and panes need Fleet 0.51.0 or later.
You don’t have to write any of these. Copy the prompt under a card into a session and the agent writes the mod as a draft that runs in that session only. You review it, and keep it if you like it. Each mod below is under 100 lines.
Test runs become passed, failed and skipped counts on the row; open it and the failing test names come first.
Ask an agent: Show test results as passed, failed and skipped counts on test rows, and list the failing tests when I open the row.
dotnet build, tsc, cargo build and go build rows get error and warning counts; open one for the first findings with file and line.
Ask an agent: Show build errors and warnings as counts on build rows, and list the first few with file and line when I open the row.
git status says how many files are staged, modified and untracked; git log --oneline says how many commits.
Ask an agent: Show git status as staged, modified and untracked counts on its row, and git log as a commit count.
curl -i and curl -sI rows show the status as a green, amber or red pill, with the size when the server sent Content-Length.
Ask an agent: Show the HTTP status of curl -i and curl -I as a coloured pill on the row, with the size if there is a Content-Length.
ESLint and ruff runs get error and warning counts; open the row and the problems are grouped by rule, most-hit first.
Ask an agent: Show ESLint and ruff results as error and warning counts, and group the problems by rule when I open the row.
File writes and patches get a +12 −3 pill. Fleet already counts edits, so this fills in the rows that had no count.
Ask an agent: Show how many lines a write or patch tool call added and removed as a pill on its row.
grep and glob rows say 14 matches in 5 files; open a grep row and the files with the most matches come first.
Ask an agent: Show how many matches and files a grep or glob found as a pill on its row, and list the files with the most matches when I open it.
When your prompt mentions branches, PRs, pushing or merging, the agent is told the session's git branch. Only the model gets the note; your bubble shows what you typed.
Ask an agent: When my prompt mentions branches, PRs, pushing or merging, tell the model which git branch the session is on. Don't change what I see in my message.
When a turn ends having changed files (and wasn't stopped or failed), Run the tests is queued and sent next. A turn that changed no files queues nothing, and a mod can queue 3 follow-ups in a row before Fleet waits for you.
Ask an agent: When a turn ends and the agent changed files, queue a message saying Run the tests. Don't do it if I stopped the turn or it failed.
The agent's git push is refused while the session is on main, with the reason Don't push from main. Make a branch and push that instead. You get no card; the agent is told why. Needs shell commands set to ask under Settings → Permissions.
Ask an agent: Refuse the agent's git push while the session is on main, and tell it to make a branch and push that instead.
A Count a press button in the opened body of a shell row, and how many times it has been pressed. Pressing it reaches the mod and the row draws again, with no page load.
Ask an agent: Add a Count a press button to the opened body of shell rows, and show how many times it has been pressed in this session.
A Release board tab next to Changes and Files, listed under From mods in the + menu. A shell row also gets an Open board button, and the tab has a Close button.
Ask an agent: Add a Release board pane to the + menu that lists three release steps with Done, Running and To do pills, with a Close button. Also add an Open board button to shell rows.
Fleet’s repository holds all twelve in mods/samples. From Fleet 0.52.0 they’re in the Showcase under Settings → Mods: choose Add beside one and it’s kept like any mod you keep. In 0.50.0 and 0.51.0 they’re links under the Mods switch in Settings → Features, Try the test-chips sample, Try build-summary and so on (0.50.0 has only test-chips). On 0.50.0 you can still ask an agent for the six tool-row mods with the prompts above; the prompt, turn and permission hooks, buttons and panes need 0.51.0.
These are designs, not screenshots of the app. Mods draw on tool rows, in panes, in a band above the composer and in a status-bar chip, and the prompt, turn and permission hooks and working buttons are above. These designs are not available yet:
$.ui.toast is accepted and shows nothing.
Design: the places a mod could draw on, numbered. Tool rows (1) work from 0.50.0 and panes (4) from 0.51.0; the band (2) and the chip (3) from 0.50.0 too.
Questions or something that doesn’t work? Open an issue in the Fleet repository.