Developing Tarsk

This guide covers running the Tarsk monorepo locally. End users should use Installation instead.

Prerequisites

Bun (pinned in the repo)
git on your PATH

Clone and Install

git clone https://github.com/damiant/tarsk.git
cd tarsk
bun install

Development Modes

Command	What it does
`bun run dev:web`	CLI server + app Vite dev with hot reload (recommended)
`cd cli && bun run dev`	Sync models, build app, start Electrobun desktop dev
`cd cli && bun run dev:web`	Debug API on port 462 + app Vite on 8100
`bun run dev:app`	Frontend only (port 8100; API calls go to 462)
`bun run dev:docs`	Documentation site (Astro)
`bun run dev:cli`	CLI server with built assets

When the app runs on Vite port 8100, API requests proxy to the debug server on 462.

Build

bun run build

Build order: shared → app → cli → postbuild (copies app/dist into the CLI public assets).

For npm publish without Electrobun native targets:

bun run build:npm

Quality Checks

bun run check:all

Runs lint, build, tests, and Vite Plus checks. bun run check:all now performs the signed desktop build path; use bun run check:all:unsigned when you need the full pipeline without codesigning or notarization, and bun run check:all:quiet for a one-line pass/fail summary.

Repository Layout

Directory	Purpose
`app/`	React frontend (Vite Plus)
`cli/`	Bun/Hono server, agent orchestration, Electrobun desktop shell
`shared/`	`@tarsk/shared` types, constants, utilities
`docs/`	This documentation site (Astro + Starlight)
`website/`	Marketing site
`mobile/`	Capacitor iOS/Android wrapper
`extensions/vscode/`	VS Code extension
`ai-data/`	Provider and model catalog data
`specs/`	Product specifications

Sync Model Data

bun run sync-models

Refreshes the model catalog in ai-data/. Full sync needs ARTIFICIAL_ANALYSIS_TOKEN.

VS Code Extension Development

cd extensions/vscode
bun install
bun run compile

In VS Code/Cursor, select Run Tarsk VS Code Extension and press F5.

AGENTS.md — contributor rules for agents
cli/README.md — published CLI reference