Vibecode BoltAI
track this build5 steps, step by step0%KINDA · weekend project
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.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of BoltAI. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # BoltAI indie build ## Goal Build the smallest trustworthy replacement for the core BoltAI workflow for one developer or a tiny team. ## Scope Build a performant native Mac chat client for a few AI providers with streaming, searchable history, attachments, agents, workflows, and basic MCP support. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - 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 If those capabilities are essential, use AnythingLLM instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build 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. ## Required capabilities - macOS 13 or later - Xcode with a Swift 6 toolchain - API keys for the selected cloud providers - Ollama for optional local models - Accessibility and microphone permissions for system-wide workflows ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of BoltAI. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # BoltAI indie build ## Goal Build the smallest trustworthy replacement for the core BoltAI workflow for one developer or a tiny team. ## Scope Build a performant native Mac chat client for a few AI providers with streaming, searchable history, attachments, agents, workflows, and basic MCP support. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - 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 If those capabilities are essential, use AnythingLLM instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build 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. ## Required capabilities - macOS 13 or later - Xcode with a Swift 6 toolchain - API keys for the selected cloud providers - Ollama for optional local models - Accessibility and microphone permissions for system-wide workflows ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of BoltAI. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # BoltAI product brief ## Problem 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. ## Product outcome Build a performant native Mac chat client for a few AI providers with streaming, searchable history, attachments, agents, workflows, and basic MCP support. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - macOS 13 or later - Xcode with a Swift 6 toolchain - API keys for the selected cloud providers - Ollama for optional local models - Accessibility and microphone permissions for system-wide workflows ## Explicit non-goals for v1 - 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 ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting 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. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted BoltAI capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# BoltAI indie build ## Goal Build the smallest trustworthy replacement for the core BoltAI workflow for one developer or a tiny team. ## Scope Build a performant native Mac chat client for a few AI providers with streaming, searchable history, attachments, agents, workflows, and basic MCP support. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - 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 If those capabilities are essential, use AnythingLLM instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build 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. ## Required capabilities - macOS 13 or later - Xcode with a Swift 6 toolchain - API keys for the selected cloud providers - Ollama for optional local models - Accessibility and microphone permissions for system-wide workflows ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# BoltAI product brief ## Problem 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. ## Product outcome Build a performant native Mac chat client for a few AI providers with streaming, searchable history, attachments, agents, workflows, and basic MCP support. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - macOS 13 or later - Xcode with a Swift 6 toolchain - API keys for the selected cloud providers - Ollama for optional local models - Accessibility and microphone permissions for system-wide workflows ## Explicit non-goals for v1 - 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 ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting 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. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted BoltAI capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent
People do not pay for BoltAI because it is the only app capable of putting a prompt box beside an API. Many native and Electron clients already do that. They pay because BoltAI is a fast, coherent Mac workspace where long histories, streaming responses, keyboard navigation, global panels, dictation, workflows, files, and tools behave like one product. Achieving that requires continuous profiling, AppKit-level engineering, product taste, and repair of real-world edge cases. AI can generate a large SwiftUI codebase quickly; it cannot one-shot the accumulated judgment and maintenance required to make that code feel native and remain performant.
xAppKit-backed performance and responsiveness across large workspaces and conversation histories
xcarefully tuned keyboard navigation, focus, menus, panels, windows, drag and drop, and other native Mac behavior
xAI Workflows that capture context from other applications and return formatted results where the user is working
xInstant Chat and Instant Dictation as reliable system-wide workflows rather than ordinary in-app screens
xmaintained provider compatibility, Cloud Sync, mobile continuity, imports, backup recovery, and protected credential portability
share on X ↗"I just replaced BoltAI with one prompt"
Don't feel like building it? These folks already made it free.
AnythingLLMA private AI desk for documents and agents; install it, then choose local models or somebody else's meter.open source↗
Cherry StudioA desktop workspace for many models, agents, files, tools, and an impressive number of toggles.open source↗
Cherry StudioA desktop model switchboard with assistants, files, agents and MCP; bring keys or make your laptop sweat.open source↗all 8 free alternatives to BoltAI →· no votes, no pay-to-list · just what's real
BoltAI pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| evaluation | $0/user | — | Evaluation access; exact duration and numeric usage cap are not published. |
| essential | custom | — | 1 seat; 1 desktop device; 512 MB cloud storage; 1 year of updates, cloud access, and mobile access. |
| pro | custom | — | 2 desktop devices + 1 mobile device; 1 GB cloud storage; 1 year of updates, cloud access, and mobile access. |
| team perpetual | custom | — | Minimum 5 seats; 1 device/seat; 10 GB shared cloud storage; 1 year of updates and cloud access. |
free tierno permanent free tier; evaluation mode exists, but its numeric cap is not published
billingone-time perpetual licenses; 1 year of updates/cloud included; optional annual renewal, no monthly subscription
hidden costsModel-provider API usage is BYOK and billed separately. Personal renewal defaults to 60% of the original pre-discount license price; Team requires 5 seats. After included cloud access ends, data becomes read-only and may be deleted after 24 months without renewal.
verified 2026-08-12 · source ↗
Vibecode BoltAI
Kinda. The core of BoltAI is buildable in a weekend with the prompt on this page, but there are real gaps: 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. Read the honest list above before committing.
How much does BoltAI cost?
BoltAI's pricing is usage-based or varies by plan · List price is 79 USD; a temporary sale price of 55 USD was shown when checked..
What do I lose by replacing BoltAI?
Honestly: 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. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to BoltAI?
Yes: AnythingLLM (A private AI desk for documents and agents; install it, then choose local models or somebody else's meter.) Cherry Studio (A desktop workspace for many models, agents, files, tools, and an impressive number of toggles.) Cherry Studio (A desktop model switchboard with assistants, files, agents and MCP; bring keys or make your laptop sweat.) All 8 curated free alternatives are at vibecodeit.com/boltai/alternatives. The prompt is for when you want it exactly your way.