# Build brief — a focused alternative to BoltAI > **Verdict:** Partly, if you narrow it · **Buildability:** 56/100 · **Category:** AI Assistant > **Source:** https://www.canitbevibecoded.com/boltai > Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from BoltAI. Verify current pricing and capabilities before acting. ## Context **BoltAI** — Private native AI workspace for Mac with multiple models, agents, workflows, files, and tools. A coding agent can one-shot a basic chat window that calls a few AI APIs. That reproduces only a small part of BoltAI. A credible replacement must remain fast with large histories and active streams, combine SwiftUI with purpose-built AppKit components where the framework falls short, and make focus, keyboard navigation, menus, windows, drag and drop, and global shortcuts behave like a real Mac app. It must also reproduce AI Workflows, Instant Chat, Instant Dictation, attachments, tools, provider-specific behavior, local persistence, sync recovery, and protected credentials. These are interacting product systems, not a collection of generated screens. This brief describes a focused, single-operator replacement for the part of BoltAI that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest. ## What you are building Build a performant native Mac chat client for a few AI providers with streaming, searchable history, attachments, agents, workflows, and basic MCP support. - Answer from retrieval over your own notes and files, with sources visible. - A responsive interface with real empty, loading, success, and error states. ## Requirements ### Functional - MacOS 13 or later. - Xcode with a Swift 6 toolchain. - Ollama for optional local models. - Accessibility and microphone permissions for system-wide workflows. ### Data and integrations - API keys for the selected cloud providers. Each of these needs a real account, credential, or quota. Set them up before writing feature code. ### Non-functional - Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support. - Security: server-side secrets, validated input, and no credentials in the client bundle. - Reliability: retries with backoff on external calls, and a clear failure state when a provider is down. - Portability: the operator can export their data and leave without losing it. ## Implementation brief Build a personal local replacement for BoltAI in an empty repository. Use Swift 6, SwiftUI, AppKit where necessary, Core Data, and macOS Keychain. Do not offer alternative stacks or copy BoltAI branding or visual assets. The goal is a performant native Mac AI workspace, not a web chat wrapped as a desktop app. Make the first run work locally with one documented command. Create a native sidebar for projects and chats, a conversation view, and a composer. Keep navigation, typing, scrolling, and streaming responsive with large chat histories. Profile those interactions and use AppKit-backed controls where naive SwiftUI falls short. Support OpenAI, Anthropic, Google Gemini, and Ollama through documented APIs. Store user-supplied API keys in Keychain. Support streaming, cancellation, retry, regeneration, and recoverable partial responses. Render Markdown, code, images, reasoning, citations, and tool results. Add projects, reusable agents, saved prompts, chat forking, and full-text search. Add reusable workflows that operate on selected text, clipboard content, and files. Add a global Instant Chat panel that accepts files, models, agents, and tools. Add Instant Dictation that transcribes speech and returns text to the original application. Support basic local and remote MCP servers with per-agent tool selection. Store chats and attachments locally with export and backup support. Handle provider failures, rate limits, interrupted streams, and application relaunches safely. Write focused tests for persistence, streaming state, workflows, and provider translation. Create a README covering setup, permissions, performance testing, data, and limitations. Do not add billing, licensing, telemetry, analytics, or proprietary BoltAI services. Deliberately leave out BoltAI Cloud Sync, mobile apps, teams, and hosted AI service. Deliberately leave out full import fidelity, production code execution, and long-tail providers. Finish by running the focused tests and listing the exact commands used. ## Delivery standard - Inspect the repository first, then write a short implementation plan before writing code. - Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data. - Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations. - Include responsive layouts plus genuine empty, loading, success, validation, and failure states. - Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data. - Add structured logs around every external call and return actionable errors without leaking sensitive details. - Write unit tests for the core logic and one automated test of the main user journey. - Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations. ## Acceptance criteria - [ ] A clean install starts the app using only the README and .env.example. - [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable. - [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state. - [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control. - [ ] Tests, type checking, linting, and a production build all pass with no ignored failures. - [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified. ## Non-goals Do not build these, and do not claim to have replaced them: - AppKit-backed performance and responsiveness across large workspaces and conversation histories. - Carefully tuned keyboard navigation, focus, menus, panels, windows, drag and drop, and other native Mac behavior. - AI Workflows that capture context from other applications and return formatted results where the user is working. - Instant Chat and Instant Dictation as reliable system-wide workflows rather than ordinary in-app screens. - Maintained provider compatibility, Cloud Sync, mobile continuity, imports, backup recovery, and protected credential portability. ## What you still own after launch - Secure credentials, rotate secrets, and handle provider rate limits. - Run migrations, backups, restores, and dependency updates. - Test the critical journey after every model, API, or hosting change. - Monitor failures and fix the edge cases a first prompt will miss. - Maintain every third-party integration as APIs and OAuth rules change. ## Risk **Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost. Editorial confidence in this assessment: medium. No reviewed project implementation is linked yet. ## Existing alternatives Before building, compare these checked options: - [AnythingLLM](https://anythingllm.com/) — A private AI desk for documents and agents; install it, then choose local models or somebody else's meter - [Cherry Studio](https://cherryai.com/) — A desktop model switchboard with assistants, files, agents and MCP; bring keys or make your laptop sweat - [Jan](https://jan.ai/) — A local-first desktop assistant with cloud connectors and tools; your RAM gets the invoice --- Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/boltai