Examples · Bug fix
A missing nav link, fixed for $3.05
Added the missing nav link, so a Skills workspace a group inherits is reachable from that group's own Set up section.
- $3.05
- Cost, start to finish
- 20m
- Lead time, filed to merged
- 2
- Files changed in the merge
Measured from this task's real merge.
- Cost
- $3.05
- Turns
- 106
- Lead time
- 20m
- Merged
- Aug 7, 2026
- Diff
- 2 files · +16 -2
A group workspace can own Skills the same way it owns Agents and Devices, and every workspace under it inherits them. Its Set up section linked to Agents and Devices, but not to Skills, so a group had no way in to a resource it already had.
What was asked for
Missing skills link in Set Up section on Group
Filed from the web app, no CLI or git required (react).
What the herd did
- plan
- code
- review
- merge
- verify
- done
- plan
- Confirmed Skills is a group-level, inherit-down resource with the same authorization shape as the two links already sitting in that section, so the fix was one nav entry, not a redesign.
- code
- Added the Skills link to GroupNav's Set up section, next to Agents and Devices, and updated the comment that documents the nav's current shape.
- review
- Checked the new link against the group-authorization tests Agents and Devices already had to pass.
- merge
- Opened the request against main and it merged the same day.
- verify
- Confirmed a group's Set up section now lists Skills alongside Agents and Devices.
- done
- Filed to merged in twenty minutes, for $3.05.
What it changed
The merge touched 2 files (+16 −2). Among them:
app/src/router/AppLayout.tsxapp/src/router/AppLayout.group.test.tsx
What it cost
$3.05 in model spend, 106 agent turns, and 20m from filed to merged. See what a month of work like this would cost your own team on our cost calculator.
A missing menu link is a real bug even when the underlying feature already works.
Got something like this to ship?
Tell us what you're building. We'll set your workspace up and you can file it today.