Devist

Project bootstrap CLI for AI-assisted development. Powered by Reso — a memory system that quietly learns your craft and aligns AI advice with your patterns over time.

A Rust CLI that lets you scaffold new projects from templates, run multiple project backends without overloading your machine, and stay on top of what's in your codebase — even when most of the code was written by AI.

Built by Webchemist.

Reso — the alignment layer

Reso is Devist's unified memory store. Every observation, decision, and preference accumulates here, classified by:

• scope — project (specific decisions), tech (stack patterns), user (your style)
• priority — constraint (always enforced), strong, preference, info
• tech tags — auto-detected from package.json, Cargo.toml, etc.

Over time, AI advice in any new project starts in tune with your past — no cold start, no repetition of resolved issues. Subtle. Persistent. Yours.

Backed by Supabase (canonical, with daily snapshots) + mem0 (semantic index, replaceable). Lose mem0, keep your memory.

Status: v0.1.0 beta. APIs and template manifest schema may change before v1.0.

Why

Two pains modern dev workflows hit hard:

1. Backend stack overload. One Supabase or Postgres docker stack per project melts your laptop. devist runs at most one backend at a time — switching projects auto-stops the previous one.
2. AI-assisted code blindness. When AI writes most of the code, you stop knowing how the system fits together. devist gives you brief, scan, explain, and watch to keep your mental model intact.

Install

Homebrew (macOS / Linux)

brew install WebchemistCorp/devist/devist

crates.io (any platform with Rust toolchain)

cargo install devist

From source

git clone https://github.com/WebchemistCorp/devist
cd devist
cargo install --path .

Manual binary download

Grab the archive for your platform from the Releases page and extract devist somewhere on your PATH.

macOS: "확인되지 않은 개발자" / "unidentified developer" warning

Devist binaries shipped via Homebrew or the GitHub Releases page are not yet code-signed with an Apple Developer ID (paid program — on the roadmap). macOS Gatekeeper will block them on first launch with an "unidentified developer" dialog.

Two ways around it:

# Option 1 — strip the quarantine attribute (one-shot)
xattr -d com.apple.quarantine "$(which devist)"

# Option 2 — first-launch override
# Right-click the binary in Finder → "Open" → "Open anyway"

This warning does not appear when you install via cargo install (builds locally) or cargo install --path . (builds from source).

Quick Start

devist setup
devist template add https://github.com/WebchemistCorp/devist-templates
devist init my-app --template=react-supabase
devist start my-app --dev

Command Reference

Project lifecycle

Templates

Worker (background observer)

A long-running daemon watches a parent folder of projects, records every file event into a local SQLite store (L1), pushes batches to your Supabase project (L2), and — when configured — generates AI advice via the claude CLI with long-term semantic memory in mem0.

State lives in ~/.devist/worker/:

worker.db    SQLite event log (L1 store)
config.toml  Worker config
rules.md     Global rules (injected into Claude prompt)
worker.pid   Daemon PID
worker.log   Daemon stdout/stderr

Supabase L2 setup

Apply the migration once on your Supabase project:

psql "$SUPABASE_DB_URL" -f migrations/0001_worker_events.sql
# or paste the file into the Supabase SQL editor

Then point the worker at it:

devist worker config set supabase_url   https://xxxx.supabase.co
devist worker config set supabase_key   <service-role-key>
devist worker config set client_id      $(hostname)   # idempotency key
devist worker stop && devist worker start

The daemon batch-flushes pending events every sync_interval_secs (30s default). Re-pushes are idempotent on (client_id, client_event_id).

Rules

Two layers, both optional plain markdown:

~/.devist/worker/rules.md                          # global
<monitor>/<project>/.devist/rules.md               # project (overrides)

Both are concatenated into the advice prompt verbatim. Use them to set tone, focus areas, and what should/shouldn't be persisted to mem0.

Advice rate limits (config keys)

Layout

~/.devist/
├── config.toml       Your settings
├── registry.toml     Projects you've created
├── state.toml        Currently active backend
├── templates/        Cloned template repos
├── worker/           Background worker state (db, pid, log, config)
└── cache/            Reserved

Templates

A template is a directory with a devist.toml manifest plus any project files. Files ending in .tmpl get variable substitution; everything else is copied as-is (binary-safe).

Minimal devist.toml:

[meta]
name = "my-stack"
version = "0.1.0"
description = "Short description"
author = "You"
tags = ["fullstack"]

[variables]
project_name = { default = "{{folder_name}}" }
description = { default = "A new project" }

[stack]
type = "supabase"   # or "docker-compose", "none"

[commands]
install = "pnpm install"
dev = "pnpm dev"
backend_start = "supabase start"
backend_stop = "supabase stop"
test = "pnpm test"

Variables are substituted in *.tmpl files with {{ name }} syntax. Auto-provided: project_name, folder_name. Override with --var key=value.

A single git repo can host multiple templates as subdirectories. The official WebchemistCorp/devist-templates repo is structured this way.

Development

cargo build
cargo test
cargo run -- --help

Required: Rust 1.70+, git. For most templates: docker, node, pnpm, supabase CLI.

Status

Active development. Phases:

Currently at end of Phase 4.

License

MIT