Skip to content

v0.8.48 tracker: presence pass #1882

@Hmbown

Description

@Hmbown

Release theme

v0.8.48 should make the product feel inevitable for both users and contributors. The first minute, the main loop, the stuck states, the finish, and the public front door should feel composed, legible, and exact.

This is the presence, default-experience, and community-front-door release: your agents' favorite agent.

Product thesis

The terminal can have taste. It can be quiet when work is routine, precise when something fails, and satisfying when a task completes.

The project can also teach without talking down. The website, issue flow, contribution docs, and PR review language should make people feel like capable colleagues: here is what we know, here is what we need, here is where your help fits.

In scope

  • First-run and first-30-seconds polish: install verification, project understanding, initial affordances, and clean fallback paths.
  • A composed task finale: changed files, tests, issues/PRs, evidence, risks, and next action.
  • Visual hierarchy and theme polish that improves legibility without turning the terminal into decoration.
  • Sensible defaults for model/provider, compaction, thinking display, status, notifications, and recovery.
  • Performance and noise budget pass: remove redundant status spam, smooth long-output rendering, and keep details inspectable on demand.
  • A manual release smoke path that exercises the product as a new user, not only as a maintainer running gates.
  • Website contribution path: report a bug, request a feature, find known issues, start a small PR, and understand the roadmap.
  • Issue and PR templates that teach evidence quality, scope, tests, and contributor credit.
  • Contributor docs that explain how maintainers merge, harvest, credit, defer, or close work.
  • Public-facing roadmap copy that is ambitious without becoming vague marketing.

Candidate issue/PR clusters

Review lenses

  • HCI thinker: does the full experience feel inevitable, or does it still expose implementation seams?
  • Brave beginner: can a new user install, start, recover, and contribute without insider knowledge?
  • Open-source maintainer: do website, issue templates, PR templates, and comments teach people how to provide useful signal?
  • Terminal power user: does polish improve legibility and flow without adding latency, clutter, or decorative distraction?
  • Expert agent operator: does the final task summary make verification and next action obvious?

Acceptance criteria

  • A fresh user can install, launch, configure, and complete a representative task with clear status and recovery options.
  • The end-of-task summary is concise, evidence-backed, and useful for shipping.
  • The default UI has a clear visual hierarchy across common terminal sizes.
  • Notifications and polish are tasteful, optional where appropriate, and do not hide terminal truth.
  • The website gives clear routes to file a useful issue, make a first PR, read the roadmap, and check current known issues.
  • Issue/PR templates help contributors give maintainers the evidence needed to act.
  • Contributor guidance uses a teacher-colleague voice: direct, respectful, specific, and oriented toward making the next contribution easier.
  • Release verification includes a manual first-run smoke path in addition to normal automated gates.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or requestquestionFurther information is requested

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions