motir-core

Open-source PM substrate for Motir — an AI-native project management tool for small startup teams. The user describes what they want to build; Motir produces a structured Epic → Story → Subtask tree; coding agents execute the Subtasks one at a time using prompts Motir generates.

Open source

motir-core is open source under the GPL-3.0 license (see LICENSE). This repo is the PM substrate: Work Items, Stories, dependency graph, multi-tenant workspaces, projects, the tree-view UI, GitHub integration, the human-todo queue, the delivery agent. The kind of thing Jira and Linear are, but open and AI-native.

The closed-source planning intelligence — the planner agent, prompt generation, async-expansion loop, shared-context retrieval — ships separately as the proprietary motir-ai service. It runs headless and is called server-to-server by motir-core. Browsers never talk to motir-ai directly, so the user experience stays unified (one app, one domain, one cookie) and the GPL boundary stays clean (a network service interface is not a derivative work).

See vision.html principle #19 and feasibility.html ADR-008 in the planning docs for the open-core architecture rationale. This split follows the same playbook as GitLab, Sentry, Plane, and Mattermost.

Rename interim: these repos are being renamed from their pre-rebrand prodect-* names to motir-core / motir-ai. GitHub redirects the old repo URLs automatically, so existing clones, remotes, and links keep working; update remotes with git remote set-url at leisure. (Vercel does NOT redirect — the *.vercel.app URLs below apply once the Vercel project rename lands.)

Stack

• Runtime: Node.js ≥22 (pnpm 11 requires it)
• Framework: Next.js 16 (App Router, React Server Components, Turbopack)
• Language: TypeScript (strict mode; noUncheckedIndexedAccess, noImplicitOverride, noFallthroughCasesInSwitch)
• Styling: Tailwind CSS v4
• Persistence: Postgres 18 with pgvector — production's major (local Docker; host port 5433 to coexist with other local Postgres instances) + Prisma 7 with @prisma/adapter-pg. Connection URL lives in prisma.config.ts (Prisma 7 split it out of schema.prisma).
• Auth: NextAuth / Better-Auth (lands in Story 1.1 — not yet present)
• Testing: Vitest unit + Playwright e2e (scaffolding lands in later Subtasks)
• Lint / format: ESLint 9 (flat config) + Prettier 3. Husky pre-commit hook runs lint-staged to auto-fix staged files on every commit.
• Package manager: pnpm (version pinned via packageManager in package.json; use corepack enable)
• Deploy: Vercel (lands in Subtask 1.0.5)
• CI: GitHub Actions — three parallel jobs (lint, typecheck, build) on every PR; build runs against a Postgres container started by the composite action

This Stack section is the authoritative reference for every later coding-agent prompt. Motir's planner (Epic 4) reads it verbatim into Subtask prompts so generated code matches the project's actual stack.

Local setup

Prerequisites: Node 22+, Docker or OrbStack, pnpm (corepack enable will handle this).

cp .env.example .env       # creates the dev DATABASE_URL
pnpm install               # installs deps + sets up husky pre-commit hook
./scripts/db-up.sh         # starts Postgres in Docker and applies migrations
pnpm dev                   # http://localhost:3000

You should see a placeholder "Motir" page on a dark theme — not the default create-next-app welcome page.

Coming from the PostgreSQL 16 dev database

The dev database runs PostgreSQL 18, production's major (MOTIR-10221). A 16 data directory cannot start under 18, so docker-compose.yml uses a new volume, prodect-pg18-data, and ./scripts/db-up.sh initialises it empty. Your old prodect-pg-data volume is left as it was. List it with:

docker volume ls --filter name=prodect-pg-data

Start fresh (recommended). Dev data is reproducible with pnpm db:seed / pnpm db:seed:large. Once you no longer need the old data, remove the old volume, using the name the command above printed:

docker volume rm motir-core_prodect-pg-data

Keep the data. Dump it while the 16 container still runs, before you pull this change (or check out an older commit and run docker compose up -d postgres there first):

docker exec prodect-postgres pg_dumpall -U prodect > prodect-pg16.sql

Then, on this change, start the empty 18 database, load the dump and finish the setup:

docker compose rm -sf postgres && docker compose up -d postgres

docker exec -i prodect-postgres psql -q -U prodect -d postgres < prodect-pg16.sql

./scripts/db-up.sh

The load reports role "prodect" already exists and database "prodect" already exists. Those are expected, because the container creates both at first boot.

This is the beginning of the README. Read the rest at the original. Read the full README ↗