Farm Manager

A personal (and soon multi-user) operating system for life, home, and work.

Capture messy notes. Farm Manager proposes structure — one-time vs recurring, priorities, deadlines, people follow-ups — you confirm. Then it surfaces a Today board, Daily Brief, and in-app pings so you stay ahead.

Stack

• Next.js 16 (App Router) + TypeScript + Tailwind
• Prisma 7 + SQLite (local); schema is workspace-scoped for multi-tenant later
• SpaceXAI / xAI (grok-4.5) for capture + brief (optional; heuristics work without a key)
• PWA manifest for installable web app

Quick start

# 1. Install deps
npm install

# 2. Env
cp .env.example .env
# Optional: set XAI_API_KEY from https://console.x.ai

# 3. Database
npm run db:migrate
# or: npx prisma migrate dev

# 4. PWA icons (optional)
npm run icons

# 5. Dev server
npm run dev

Open http://localhost:3000 → Get started → create an account.

Core flows

Flow	What happens
Capture	Paste brain-dump → AI proposes tasks → you accept
Today	Priority + due-today + follow-ups
People	Open loops per person
Recurring	Templates; occurrences auto-materialize when due
Daily Brief	Morning-style briefing + coach tips
Pings	Bell menu for due reminders

Product principles

1. AI proposes; you confirm — never silent autopilot on your life.
2. Workspace-scoped data — ready for small-team workspaces later.
3. Areas — Work / Home / Life by default.
4. Trustworthy board — complete, snooze, or reschedule; no zombie lists.

Scripts

Script	Purpose
npm run dev	Dev server
npm run build	Production build
npm run db:migrate	Apply migrations (local SQLite)
npm run db:push:turso	Apply Prisma migrations to Turso (prod/preview — Vercel build does not migrate)
npm run db:studio	Prisma Studio
npm run icons	Generate PWA icons

Env vars

Var	Purpose
DATABASE_URL	SQLite path (file:./dev.db)
TURSO_DATABASE_URL / TURSO_AUTH_TOKEN	Production libSQL. Preview uses its own database, aiea-db-preview, not production.

Starting the app does not copy a bf-maintenance database and does not change the schema. Production (aiea-cyan) stays on the old schema until you push the schema immediately before merge, then merge right away — the code that is live now breaks on the new schema.

Back up first (turso db shell <db-name> ".dump" or a Turso branch). Count tasks before and after (SELECT COUNT(*) FROM Task). Find the workspace with SELECT id, name, createdAt FROM Workspace. Then:

vercel env pull .env.vercel --environment=production --yes
FARM_SCHEMA_PUSH=1 node --env-file=.env.vercel scripts/push-turso-schema.mjs

Import only after that backup, into the workspace id you looked up. Load the production env with --env-file. BF_SOURCE_* stays on this command, never in Vercel.

FARM_IMPORT_ALLOW_REMOTE=1 \
  BF_SOURCE_DATABASE_URL="libsql://..." \
  BF_SOURCE_AUTH_TOKEN="..." \
  npx tsx --env-file=.env.vercel scripts/import-bf-data.ts --workspace <id>

A file database needs an explicit --local. With TURSO_DATABASE_URL unset and no --local, the script refuses so it cannot write dev.db:

BF_SOURCE_DATABASE_URL="file:./bf.db" \
  npx tsx scripts/import-bf-data.ts --local --workspace <id>

| XAI_API_KEY | SpaceXAI / xAI key — console.x.ai | | XAI_MODEL | Optional model override (default grok-4.5) | | XAI_BASE_URL | Optional API base (default https://api.x.ai/v1) | | AIEA_TIMEZONE | Optional IANA tz for AI date reasoning (e.g. America/New_York) | | AUTH_SECRET | Session hardening (change in prod) | | CRON_SECRET | Auth for /api/cron/materialize-schedules (daily 12:00 UTC) | | BF_SOURCE_DATABASE_URL / BF_SOURCE_AUTH_TOKEN | Old bf-maintenance database for scripts/import-bf-data.ts. One-shot, on your machine. Never set these in Vercel. | | FARM_IMPORT_WORKSPACE_ID | Workspace that receives that import (or pass --workspace) | | FARM_SCHEMA_PUSH | Set to 1 to allow scripts/push-turso-schema.mjs on a remote database. Not a Vercel env var. | | FARM_IMPORT_ALLOW_REMOTE | Set to 1 to allow the import script to write to Turso. Not a Vercel env var. |

Remove these from Vercel when this app ships: BF_MAINTENANCE_URL, BF_MAINTENANCE_ORIGIN, NEXT_PUBLIC_BF_MAINTENANCE_URL, BF_INTEGRATION_SECRET. Keep CRON_SECRET, TURSO_DATABASE_URL, TURSO_AUTH_TOKEN, AUTH_SECRET, and XAI_*. After the import, freeze bf-maintenance.vercel.app (no further deploys or edits).

Wire SpaceXAI

1. Create an API key at console.x.ai (load credits on the account first).
2. Put it in .env (never commit this file):

XAI_API_KEY="xai-..."

3. Restart the dev server (npm run dev) so Next.js reloads env.
4. Optional live check (while logged in): GET /api/ai/status?ping=1

Without a key, Capture still works via local heuristics.

AI behavior

• Capture uses structured JSON outputs + Zod validation (strict schema) and creates tasks immediately.
• Prompts include clock context (timezone, today, EOM) so deadlines stay grounded.
• On any AI failure, the app falls back to heuristics. The field also offers Retry and Save as one task.

Roadmap (post-MVP)

• Web Push + email/SMS channels
• Calendar sync (Google / Apple)
• Multi-user workspace invites & shared Home lists
• Email/Slack ingest
• Native mobile shells

License

Private — all rights reserved unless you choose otherwise.

Agent verification (pstack / poteto)

Hong / agents: use poteto-mode with the project skill .cursor/skills/verify-aiea/ (launch → doctor → Playwright drive → evidence). Confirm ~/.cursor/rules/pstack-models.mdc on the box. One-shot:

./.cursor/skills/verify-aiea/scripts/gate.sh --local --feature capture-accept

Live/post-auth needs AIEA_SMOKE_EMAIL + AIEA_SMOKE_PASSWORD (both; smoke user only — never personal / 1Password). When unset, gate.sh --live-smoke clean-skips (CI stays green). On a pull request it also clean-skips: production is still the pre-merge app, while this revision’s doctor requires the public landing page on logged-out GET / and 307 to /tasks when signed in. That check stays strict on main. Hong creates the smoke User row; verify does not. Set CI secrets with gh secret set (see .cursor/skills/verify-aiea/SKILL.md). Legacy AIEA_EMAIL/AIEA_PASSWORD are demoted — migrate to SMOKE names. No separate BF_* pair for smoke login. Parallel to bf-maintenance verify — do not conflate with BF PIN / #20 login threads.