Skip to content

Wukong Code v0.0.13

Choose a tag to compare

View all tags
@xxg1413 xxg1413 released this 16 Jul 15:04
v0.0.13
013b622

Wukong Code 0.0.13 — Review until ready

Status: released as v0.0.13. The release tag triggers native builds for the six supported platform targets.

Upgrade from 0.0.12

Native 0.0.12 binaries still contain the old manual-upgrade behavior. Upgrade once through the verified installer:

curl -fsSL https://wukong.today/install.sh | sh

The installer selects the matching 0.0.13 release asset, verifies its SHA-256 file, and replaces the binary in the existing install directory. Starting with 0.0.13, macOS and Linux native installs can use wukong upgrade for later releases.

What's Changed

0.0.13 makes the review step useful inside the Loop. Wukong now returns multiple structured findings, separates blocking defects from non-blocking advice, and feeds concrete blockers into the next coding iteration.

Structured review findings

  • Each finding has a stable ID, severity, category, evidence, file location, next action, confidence, and validation status.
  • Only blocking findings produce NEEDS_WORK; important and note findings remain visible without creating an endless repair loop.
  • Invalid reviewer output is retried once, counted locally, and becomes ERROR when no trustworthy result can be produced.
  • Legacy 0.0.12 single-blocker reviewer output remains readable.

Project review policy

Run:

wukong review init

This creates .wukong/review-policy.md. The policy becomes part of the workspace fingerprint and reviewer input, so a verdict cannot be reused after the policy changes. Project policy is treated as untrusted review criteria and never grants the reviewer write or shell permissions.

Local feedback and review statistics

Record whether a finding was useful:

wukong review feedback <finding-id> accept
wukong review feedback <finding-id> false-positive
wukong review feedback <finding-id> fixed
wukong review feedback <finding-id> unclear
wukong review stats

The same actions are available in the TUI through /review. Feedback, optional reasons, reviewer-cycle counts, and invalid-output counts stay in ~/.wukong/review/ by default. Wukong hides quality percentages until at least 10 findings have feedback.

Independent reviewer model

Use another configured model for the read-only reviewer:

wukong loop "finish the API change" --review-model reviewer

The writer model remains unchanged. 0.0.13 stays free and bring-your-own-key; no managed reviewer credits or paid entitlement are introduced.

Loop-first TUI and Web copy

  • Idle TUI chrome now points users to /loop <goal> instead of showing zero-value Today, verify, scan, and proof counters.
  • Loop phases use Write, Check, Review, and Fix language.
  • The website, download flow, Pricing, Dashboard, Onboarding, terminal preview, SEO, and email copy use the same Goal → Write → Check → Review → Fix model.
  • Existing hosted reports remain a compatibility surface, not the primary 0.0.13 workflow.

Deliberately deferred

  • Payment, Checkout, subscription management, and real Pro entitlements
  • Automatic policy mutation or cloud reviewer improvers
  • GitHub PR comments and status checks
  • Team policy synchronization and managed reviewer credits

These remain 0.1.0+ work. Pro and Team stay Coming Soon until real Loop activation and review value are validated.

Assets 14
Loading