Repository navigation
Vibe Coding Hub v1.1.0
Vibe Coding Hub v1.1.0
This release adds characters with their own skills and team flows: characters working together on a task, drawn on a canvas and run in parallel where the work allows.
Highlights
- Skills registry. Write skills as plain markdown files, then add, edit and delete them from the app or the CLI.
- Characters with unique skillsets. Give each character exactly the skills it needs. One developer can know clean architecture and C#, another ML and Python.
- Team flows. Connect characters with arrows into a flow. A character starts when the characters pointing into it are done, and independent characters run in parallel.
- Flows panel. Draw, validate and run flows in the desktop app, with live status for every step.
Skills and characters
Skills registry
- A skill is a markdown file with YAML frontmatter:
<dir>/<name>/SKILL.md. - Skills live in
~/.aiagent/skills(global) or.aiagent/skills(per project). A project skill overrides a global one with the same name. - Renaming or deleting a skill updates the characters that use it, and the doctor reports dangling references.
- Agents load skills on demand with the
use_skilltool. A character can only use the skills it has. - Pinned skills are always included in the character's context.
Characters
- A character is a markdown file in
characters/<id>.md, global or per project, with a persona and a list of skills. - Add skill button in the character profile: pick a skill from the library or create a new one on the spot.
- Templates: a character can extend a template (
extends) and add or remove skills (remove-skills), so a "software developer" base can become a C# architect or an ML engineer. spawn_subagentcan start a sub-agent as a specific character.- CLI:
aiagent characters add-skilland the other skill and character commands.
Note: the earlier "skill sets" idea was dropped in favor of per-character skills. An old skillsets: field in a character file is ignored and produces a warning.
Team flows
What a flow is
A flow is a pipeline whose stages are characters connected by arrows.
design (Alex) ──► backend (Dana) ──┐
└─► model (Mia) ─────┴─► review (Quinn) ──approved──► release notes (Sam)
▲ │
└──── rejected, ≤2× ──┘
- Parallel by default. Steps whose inputs are ready run at the same time, each in its own git worktree. The limit is
maxParallel(default 3). - Handoff. A step receives the task plus the final answers of the steps connected into it.
- Conditions. A step can declare outcomes such as
approvedorrejected. Arrows can follow a specific outcome. - Loops. An arrow back to an earlier step re-runs it with the feedback, up to a limit. When the limit is reached, a
loop-exhaustedarrow can route elsewhere. A cap of 25 step runs per flow prevents runaway runs. - Failures only skip the steps that depend on the failed one. Other branches finish.
- Confirmation prompts and cancellation work per step.
- Flows are stored in
pipelines/*.json. The new fields are optional, so existing pipelines, includingfull-sdlcandquick-fix, behave as before.
Flows panel (desktop)
Open it with the 🔀 button or from the command palette ("Flows", "New Flow").
- Draw: drag characters from the palette, move steps, drag from a step's right handle to connect. Zoom, pan, undo and redo are supported.
- Edit: set each step's character, prompt, outcomes, confirmation and on/off state, and each arrow's condition and loop limit.
- Check: problems are outlined in red with a list below, and the header shows which steps run in parallel.
- Auto-layout arranges steps by execution order.
- Run: each step shows waiting, running, done, failed or skipped. Arrows light up when taken. Click a step to see its live output and answer approvals on the step. Stop cancels the run.
CLI
aiagent pipeline runshows per-step progress and accepts--max-paralleland--cast.aiagent pipeline validate <name>lists problems and exits with code 1 on errors.aiagent pipeline show <name> [--mermaid]lists the execution waves and loops, or exports a Mermaid diagram.
Examples
examples/pipelines/feature-team.json: Alex designs, Dana (backend) and Mia (model) work in parallel, Quinn reviews and loops on rejection, Sam writes the release notes.- The README has a new section, Flows: characters working together.
Worktree improvements
- Parallel agents now see uncommitted work from the main checkout, such as files written by an earlier step. Their results are applied back as uncommitted changes, so nothing is committed to your branch.
- Each loop round gets its own branch.
- A merge conflict fails that step and blocks what depends on it. The branch and worktree are kept so you can resolve it by hand.
Fixes
- The chat's Run pipeline button works again.
- The chat shows events from flow steps, and its pipeline picker refreshes when a flow is saved.
- Several cross-platform fixes in tests and git handling: macOS symlinked temp folders, Windows line endings, and timing-dependent tests.
Upgrade notes
- No action is needed for existing pipelines or characters.
- Saving a linear pipeline from the Flows panel converts it into a flow. The panel warns you first.
- Remove any leftover
skillsets:fields from character files.
What's Changed
- Feature/skills registry by @Eisenmann in #4
- feat: team flows by @Eisenmann in #5
Full Changelog: v1.0.1...v1.1.0