ClickVibe v0.1.0 — Experimental Working Baseline

ClickVibe v0.1.0 — Experimental Working Baseline

ClickVibe v0.1.0 is the first public baseline of the DSH Web plugin. It is a
developer preview: the main Issue-driven development loop works, but the
release is not a production-stability claim.

What works

• Load GitHub repositories and open Issues into a project-oriented panel.
• Create or recover an Issue-specific branch and worktree from a selectable
  remote baseline.
• Run Codex or Claude for development, review, rework, and resumed sessions.
• Bind review results to the reviewed commit and Issue contract snapshot.
• Create PRs, publish delivery history, enforce merge gates, and perform
  authorized merge and cleanup.
• Run an Issue automatically through development and review, with optional
  automatic merge.
• Preserve task output, workflow events, diagnostic errors, and recoverable
  conflict state for inspection.
• Trigger the same backend actions from the panel or text commands with
  preview and short-lived authorization.

Known limitations

• Git, gh, and GitHub REST access has grown feature by feature. Reads are not
  yet fully consolidated behind one request-accounting and cache policy.
• Existing TTL, throttling, and rate-limit recovery mechanisms are useful but
  do not yet form a complete repository-wide scheduler.
• Automatic merge, conflict recovery, host restart recovery, and concurrent
  workflow writes are experimental. Inspect Git/GitHub facts and local logs
  when an exceptional path does not converge.
• Logs and diagnostic events exist, but there is no complete cross-component
  trace and deterministic replay model yet.
• The protocol Observer is documented as an out-of-loop audit skill; it is not
  a first-class runtime task or self-improving control loop.
• ClickVibe trusts the local developer environment and must remain bound to
  loopback. Do not expose it directly to a LAN or the public Internet.
• Compatibility is not guaranteed across 0.x releases. Back up
  ~/.clickvibe/state/ before upgrading and expect migration notes when state
  or API contracts change.

Release boundary

This tag freezes the currently working implementation so later architecture
work has an explicit historical baseline. It does not declare every open PR or
Issue complete, and it does not turn current implementation accidents into
permanent product principles.

In particular, v0.1 supports both manually authorized merge and optional
automatic merge. The old wording that “merge is always left to a human”
describes the original operating posture, not the future ceiling of ClickVibe.

The next architecture phase starts by consolidating Git/GitHub operations,
request accounting, cache policy, and evidence boundaries. More advanced
capabilities such as protocol-level observation and controlled self-improvement
remain later milestones rather than v0.1 commitments.

Install from source

Requirements: Node.js 24, pnpm 11, DSH Web, local git, authenticated gh,
and either Codex or Claude for agent execution.

git clone https://github.com/ai-daming/clickvibe.git
cd clickvibe
git checkout v0.1.0
pnpm install --frozen-lockfile
pnpm run build
dsh plugin --profile web add link:"$PWD"

Configure ~/.clickvibe/config.yaml as described in the repository README,
then restart DSH Web.

Verification baseline

The release is gated by type checking, production builds, the complete test
suite, coverage thresholds, lint and formatting checks, file-size and import
layer checks, style-token checks, and workflow-state write-boundary checks.