# Build brief — a focused alternative to Littlebird

> **Verdict:** Partly, if you narrow it · **Buildability:** 63/100 · **Category:** AI Assistant
> **Source:** https://www.canitbevibecoded.com/littlebird
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Littlebird. Verify current pricing and capabilities before acting.

## Context

**Littlebird** — An AI assistant product sold under the Littlebird name, positioned around letting an agent do the boring reading and drafting for you. It currently costs $20/mo.

Public detail on this one is thin, so treat this entry as a first pass rather than a teardown. Anything in the "AI assistant that reads and drafts for you" shape is mostly a wrapper: a model API, a place to put your context, and a loop that runs on a schedule. A coding agent can rebuild that shape with a focused implementation and you keep the API bill instead of the subscription. What you will not rebuild with a focused implementation is the polish, the mobile surface, and whatever integrations the paid product ships against your actual accounts. Verdict stays "kinda" until someone confirms whether the real value here is the agent loop or the connectors underneath it.

This brief describes a focused, single-operator replacement for the part of Littlebird 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

A local web app where you chat with a model over your own uploaded notes and links, plus a scheduled job that produces a digest of anything you told it to watch.

- 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

- Node 20+ and a machine or small VPS that stays awake for the cron job.
- Willingness to paste your own context in instead of having connectors do it.

### Data and integrations

- An LLM API key (OpenAI or Anthropic) in .env.

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 local personal AI assistant web app in an empty folder. No accounts, no cloud, no telemetry.

Stack, no substitutions:
- TypeScript, Node 20, Fastify for the server
- SQLite via better-sqlite3, file at ./data/assistant.db
- Server-rendered HTML with htmx for interactivity, plain CSS, no React, no Tailwind
- OpenAI-compatible chat completions and embeddings, base URL and key read from .env (OPENAI_API_KEY, OPENAI_BASE_URL, CHAT_MODEL, EMBED_MODEL)
- node-cron for scheduled jobs, all in one process

Features in scope:
1. Context library: paste text, upload .md/.txt, or submit a URL. URLs are fetched server side and reduced to readable text with @mozilla/readability plus jsdom. Chunk to ~800 tokens, embed, store chunks and vectors in SQLite.
2. Chat: a single conversation view. On each message, retrieve the top 8 chunks by cosine similarity, put them in the system prompt with source titles, stream the reply back. Persist all turns.
3. Watchlist: each row is a name, a URL or a search query, and a cadence (daily or weekly). A cron job fetches each item, diffs the extracted text against the last stored snapshot, and asks the model to summarize what changed in under 80 words. Skip items with no meaningful diff.
4. Digest: a /digest page listing the latest summaries newest first, plus a digest.md file written to ./out/ after each run so it is greppable.
5. Every model call is logged to a calls table with model, token counts and latency, and /usage shows totals by day so you can see what you are spending.

Out of scope, do not build: user accounts, OAuth to any third party, email or push notifications, mobile app, multi-user sharing, vector database services, Docker.

Deliver: npm install, npm run dev on port 3000, a seeded example watchlist item, .env.example with every variable, and a README that states plainly what works and what breaks if the process dies.

## 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:

- Mobile app and notifications; your version is a browser tab.
- Prebuilt connectors to email, calendar, Slack and whatever else the paid product authenticates against.
- Someone else tuning prompts and swapping models when a better one ships.
- Reliability: your cron job dies silently and nobody pages you.
- Any team or sharing features, if the product has them.

## 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: low. No reviewed project implementation is linked yet.

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/littlebird