v0.9.0

OpencodeView 0.9.0

Source-only OSS release. This release publishes the Git repository, annotated
tag, and GitHub Release notes. It does not publish packages to a registry,
binaries, installers, or container images. Both root and web packages remain
private: true.

Status

• Licensed under Apache-2.0.
• Run from source with Bun >=1.3.0.
• Tag: v0.9.0.
• Ledger entry recorded in docs/release/ledger.json.

Scope

• Local, read-only analytics dashboard for OpenCode session data.
• Source database access stays read-only, with derived metrics written only to a
  separate OpencodeView cache.
• EN-US canonical documentation with PT-BR semantic parity.
• Release harness and dependency audit gates for a fast path toward 1.0.0.
• Frontend performance and accessibility polish: lazy-loaded dashboard views
  and charts, overflow-gated table scroll affordances, explicit load/error
  panel states, specific table accessible labels, and chart title/description
  names.
• Exclusive GitHub identity gate for owner account 4i3n6.

Security And Privacy

• The API and Vite development server bind to loopback by default.
• Non-loopback API binding still requires OPENCODEVIEW_AUTH_TOKEN, and API
  responses remain Cache-Control: no-store.
• Transcript, tool payload, title, error, and path data still go through
  server-side redaction before API serialization.
• OpencodeView does not add telemetry or outbound network calls; it reads local
  SQLite files and serves the local dashboard.
• The dependency audit blocker from postcss <=8.5.17 is remediated by updating
  Vite's parent dependency chain and regenerated Bun lock data.

Install From Source

git clone https://github.com/4i3n6/opencodeview.git
cd opencodeview
bun install
cd web && bun install && cd ..
bun src/scan.ts --all
bun run serve
bun run web

Local Validation

bun run check
bun run release:check

Known Limitations

• OpenCode's opencode.db schema is internal and unstable, so the SQLite adapter
  remains best-effort and version-sensitive.
• The cache schema, API, CLI flags, and environment variables can still change
  before 1.0.0.
• OAuth-based OpenCode usage can report zero cost, so cost comparisons are only
  meaningful within the same billing regime.
• Upstream summary_additions gaps for sessions created in 2026-06 and 2026-07
  remain flagged as data_quality_gap.
• This release is not a support promise for production exposure beyond loopback;
  non-loopback operation requires independent hardening.