Vibecode Admix
track this build5 steps, step by step0%KINDA · weekend project
A local chat UI with side-by-side replies is a weekend project when it calls OpenRouter, but Admix's value depends on access to many hosted models, a current catalog, provider routing, and a maintained account and billing layer. You can reproduce the comparison workflow. You cannot reproduce the model access and service layer for a flat $10 subscription.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Admix. 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 ===== # Admix indie build ## Goal Build the smallest trustworthy replacement for the core Admix workflow for one developer or a tiny team. ## Scope Send one prompt to selected models through OpenRouter, stream the replies into a side-by-side grid, and save the thread locally. ## 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: - Admix's bundled access to many providers under one subscription - A maintained model catalog and provider routing - Cross-device sync and account history - Built-in image, search, and document workflows - Usage limits, billing, and support handled for you If those capabilities are essential, use Open WebUI 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 me a local multi-model comparison chat to replace Admix. Requirements: - Node 22 + Express + better-sqlite3, a server-rendered shell with a little vanilla JS for streaming; no frontend framework, no build step. - One OpenRouter key in .env, kept server-side; the server proxies all model calls. - A model picker fed from OpenRouter's /models endpoint; select up to four models. - One prompt fans out to the selected models and streams each reply into a side-by-side grid with model name, elapsed time, and token usage when reported; a failed model shows its error in its own column without killing the others. - Markdown rendering with fenced code blocks and a copy button per reply. - Threads, prompts, model ids, replies, and timestamps in SQLite; full-text search across saved threads; export a thread as Markdown. - A running cost estimate per thread from OpenRouter's usage and pricing fields. - Binds to localhost only. No accounts, no telemetry; prompts and replies leave the machine only for OpenRouter, and the README says so. - Out of scope: auth, billing, mobile apps, image generation, hosted sync, and provider-specific tools like web search or file upload. - README: setup, .env.example, and how to add a model id by hand if the catalog fetch fails. ## Required capabilities - Node 22 - OpenRouter API key in .env - SQLite - Provider and model IDs to compare ## 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 Admix. 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 ===== # Admix indie build ## Goal Build the smallest trustworthy replacement for the core Admix workflow for one developer or a tiny team. ## Scope Send one prompt to selected models through OpenRouter, stream the replies into a side-by-side grid, and save the thread locally. ## 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: - Admix's bundled access to many providers under one subscription - A maintained model catalog and provider routing - Cross-device sync and account history - Built-in image, search, and document workflows - Usage limits, billing, and support handled for you If those capabilities are essential, use Open WebUI 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 me a local multi-model comparison chat to replace Admix. Requirements: - Node 22 + Express + better-sqlite3, a server-rendered shell with a little vanilla JS for streaming; no frontend framework, no build step. - One OpenRouter key in .env, kept server-side; the server proxies all model calls. - A model picker fed from OpenRouter's /models endpoint; select up to four models. - One prompt fans out to the selected models and streams each reply into a side-by-side grid with model name, elapsed time, and token usage when reported; a failed model shows its error in its own column without killing the others. - Markdown rendering with fenced code blocks and a copy button per reply. - Threads, prompts, model ids, replies, and timestamps in SQLite; full-text search across saved threads; export a thread as Markdown. - A running cost estimate per thread from OpenRouter's usage and pricing fields. - Binds to localhost only. No accounts, no telemetry; prompts and replies leave the machine only for OpenRouter, and the README says so. - Out of scope: auth, billing, mobile apps, image generation, hosted sync, and provider-specific tools like web search or file upload. - README: setup, .env.example, and how to add a model id by hand if the catalog fetch fails. ## Required capabilities - Node 22 - OpenRouter API key in .env - SQLite - Provider and model IDs to compare ## 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 Admix. 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 ===== # Admix product brief ## Problem A local chat UI with side-by-side replies is a weekend project when it calls OpenRouter, but Admix's value depends on access to many hosted models, a current catalog, provider routing, and a maintained account and billing layer. You can reproduce the comparison workflow. You cannot reproduce the model access and service layer for a flat $10 subscription. ## Product outcome Send one prompt to selected models through OpenRouter, stream the replies into a side-by-side grid, and save the thread locally. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node 22 - OpenRouter API key in .env - SQLite - Provider and model IDs to compare ## Explicit non-goals for v1 - Admix's bundled access to many providers under one subscription - A maintained model catalog and provider routing - Cross-device sync and account history - Built-in image, search, and document workflows - Usage limits, billing, and support handled for you ## 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 me a local multi-model comparison chat to replace Admix. Requirements: - Node 22 + Express + better-sqlite3, a server-rendered shell with a little vanilla JS for streaming; no frontend framework, no build step. - One OpenRouter key in .env, kept server-side; the server proxies all model calls. - A model picker fed from OpenRouter's /models endpoint; select up to four models. - One prompt fans out to the selected models and streams each reply into a side-by-side grid with model name, elapsed time, and token usage when reported; a failed model shows its error in its own column without killing the others. - Markdown rendering with fenced code blocks and a copy button per reply. - Threads, prompts, model ids, replies, and timestamps in SQLite; full-text search across saved threads; export a thread as Markdown. - A running cost estimate per thread from OpenRouter's usage and pricing fields. - Binds to localhost only. No accounts, no telemetry; prompts and replies leave the machine only for OpenRouter, and the README says so. - Out of scope: auth, billing, mobile apps, image generation, hosted sync, and provider-specific tools like web search or file upload. - README: setup, .env.example, and how to add a model id by hand if the catalog fetch fails. ## 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 Admix capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Admix indie build ## Goal Build the smallest trustworthy replacement for the core Admix workflow for one developer or a tiny team. ## Scope Send one prompt to selected models through OpenRouter, stream the replies into a side-by-side grid, and save the thread locally. ## 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: - Admix's bundled access to many providers under one subscription - A maintained model catalog and provider routing - Cross-device sync and account history - Built-in image, search, and document workflows - Usage limits, billing, and support handled for you If those capabilities are essential, use Open WebUI 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 me a local multi-model comparison chat to replace Admix. Requirements: - Node 22 + Express + better-sqlite3, a server-rendered shell with a little vanilla JS for streaming; no frontend framework, no build step. - One OpenRouter key in .env, kept server-side; the server proxies all model calls. - A model picker fed from OpenRouter's /models endpoint; select up to four models. - One prompt fans out to the selected models and streams each reply into a side-by-side grid with model name, elapsed time, and token usage when reported; a failed model shows its error in its own column without killing the others. - Markdown rendering with fenced code blocks and a copy button per reply. - Threads, prompts, model ids, replies, and timestamps in SQLite; full-text search across saved threads; export a thread as Markdown. - A running cost estimate per thread from OpenRouter's usage and pricing fields. - Binds to localhost only. No accounts, no telemetry; prompts and replies leave the machine only for OpenRouter, and the README says so. - Out of scope: auth, billing, mobile apps, image generation, hosted sync, and provider-specific tools like web search or file upload. - README: setup, .env.example, and how to add a model id by hand if the catalog fetch fails. ## Required capabilities - Node 22 - OpenRouter API key in .env - SQLite - Provider and model IDs to compare ## 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
# Admix product brief ## Problem A local chat UI with side-by-side replies is a weekend project when it calls OpenRouter, but Admix's value depends on access to many hosted models, a current catalog, provider routing, and a maintained account and billing layer. You can reproduce the comparison workflow. You cannot reproduce the model access and service layer for a flat $10 subscription. ## Product outcome Send one prompt to selected models through OpenRouter, stream the replies into a side-by-side grid, and save the thread locally. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node 22 - OpenRouter API key in .env - SQLite - Provider and model IDs to compare ## Explicit non-goals for v1 - Admix's bundled access to many providers under one subscription - A maintained model catalog and provider routing - Cross-device sync and account history - Built-in image, search, and document workflows - Usage limits, billing, and support handled for you ## 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 me a local multi-model comparison chat to replace Admix. Requirements: - Node 22 + Express + better-sqlite3, a server-rendered shell with a little vanilla JS for streaming; no frontend framework, no build step. - One OpenRouter key in .env, kept server-side; the server proxies all model calls. - A model picker fed from OpenRouter's /models endpoint; select up to four models. - One prompt fans out to the selected models and streams each reply into a side-by-side grid with model name, elapsed time, and token usage when reported; a failed model shows its error in its own column without killing the others. - Markdown rendering with fenced code blocks and a copy button per reply. - Threads, prompts, model ids, replies, and timestamps in SQLite; full-text search across saved threads; export a thread as Markdown. - A running cost estimate per thread from OpenRouter's usage and pricing fields. - Binds to localhost only. No accounts, no telemetry; prompts and replies leave the machine only for OpenRouter, and the README says so. - Out of scope: auth, billing, mobile apps, image generation, hosted sync, and provider-specific tools like web search or file upload. - README: setup, .env.example, and how to add a model id by hand if the catalog fetch fails. ## 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 Admix 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
They pay for one bill and one interface instead of managing several provider accounts, API keys, model IDs, and usage limits. The comparison grid is easy to copy; keeping model access and the account, billing, and storage layer working is the service.
xAdmix's bundled access to many providers under one subscription
xA maintained model catalog and provider routing
xCross-device sync and account history
xBuilt-in image, search, and document workflows
xUsage limits, billing, and support handled for you
share on X ↗"I just replaced Admix ($10/mo) with one prompt"
Don't feel like building it? These folks already made it free.
Cherry StudioA desktop model cockpit with parallel answers, files, agents, and rather more settings than restraint.open source↗
Cherry StudioSame prompt, several models, side by side; bring API keys or make local models do the arguing.open source↗
ChatALLThe exact compare-everyone desktop app; use API-backed bots, because scraped web connectors break whenever vendors sneeze.open source↗all 5 free alternatives to Admix →· no votes, no pay-to-list · just what's real
Admix pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| free | $0 | $0 | 20 credits/day; Gemini 2.5 Flash access. |
| starter | $10 | $8 | 500 credits/month; 350+ models; 10 cross-chat memories. |
| basic | $19 | $15.20 | 1,500 credits/month; 350+ models; 30 cross-chat memories. |
| pro | $39 | $31.20 | 4,000 credits/month; 350+ models; 100 cross-chat memories; per-model memory. |
| max | $99 | $79.20 | 10,000 credits/month; 350+ models; 100 cross-chat memories. |
free tier20 credits/day; Gemini 2.5 Flash access.
billingmonthly + annual (-20%); paid plans begin with a $1.99 7-day trial that auto-renews
hidden costsCredits are model-dependent and multi-model/parallel comparisons consume multiple allocations; the paid trial auto-renews.
verified 2026-08-12 · source ↗
Vibecode Admix
Kinda. The core of Admix is buildable in a weekend with the prompt on this page, but there are real gaps: Admix's bundled access to many providers under one subscription, A maintained model catalog and provider routing. Read the honest list above before committing.
How much does Admix cost?
Admix costs about $10/month (Starter, checked 2026-08-03), which is $120 per year.
What do I lose by replacing Admix?
Honestly: Admix's bundled access to many providers under one subscription; A maintained model catalog and provider routing; Cross-device sync and account history; Built-in image, search, and document workflows; Usage limits, billing, and support handled for you. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Admix?
Yes: Cherry Studio (A desktop model cockpit with parallel answers, files, agents, and rather more settings than restraint.) Cherry Studio (Same prompt, several models, side by side; bring API keys or make local models do the arguing.) ChatALL (The exact compare-everyone desktop app; use API-backed bots, because scraped web connectors break whenever vendors sneeze.) All 5 curated free alternatives are at vibecodeit.com/admix/alternatives. The prompt is for when you want it exactly your way.