lich

KO | EN

gitlite — search

#ai #large-language-models #macos #mysql #awesome #api #deep-learning #containers #computer-vision #openai

(★ 9)

Worktree isolated dev stacks for parallel coding agents.

파일 탐색기

ZIP 다운로드

- - worktree-verify.sh
  - worktree.sh
- - docs-deploy.yml
  - release-please.yml
  - release.yml
- - dogfood-example.md
  - framework-patterns.md
- - .gitignore
  - dashboard.md
  - index.md
  - package-lock.json
  - package.json
  - telemetry.md
  - troubleshooting.md
- audit-2026-05-26-spec-skill.md
- - .gitignore
  - _pool-manifest.ts
  - AUDIT.md
  - bun.lock
  - package.json
  - tsconfig.json
  - vitest.config.ts
  - vitest.workspace.ts
- - .gitignore
  - bunfig.toml
  - CLEANUP-HINTS.md
  - package.json
  - README.md
  - tsconfig.json
  - vitest.config.ts
- - pre-commit
- install-git-hooks.sh
- link-local.sh
- unlink-local.sh
- - SKILL.md
  - VERSION
- - SKILL.md
  - VERSION
.gitignore
.release-please-manifest.json
bun.lock
CHANGELOG.md
CLAUDE.md
install.sh
LICENSE
package.json
README.md
release-please-config.json
vitest.shared.ts

# CDN으로 사용하기

jsDelivr

jsDelivr는 공개 GitHub 리포지토리를 별도 설정 없이 CDN으로 즉시 서빙합니다. 버전과 파일을 고르면 웹페이지에 바로 붙일 수 있는 링크와 예시 코드가 만들어집니다.

버전

파일

링크

예시

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

Worktree-scoped dev stack orchestrator. Run as many dev stacks as you have worktrees.

https://github.com/user-attachments/assets/f173c9cc-18d5-4de1-8012-2f2a1e4b888f

**What it is**

A CLI that reads a `lich.yaml` file describing your stack (docker containers, host processes, env variables, lifecycle) and brings it up with per-worktree isolation. Run `lich up` in two worktrees, get two independent stacks running whatever code exists in those worktrees.

**Who it's for**

Developers who want to run parallel development stacks from multiple worktrees. Typically this is to enable workflows using multiple parallel coding agents.

## Why

Traditional local dev tooling is done ad hoc. It uses various tools: bash/npm scripts, procfiles, docker compose, etc. These systems generally can't run multiple copies of the same stack on one machine at the same time. Ports collide, container names conflict, memory leaks from zombie processes never cleaned up, agents get derailed running down bugs in tooling instead fixing actual problems. Lich implements a robust and observable system to manage this complexity.

## Install

```bash
curl -fsSL https://lich.sh/install.sh | bash
```

