Skip to content

PRODUCT.md

Latest commit

 

History

History
37 lines (23 loc) · 2.17 KB

PRODUCT.md

File metadata and controls

37 lines (23 loc) · 2.17 KB
Raw

Product

Register

product

Users

Developers and technical teams who want one local desktop workspace for multiple ACP agents. They move between projects, agents, models, commands, files, terminals, and conversations, and need the interface to expose the active runtime state without slowing down the work.

Product Purpose

OpenMA Desktop is a local-first, vendor-neutral ACP client. It makes multiple agent harnesses feel like one coherent desktop product while preserving each harness's real capabilities, configuration, commands, and runtime behavior. Success means users can start or resume work quickly, understand what is active, and trust that visible state comes from the selected agent rather than fabricated defaults.

Brand Personality

Calm, precise, and responsive. The product should feel technically capable without becoming noisy, ornamental, or self-important. Copy is direct and concrete; interaction feedback is immediate and spatially stable.

Anti-references

  • Generic AI dashboards with fake capability labels or static model lists.
  • Layouts that jump, squeeze, or reveal accidental scrollbars as transient UI appears.
  • Heavy glass effects, transparent error surfaces, and decorative animation without state meaning.
  • Persistent selected states for structural items such as project folders.
  • Long, repetitive, abstract suggestion copy that does not help the user form a concrete request.

Design Principles

  • Show live truth: derive agent, model, command, and status UI from the selected harness.
  • Preserve spatial continuity: transient suggestions, loading states, and menus should not move stable landmarks.
  • Progressive disclosure over density: keep primary choices compact and reveal detailed capability sets on demand.
  • Make state changes legible: use restrained, tokenized motion and immediate local feedback.
  • Prefer concrete action language: suggestions and errors should help the user take the next step.

Accessibility & Inclusion

Maintain keyboard access, visible focus, semantic labels, sufficient contrast in all themes, and reduced-motion fallbacks. Truncation must preserve accessible names or titles, and color must never be the only carrier of state.