kodingo-cli

Purpose

This repository contains the Kodingo command-line interface.

The CLI acts as a local adapter between a developer’s environment and the Kodingo core engine.

It is responsible for observing, normalizing, and forwarding signals — not interpreting them.

What This Repo Owns

• CLI commands and UX
• Local project initialization
• Project scoping and isolation
• Authentication and authorization flow
• Event emission to kodingo-core
• Local configuration and credentials

What This Repo Does NOT Do

• No decision inference
• No memory interpretation
• No confidence calculation
• No domain logic

Design Constraints

• The CLI must be safe to run locally
• It must never leak data across projects
• It must respect paid vs unpaid project boundaries
• All intelligence lives elsewhere

Dependencies

• Depends on kodingo-core
• Depends on kodingo-schema

Security Model

• Projects are explicitly initialized
• Access is opt-in per project
• Local identity is scoped per project directory

Status

Interface design phase.

Local DB Setup

1) Run Postgres locally

Use Docker:

docker run --name kodingo-postgres -e POSTGRES_PASSWORD=postgres -e POSTGRES_DB=kodingo -p 5432:5432 -d postgres:16

Ensure psql is available in your PATH (it ships with Postgres client tools).

2) Configure environment

Create a .env file (or export in shell):

export DATABASE_URL=postgres://postgres:postgres@localhost:5432/kodingo

3) Build and run the CLI

npm ci
npm run build
node src/cli.js capture --type decision --title "Chosen DB" --content "We chose Postgres for persistence." --tags "architecture,db"
node src/cli.js query-memory "Postgres" --limit 5