Skip to content

v2.7.0 - skilled agents, specs that travel, a chat that heals

Choose a tag to compare

View all tags
@Samuel0101010 Samuel0101010 released this 11 Jun 18:02
· 5 commits to main since this release
v2.7.0
This tag was signed with the committer’s verified signature.
Samuel0101010
SSH Key Fingerprint: m42L3OvnFCqALlIR7/TWil0tlcwO6R8KhmAjv9dGNCA
Verified
Learn about vigilant mode.
10b3967
This commit was signed with the committer’s verified signature.
Samuel0101010
SSH Key Fingerprint: m42L3OvnFCqALlIR7/TWil0tlcwO6R8KhmAjv9dGNCA
Verified
Learn about vigilant mode.

Execution agents now carry working methods (skills) in their instructions — the lever that keeps smaller models reliable. A spec attached in the team chat becomes the project brief with one manager action. And a transient auth hiccup at boot no longer bricks chat and runs until restart.

Highlights

Skilled agents (works better with smaller models)

  • Teams assign skills per role (new picker in the Team Builder); the orchestrator renders each skill's instructions into that agent's system prompt at dispatch. Until now skills only existed for the chat manager — builder/QA agents never saw any.
  • Three new built-in execution skills: builder-discipline (read before write, smallest correct change, run the gates before claiming done), qa-verification (execute, don't assume; evidence per claim), frontend-quality (states, responsiveness, accessibility, consistency).
  • Every surface that creates a team — all 10 templates, the default team, chat project creation, the add-built-in-agent flow — assigns sensible defaults by role (QA roles get qa-verification, frontend builders get builder-discipline + frontend-quality, …).
  • Plan generation re-stamps skills from the stored team, so no planner model can ever drop them.
  • Bonus: the merge-conflict resolver now receives the project brief context instead of resolving conflicts blind.

Specs that travel: import_brief

  • File upload in the team chat already worked — but the attached spec never reached the build agents. Now the manager can write an uploaded .md/.txt spec verbatim to docs/PRD.md and finalise the brief right after create_project (taught in its prompt; receipt card in chat). The crew builds from the full spec, not a one-line goal.

A chat that heals

  • A boot-time auth probe timeout (busy machine) used to 503-block chat and runs until the next restart. All four gates now re-probe on a cached failure (throttled to once per minute, shared in-flight) and self-heal — the warning banner clears on its own.

From PR #110

  • The live-tail dialog restores a finished task's output from the persisted run log after a page reload.
  • Chat links to deleted projects degrade to a plain "project has since been deleted" note instead of a 404.

Verification

End-to-end live proof of the full story: spec attached in chat → manager quoted a secret marker from the file (proving it reads uploads) → create_project → import_brief (PRD verbatim on disk, brief 100%, committed) → plan carried each role's skills → real run: the spawned CLI processes were probed mid-run and showed ### Skill: builder-discipline + frontend-quality (sonnet builder) and ### Skill: qa-verification (haiku QA) in their prompts → release gate READY, auto-merge, finished app matching the spec including edge-case evidence screenshots. Gates: 8/8 local (698 server / 241 web / 169 orchestrator / 71 schemas tests, +28 new), e2e 54/54, CI green on PR #111 and main.

Install / Update

claude plugin marketplace add Samuel0101010/wisp-orchestrator
claude plugin install wisp@wisp-orchestrator
Assets 2
Loading