product
Berd is for people doing real work with AI agents inside a desktop workspace: engineers, product designers, and other builders who need a persistent agent companion that can use projects, skills, extensions, automations, model providers, and local workspace context. Users are often moving between broad product thinking and concrete implementation, so the interface needs to support fast chat, precise context selection, and confidence about what the agent can see or do.
Berd packages the desktop agent experience as a standalone Tauri app that talks to the Goose backend through ACP. Its job is to make agent work feel grounded, inspectable, and continuous: start a chat, attach files or folders, choose agents and models, work inside projects, manage skills and extensions, review session history, configure providers, and build automations without losing the thread of the workspace.
Success looks like a user trusting the app as their daily AI work surface. They should understand where they are, what context is active, which model or agent is responding, and how to recover or adjust settings when something is not ready.
Focused, capable, companionable. Berd should feel like a calm, practical desktop tool with enough warmth to make repeated daily use pleasant. It should respect expert users without becoming cold or cryptic, and it should help less configured states feel approachable rather than broken.
Do not make Berd feel like a generic chatbot wrapper, a dark terminal skin, a dashboard stuffed with metrics, or a marketing site wearing product chrome. Avoid novelty-first AI visuals, oversized decorative cards, vague "assistant magic" copy, and interfaces that hide operational state behind friendliness. The product should not feel like a toy, a sales demo, or a pile of disconnected settings pages.
Make context legible. The user should always be able to tell which project, files, agent, model, provider, and session state are shaping the conversation.
Keep the work surface quiet. The interface should preserve attention for the conversation, active tools, and workspace state; chrome should be useful, dense, and calm.
Treat configuration as part of the workflow. Providers, extensions, skills, automations, projects, and onboarding are not admin leftovers; they are how users shape what Berd can do.
Show operational truth plainly. Loading, streaming, compacting, unavailable providers, failed imports, empty states, and permission-like boundaries should be honest and actionable.
Design for continuity. Sessions, projects, history, navigation, and workspace context should make it easy to resume work without rebuilding mental state.
Use semantic controls, labels for icon-only actions, keyboard-reachable navigation, visible focus states, localized strings, and reduced-motion-aware interaction patterns. Product work should preserve readability in light and dark themes, avoid relying on color alone for state, and keep compact desktop layouts usable without sacrificing touch or assistive technology affordances where applicable.