Or download a release tarball from [GitHub Releases](https://github.com/RPate97/lich/releases) and put `lich` on your PATH.

## Quickstart

The fastest way to see lich working is the [t3 starter](https://github.com/RPate97/lich-starter-t3). A [T3 Stack](https://create.t3.gg/) (Next.js + tRPC + Prisma + Postgres + Tailwind) preconfigured with a `lich.yaml`:

```bash
git clone https://github.com/RPate97/lich-starter-t3
cd lich-starter-t3
lich up
```

Postgres boots in a Docker container on a dynamically allocated port, `DATABASE_URL` is wired automatically, Prisma pushes the schema, Next.js starts. Open the URL lich prints and you have a working full-stack app.

### Run two stacks in parallel

Add a worktree and bring up a second stack from the same template:

```bash
git worktree add ../lich-starter-t3-feature -b feature
cd ../lich-starter-t3-feature
lich up
lich stacks
```

```
WORKTREE                       STATUS  UPTIME    SERVICES  URL
lich-starter-t3                up      00:02:15  2/2       http://web.lich-starter-t3.lich.localhost:3300/
lich-starter-t3-feature        up      00:00:08  2/2       http://web.lich-starter-t3-feature.lich.localhost:3300/
```

Two stacks. Two databases. Two dev servers. No port collisions. Same `lich.yaml`. Both URLs work independently in your browser.

Tear down both:
```bash
lich nuke
```

### Use lich in your own repo

To wire lich into an existing repo, install the `lich-instrument` skill and run it in your coding agent:

```bash
npx skills add https://github.com/RPate97/lich/skills/lich-instrument
```

```bash
/lich-instrument
```

The skill walks an agent through writing a `lich.yaml` for your stack. You may need to iterate a few times to get the env variable mapping and loading right; if you get stuck, the [lich.yaml reference](https://lich.sh/reference/lich-yaml-spec) is the place to look. Then it's the same workflow:

```bash
lich up                 # brings the stack up
lich logs               # tail logs
lich down               # stop it
```

## Minimal lich.yaml

```yaml
version: 1

services:
  postgres:
    image: postgres:16
    ports:
      - { container_port: 5432, published_env: POSTGRES_HOST_PORT }
    environment:
      POSTGRES_PASSWORD: dev

owned:
  api:
    cwd: apps/api
    cmd: pnpm dev
    port: { published_env: PORT }
    env:
      DATABASE_URL: "postgres://postgres:dev@localhost:${services.postgres.host_port}/app"
```

## Docs

Full docs at **[lich.sh](https://lich.sh)**. Entry points:

- [Getting started](https://lich.sh/)
- [lich.yaml reference](https://lich.sh/reference/lich-yaml-spec)
- [CLI reference](https://lich.sh/reference/cli)
- [Recipes](https://lich.sh/recipes/)
- [Worktree isolation](https://lich.sh/concepts/worktrees-isolation)
- [Troubleshooting](https://lich.sh/troubleshooting)

## Agent skills

Lich ships agent skills that let Claude (or other agents) work with lich effectively:

- [`lich`](skills/lich/): daily-driver on-ramp; understand the CLI surface and use it
- [`lich-instrument`](skills/lich-instrument/): guides an agent through writing a `lich.yaml` for your repo

Add a skill:

```bash
npx skills add https://github.com/RPate97/lich/skills/lich
npx skills add https://github.com/RPate97/lich/skills/lich-instrument
```

## Contributing

Setup:

```bash
git clone https://github.com/RPate97/lich
cd lich
bash scripts/install-git-hooks.sh
```

Build:

```bash
cd packages/lich && bun install && bun run build
```

Test:

```bash
cd packages/lich && bun test                                 # unit
cd packages/e2e && bun run test                              # end-to-end
```

The test suites disable telemetry automatically (set in `vitest.config.ts` and the e2e helper). For ad-hoc local runs of the lich binary while developing, set `LICH_TELEMETRY=0` in your shell so your dev usage doesn't show up in real-user analytics:

```bash
echo 'export LICH_TELEMETRY=0' >> ~/.zshrc  # or ~/.bashrc
```

## Telemetry

Lich collects anonymous CLI usage telemetry (command name, exit code, duration, version, platform). No paths, no `lich.yaml` contents, no env values, no log content. The `distinct_id` is a machine-stable SHA-256 hash of your home directory + hostname + platform (one-way, no reversal), cached at `~/.lich/installation-id`.

Disable:

```bash
export LICH_TELEMETRY=0                      # per-shell
echo '{"telemetry":false}' > ~/.lich/config.json  # per-user, persistent
```

Or in `lich.yaml`:

```yaml
runtime:
  telemetry: false
```

Full disclosure of what's collected, where it goes, and how to delete the per-installation ID: [lich.sh/telemetry](https://lich.sh/telemetry).

[Check the code.](https://github.com/RPate97/lich/blob/main/packages/lich/src/telemetry/client.ts#L44)

> If you can, please leave telemetry enabled.

## License

MIT.

lich

파일 탐색기

# CDN으로 사용하기

Was this content helpful?

Recent Feedback

Download README