open-index/open-npm huggingface dataset:
npm package: @openlap/openlap
Description: Local MCP proxy for openlap.app -- auto-save, live feeds, project detection, one install
Latest version: 1.24.0

# openlap

Product requirements that agents read. Write a lap, agent builds it.

A lap is one goal, issues to implement, and verification criteria. Agents pick the next open lap and work through it. When they commit, criteria auto-check via webhook. No dashboard, no CLI -- just the MCP server.

Live at [openlap.app](https://openlap.app)

## Install

1. Admin installs the GitHub App (once per org): https://github.com/apps/openlap-app/installations/new
2. Add the MCP server:

```bash
claude mcp add --transport http lap https://openlap.app/mcp
```

3. Open Claude Code. First message triggers GitHub login in browser. Done.

For project-scoped briefings (filters context to one repo):

```bash
claude mcp add --transport http --scope project lap "https://openlap.app/mcp?project=owner/repo"
```

Project scope overrides global when both exist.

4. Register your repo as a project (once per repo):

```
create_project owner/repo
```

## What agents see

**Briefings** -- computed context injected into tool descriptions. Agents see project health, the focused lap's unchecked criteria, staleness signals, and priority collisions without calling any tool. Briefings refresh mid-session after mutations.

**Laps** -- sorted by priority (0=focus, 1=urgent, 2=high, 3=normal). Agents work on the first open lap. Each lap has a goal, body, and structured criteria.

**Criteria** -- verification checks on each lap. Agents prove work by committing with `LAP-NNN #N` in the commit message:

```bash
git commit -m "LAP-010 #1 #2 add auth middleware"
```

The GitHub webhook auto-checks the referenced criteria. When all code criteria pass, the lap auto-closes to done. If manual criteria remain (screenshots, design review), the lap moves to review for human verification.

**Focus mode** -- set priority=0 on one lap per project. Its unchecked criteria appear in briefings automatically, so agents know what to verify from `tools/list` alone.

## Develop

Prerequisites: Go 1.23+, a GitHub App.

```bash
export BASE_URL=http://localhost:7784
export DB_PATH=./openlap.db
cd cmd/anylap && go run .
```

Local MCP (overrides the remote server):

```bash
claude mcp add --transport http lap http://localhost:7784/mcp
```

## Deploy

Hetzner. `sky ship --app openlap-1`. Secrets via `sky deploy --app openlap-1`.

## Architecture

```
Agent -> MCP (openlap.app/mcp) -> SQLite
```

One Go binary serves REST API + MCP protocol. OAuth 2.1 with PKCE, chaining to GitHub for identity. GitHub App installation = team boundary. SQLite with Litestream S3 backup.

See CLAUDE.md for technical reference.
npm package: @openlaw/snapshot-js-erc712
Description: Implementation of ERC-712 structure signatures.
Author: OpenLaw Dev Team
Latest version: 1.8.1

## Deployment

1. Checkout `master` and pull the latest
2. Locally run `npm run release`
3. Choose a new semver version number
4. **In the background the following will now happen**:
    1. the `package.json` version will be bumped
    2. a new Git tag created
    3. version bump and tag pushed to `master`
    4. `prod-release.yaml` will execute (due to package bump) to publish the new package version to the NPM registry
    5. GitHub Release page will open

5. Create a GitHub Release entry (opens in brower automatically)
6. Done!