### Setup Engram Beta Repository

Source: https://github.com/gentleman-programming/engram/blob/main/README.md

Clones the Engram beta repository, checks out the specific branch, starts Docker, builds the Engram binary, and sets up isolated environment variables for testing new memory-conflict-surfacing features.

```bash
git clone https://github.com/Gentleman-Programming/engram.git engram-beta-repo
cd engram-beta-repo && git checkout feat/memory-conflict-surfacing-cloud-sync
docker compose -f docker-compose.beta.yml up -d
go build -o ./engram-beta ./cmd/engram

# Isolated env (does NOT touch ~/.engram or your prod cloud)
export ENGRAM_DATA_DIR=/tmp/engram-beta-data
export ENGRAM_CLOUD_SERVER=http://127.0.0.1:28080
export ENGRAM_CLOUD_TOKEN=beta-token-CHANGE-ME-please-32chars
mkdir -p "$ENGRAM_DATA_DIR"
```

--------------------------------

### Install engram-beta from source

Source: https://github.com/gentleman-programming/engram/blob/main/docs/beta/obsidian-brain.md

Installs the beta version using the Go toolchain.

```bash
go install github.com/Gentleman-Programming/engram/cmd/engram@v1.12.0-beta.1
mv ~/go/bin/engram ~/go/bin/engram-beta
engram-beta version
```

--------------------------------

### Setup Local Engram Cloud with Docker Compose

Source: https://github.com/gentleman-programming/engram/blob/main/docs/engram-cloud/README.md

Use this command to quickly set up a local Engram Cloud environment using Docker Compose. It starts the cloud service and configures the local CLI server URL. Ensure you have Docker and Docker Compose installed.

```bash
docker compose -f docker-compose.cloud.yml up -d
engram cloud config --server http://127.0.0.1:18080
engram cloud enroll smoke-project
engram sync --cloud --project smoke-project
```

--------------------------------

### Install engram-beta on Linux

Source: https://github.com/gentleman-programming/engram/blob/main/docs/beta/obsidian-brain.md

Downloads and installs the beta binary for Linux systems.

```bash
curl -L https://github.com/Gentleman-Programming/engram/releases/download/v1.12.0-beta.1/engram_1.12.0-beta.1_linux_amd64.tar.gz -o /tmp/engram-beta.tar.gz
tar -xzf /tmp/engram-beta.tar.gz -C /tmp
sudo mv /tmp/engram /usr/local/bin/engram-beta
sudo chmod +x /usr/local/bin/engram-beta
engram-beta version
```

--------------------------------

### Absolute Directory Examples

Source: https://github.com/gentleman-programming/engram/blob/main/docs/engram-cloud/troubleshooting.md

Examples of correctly formatted absolute paths for the directory argument. Avoid relative paths.

```text
/home/user/work/sias-app
```

```text
/Users/user/work/sias-app
```

```text
C:/Users/user/work/sias-app
```

--------------------------------

### Install Engram via Go Install (Windows)

Source: https://github.com/gentleman-programming/engram/blob/main/docs/INSTALLATION.md

Recommended for technical users on Windows with Go installed. Compiles the binary locally.

```powershell
go install github.com/Gentleman-Programming/engram/cmd/engram@latest
# Binary goes to %GOPATH%\bin\engram.exe (typically %USERPROFILE%\go\bin\)
```

--------------------------------

### Example failure message for templ file size check

Source: https://github.com/gentleman-programming/engram/blob/main/openspec/changes/cloud-dashboard-visual-parity/design.md

Provides an example of the explicit failure message shown to contributors when generated Go files are too small, guiding them on how to fix the issue.

```text
components_templ.go size = 1234 bytes; expected >= 100000 bytes.
Possible cause: the *.templ sources changed but the generated *_templ.go files
were not committed. Run `make templ` (or `go tool templ generate ./internal/cloud/dashboard/...`)
and commit the regenerated files.
```

--------------------------------

### Manual Pi Agent Setup

Source: https://github.com/gentleman-programming/engram/blob/main/docs/AGENT-SETUP.md

Manually installs the necessary packages for Engram integration with the Pi agent and initializes the Engram MCP configuration.

```bash
pi install npm:gentle-engram@0.1.5
pi install npm:pi-mcp-adapter
pi-engram init
```

--------------------------------

### Execute Installer Build and Test Commands

Source: https://github.com/gentleman-programming/engram/blob/main/skills/gentleman-bubbletea/SKILL.md

Provides shell commands for building the installer binary and executing TUI-related test suites.

```bash
cd installer && go build ./cmd/gentleman-installer  # Build installer
cd installer && go test ./internal/tui/...          # Run TUI tests
cd installer && go test -run TestNewFeature         # Run specific test
```

--------------------------------

### Install engram-beta on macOS (Apple Silicon)

Source: https://github.com/gentleman-programming/engram/blob/main/docs/beta/obsidian-brain.md

Downloads and installs the beta binary for Apple Silicon systems.

```bash
curl -L https://github.com/Gentleman-Programming/engram/releases/download/v1.12.0-beta.1/engram_1.12.0-beta.1_darwin_arm64.tar.gz -o /tmp/engram-beta.tar.gz
tar -xzf /tmp/engram-beta.tar.gz -C /tmp
sudo mv /tmp/engram /usr/local/bin/engram-beta
sudo chmod +x /usr/local/bin/engram-beta
engram-beta version
```

--------------------------------

### Install and Use npq for npm Dependency Inspection

Source: https://github.com/gentleman-programming/engram/blob/main/CONTRIBUTING.md

Install the `npq` tool globally once. Then, use `npq install` to add new npm dependencies, which performs pre-flight checks for security and typosquatting.

```bash
npm i -g npq
```

```bash
npq install <package>
```

--------------------------------

### Install engram-beta on macOS (Intel)

Source: https://github.com/gentleman-programming/engram/blob/main/docs/beta/obsidian-brain.md

Downloads and installs the beta binary for Intel-based macOS systems.

```bash
curl -L https://github.com/Gentleman-Programming/engram/releases/download/v1.12.0-beta.1/engram_1.12.0-beta.1_darwin_amd64.tar.gz -o /tmp/engram-beta.tar.gz
tar -xzf /tmp/engram-beta.tar.gz -C /tmp
sudo mv /tmp/engram /usr/local/bin/engram-beta
sudo chmod +x /usr/local/bin/engram-beta
engram-beta version
```

--------------------------------

### Start Isolated Engram Beta Cloud

Source: https://github.com/gentleman-programming/engram/blob/main/docs/BETA_TESTING.md

Start the isolated Engram beta cloud services using Docker Compose. This setup uses non-default ports and volumes to ensure no interference with production.

```bash
docker compose -f docker-compose.beta.yml up -d
```

--------------------------------

### List Command Output Example

Source: https://github.com/gentleman-programming/engram/blob/main/openspec/changes/memory-conflict-audit/design.md

Example of the formatted output for the 'list' command, showing aligned columns for relation ID, type, status, creation time, and source/target information.

```text
RELATION_ID  TYPE             STATUS    CREATED              SOURCE → TARGET
─────────────────────────────────────────────────────────────────────────────
42           conflicts_with   pending   2026-04-26 14:21:03  alpha … → beta …
43           supersedes       judged    2026-04-26 14:18:11  beta  … → gamma…
```

--------------------------------

### Engram CLI: obsidian-export Examples

Source: https://github.com/gentleman-programming/engram/blob/main/docs/beta/obsidian-brain.md

Practical examples demonstrating various use cases of the `engram-beta obsidian-export` command, from basic exports to advanced configurations like auto-sync and graph management.

```bash
# Single export of everything
engram-beta obsidian-export --vault ~/Obsidian/engram

# Export only the engram project
engram-beta obsidian-export --vault ~/Obsidian/engram --project engram

# Force a complete re-export (useful after pruning observations)
engram-beta obsidian-export --vault ~/Obsidian/engram --force

# Auto-sync every 10 minutes (default), runs forever
engram-beta obsidian-export --vault ~/Obsidian/engram --watch

# Auto-sync every 5 minutes, only the engram project
engram-beta obsidian-export --vault ~/Obsidian/engram --watch --interval 5m --project engram

# Reset the graph layout to the engram-brain default
engram-beta obsidian-export --vault ~/Obsidian/engram --graph-config force

# Never touch the graph config (you have your own custom layout)
engram-beta obsidian-export --vault ~/Obsidian/engram --graph-config skip

```

--------------------------------

### Conventional Commit Examples

Source: https://github.com/gentleman-programming/engram/blob/main/CONTRIBUTING.md

Examples demonstrating various conventional commit types and structures, including breaking changes.

```text
feat(cli): add --json flag to session list command

```

```text
fix(store): prevent duplicate observation insert on retry

```

```text
docs(contributing): add label system documentation

```

```text
refactor(internal): extract search query sanitizer

```

```text
chore(deps): bump github.com/charmbracelet/bubbletea to v0.26

```

```text
fix!: change session ID format (breaking change)
BREAKING CHANGE: session IDs are now UUIDs instead of integers
```

--------------------------------

### CLI List Pagination Footer Example

Source: https://github.com/gentleman-programming/engram/blob/main/openspec/changes/memory-conflict-audit/design.md

Example of a footer message displayed by the CLI when the number of results shown is less than the total available.

```text
showing 50 of 80; use --limit or query HTTP /conflicts for full pagination
```

--------------------------------

### Install Engram Claude Plugin

Source: https://github.com/gentleman-programming/engram/blob/main/docs/AGENT-SETUP.md

Installs the Engram plugin for Claude Code from the marketplace and then installs it.

```bash
claude plugin marketplace add Gentleman-Programming/engram && claude plugin install engram
```

--------------------------------

### Valid Branch Name Examples

Source: https://github.com/gentleman-programming/engram/blob/main/skills/commit-hygiene/SKILL.md

Provides examples of correctly formatted branch names that adhere to the `type/description` convention.

```text
feat/json-export-command
fix/duplicate-observation-insert
docs/api-reference-update
refactor/extract-query-sanitizer
chore/bump-bubbletea-v0.26
ci/split-e2e-job
```

--------------------------------

### Stats Command Output Example

Source: https://github.com/gentleman-programming/engram/blob/main/openspec/changes/memory-conflict-audit/design.md

Example of the formatted output for the 'stats' command, using a label-colon style to display project statistics, including relation counts by type and deferred/dead counts.

```text
project:   alpha
relations: 12 (pending=5, judged=7)
  by relation_type:
    conflicts_with:   8
    supersedes:       3
    related:          1
deferred:  4
dead:      1
```

--------------------------------

### Install OpenCode Plugin

Source: https://github.com/gentleman-programming/engram/blob/main/docs/PLUGINS.md

Install the OpenCode plugin using the engram CLI. This plugin enhances session management for OpenCode users.

```bash
engram setup opencode
```

--------------------------------

### Start Engram Local Server

Source: https://github.com/gentleman-programming/engram/blob/main/docs/BETA_TESTING.md

Start the local Engram server to access the HTTP API. Ensure exported environment variables from previous steps are active.

```bash
./engram-beta serve
```

--------------------------------

### Example .env File for Engram Cloud Deployment

Source: https://github.com/gentleman-programming/engram/blob/main/docs/engram-cloud/quickstart.md

An example environment file (.env) for configuring Engram Cloud when deploying on a VPS using Docker Compose. It includes essential runtime variables and secrets.

```dotenv
POSTGRES_USER=engram
POSTGRES_PASSWORD=replace-with-strong-postgres-password
POSTGRES_DB=engram_cloud

ENGRAM_DATABASE_URL=postgres://engram:replace-with-strong-postgres-password@postgres:5432/engram_cloud?sslmode=disable
ENGRAM_CLOUD_TOKEN=replace-with-long-random-bearer-token
ENGRAM_CLOUD_ADMIN=replace-with-separate-admin-token
ENGRAM_JWT_SECRET=replace-with-32+-byte-random-secret
ENGRAM_CLOUD_ALLOWED_PROJECTS=engram,gentle-ai
ENGRAM_CLOUD_HOST=0.0.0.0
ENGRAM_PORT=18080
```

--------------------------------

### HTTP GET Request for Pulling Mutations

Source: https://github.com/gentleman-programming/engram/blob/main/openspec/changes/cloud-autosync-restoration/design.md

Example of a GET request to the /sync/mutations/pull endpoint, specifying the sequence number to pull from and a limit for the number of mutations.

```json
// GET /sync/mutations/pull?since_seq=41&limit=100
```

--------------------------------

### Example HTTP Request for Browser Observations

Source: https://github.com/gentleman-programming/engram/blob/main/openspec/changes/cloud-dashboard-visual-parity/design.md

An example of an HTTP GET request to retrieve browser observations, specifying project, type, limit, and cursor for pagination.

```HTTP
GET /dashboard/browser/observations?project=engram&type=bugfix&limit=20&cursor=40
```

--------------------------------

### HTTP GET Response for Pulling Mutations

Source: https://github.com/gentleman-programming/engram/blob/main/openspec/changes/cloud-autosync-restoration/design.md

Example of a successful 200 OK response from the GET /sync/mutations/pull endpoint, containing a list of mutations and a flag indicating if more are available.

```json
// → 200 {"mutations":[{"seq":42,"entity":"observation","entity_key":"...","op":"upsert","payload":{...},"occurred_at":"..."}],"has_more":false}
```

--------------------------------

### Configure Engram Cloud Client and Enroll Project

Source: https://github.com/gentleman-programming/engram/blob/main/docs/engram-cloud/quickstart.md

After starting the server, configure the client to connect to the server endpoint and set the cloud token. Then, enroll your project and initiate a cloud sync. This sequence ensures the client can communicate with the server and synchronize data.

```bash
engram cloud config --server http://127.0.0.1:8080
export ENGRAM_CLOUD_TOKEN="your-token"
engram cloud enroll my-project
engram sync --cloud --project my-project
```

--------------------------------

### Get Recent Session Context with GET /context

Source: https://context7.com/gentleman-programming/engram/llms.txt

Retrieve formatted context from recent sessions for a specific project. This is used by agents at session start to recover prior state. Supports filtering by scope.

```bash
curl -s "http://127.0.0.1:7437/context?project=my-app" | jq
```

```bash
# With scope filter
curl -s "http://127.0.0.1:7437/context?project=my-app&scope=project" | jq
```

--------------------------------

### Link Agent Skills to Project Local Directories

Source: https://github.com/gentleman-programming/engram/blob/main/CONTRIBUTING.md

Execute the setup script to link repository skills located in 'skills/' to the project-local directories for various agent environments.

```bash
./setup.sh
```

--------------------------------

### Setup Engram for Codex Agent

Source: https://github.com/gentleman-programming/engram/blob/main/README.md

This command sets up Engram for the Codex agent. Verify Codex is properly installed and accessible.

```bash
engram setup codex
```

--------------------------------

### GET /context

Source: https://context7.com/gentleman-programming/engram/llms.txt

Returns formatted context from recent sessions for a project. Used by agents at session start to recover prior state.

```APIDOC
## GET /context — Recent Session Context

### Description
Returns formatted context from recent sessions for a project. Used by agents at session start to recover prior state.

### Method
GET

### Endpoint
/context

### Query Parameters
- **project** (string) - Required - The project to retrieve context for.
- **scope** (string) - Optional - Filter context by scope.

### Response
#### Success Response (200)
- (Response structure not explicitly defined in source, but implies contextual data)
```

--------------------------------

### Run Cloud Backend API and Dashboard

Source: https://github.com/gentleman-programming/engram/blob/main/DOCS.md

Start the cloud backend API and dashboard. This command uses the Postgres configuration from the environment variables.

```bash
engram cloud serve
```

--------------------------------

### Setup Engram for Gemini CLI Agent

Source: https://github.com/gentleman-programming/engram/blob/main/README.md

This command sets up Engram for the Gemini CLI agent. Ensure the Gemini CLI is installed and configured.

```bash
engram setup gemini-cli
```

--------------------------------

### Run Go Build

Source: https://github.com/gentleman-programming/engram/blob/main/openspec/changes/cloud-dashboard-visual-parity/verify-report.md

Execute the build command for all Go packages in the project.

```bash
go build ./...
```

--------------------------------

### Engram Obsidian Export CLI Command

Source: https://github.com/gentleman-programming/engram/blob/main/openspec/specs/obsidian-export/spec.md

Example of the `engram obsidian-export` command with all optional flags provided. Use this to filter exports by project, limit the number of observations, and specify a start date.

```bash
engram obsidian-export --vault ~/vault --project eng --limit 100 --since 2026-01-01
```

--------------------------------

### Documentation update for AGENT-SETUP.md

Source: https://github.com/gentleman-programming/engram/blob/main/openspec/changes/memory-conflict-surfacing-cloud-sync/tasks.md

Notes any user-visible behavior changes in AGENT-SETUP.md related to Phase 2 deferrals. This includes the updated annotation format with titles and the introduction of new '/sync/status' fields.

```markdown
## Synchronization Status

Synchronization status is now more detailed. The `/sync/status` endpoint provides `deferred_count` and `dead_count` to indicate the number of items currently deferred or marked as dead due to repeated application failures.

## Annotation Format

Users interacting with annotations should be aware that relation annotations, such as conflicts and supersedes, now include enriched title information where available, e.g., `conflicts: #456 (Another Title)`.
```

--------------------------------

### Run Go Tests and Coverage

Source: https://github.com/gentleman-programming/engram/blob/main/skills/testing-coverage/SKILL.md

Execute these commands to run all tests and generate coverage reports for the project.

```bash
go test ./...
go test -cover ./...
```

--------------------------------

### Install Claude Code Plugin via Engram CLI

Source: https://github.com/gentleman-programming/engram/blob/main/docs/PLUGINS.md

Install the Claude Code plugin using the engram CLI. This method is an alternative to the marketplace installation.

```bash
engram setup claude-code
```

--------------------------------

### Verify Engram Installation

Source: https://context7.com/gentleman-programming/engram/llms.txt

Checks the installed Engram version.

```bash
engram version
```

--------------------------------

### Docker Compose Cloud Setup and Teardown

Source: https://github.com/gentleman-programming/engram/blob/main/openspec/changes/integrate-engram-cloud/verify-report.md

Manage the cloud environment using Docker Compose. This includes bringing services up, down, and checking their status.

```bash
docker compose -f "docker-compose.cloud.yml" down --remove-orphans
docker compose -f "docker-compose.cloud.yml" up -d postgres
docker compose -f "docker-compose.cloud.yml" up -d --build cloud
docker compose -f "docker-compose.cloud.yml" ps
```

--------------------------------

### Install Engram via Homebrew

Source: https://context7.com/gentleman-programming/engram/llms.txt

Installs Engram on macOS using the Homebrew package manager.

```bash
# macOS (Homebrew)
brew install gentleman-programming/tap/engram
```

--------------------------------

### Local Cloud Bring-Up with Docker Compose

Source: https://github.com/gentleman-programming/engram/blob/main/DOCS.md

Steps to set up a local Engram cloud environment using Docker Compose. This includes server-side requirements and client-side CLI configuration.

```bash
# 1) SERVER-SIDE startup requirements (configure before startup)
# docker-compose.cloud.yml includes defaults for browser-demo smoke usage:
# ENGRAM_CLOUD_INSECURE_NO_AUTH=1
# ENGRAM_CLOUD_ALLOWED_PROJECTS=smoke-project
docker compose -f docker-compose.cloud.yml up -d
```

```bash
# source-run flow (without compose): set BOTH token + allowlist before startup
# ENGRAM_DATABASE_URL="postgres://engram:engram_dev@127.0.0.1:5433/engram_cloud?sslmode=disable" \
# ENGRAM_JWT_SECRET="replace-with-32+-byte-random-secret" \
# ENGRAM_CLOUD_TOKEN="your-token" \
# ENGRAM_CLOUD_ALLOWED_PROJECTS="my-project" \
# engram cloud serve
```

```bash
# 2) CLIENT-SIDE CLI setup
# compose runtime flow: published :18080
engram cloud config --server http://127.0.0.1:18080
# compose runtime default is insecure local-dev mode; keep token unset
# client sync preflight only requires the configured cloud server URL; no
# client-side ENGRAM_CLOUD_INSECURE_NO_AUTH flag is required for compose flow
unset ENGRAM_CLOUD_TOKEN
```

```bash
# 3) Enroll project + run explicit cloud sync
engram cloud enroll smoke-project
engram cloud upgrade doctor --project smoke-project
engram cloud upgrade repair --project smoke-project --dry-run
engram cloud upgrade repair --project smoke-project --apply
engram cloud upgrade bootstrap --project smoke-project --resume
engram cloud upgrade status --project smoke-project
engram sync --cloud --status --project smoke-project
```

```bash
# source-run client endpoint (without compose): default :8080
# engram cloud config --server http://127.0.0.1:8080
```

```bash
# cloud mode enforces a single explicit project scope
# engram sync --cloud --all  # blocked by design
```

--------------------------------

### Get Full Observation Content with mem_get_observation

Source: https://github.com/gentleman-programming/engram/blob/main/DOCS.md

Get the full untruncated content of a specific observation by ID.

```text
Get full untruncated content of a specific observation by ID.
```

--------------------------------

### Build Command Output

Source: https://github.com/gentleman-programming/engram/blob/main/openspec/changes/memory-conflict-semantic/verify-report.md

Result of the 'go build ./...' command, indicating a clean build.

```bash
go build ./...   → exit 0 (clean)
```

--------------------------------

### Backup and Restore with GET /export and POST /import

Source: https://context7.com/gentleman-programming/engram/llms.txt

Export all data as JSON for backup, migration, or sharing. Import merges data using INSERT OR IGNORE per session, skipping duplicates.

```bash
# Export all data
curl -s http://127.0.0.1:7437/export > engram-backup.json
```

```bash
# Export project-scoped
curl -s "http://127.0.0.1:7437/export?project=my-app" > my-app-backup.json
```

```bash
# Import (merges with existing, skips duplicates)
curl -s -X POST http://127.0.0.1:7437/import \
  -H "Content-Type: application/json" \
  -d @engram-backup.json | jq
```

--------------------------------

### Install Engram via Homebrew

Source: https://github.com/gentleman-programming/engram/blob/main/docs/INSTALLATION.md

Use this command to install the latest version of Engram on macOS or Linux using Homebrew.

```bash
brew install gentleman-programming/tap/engram
```

--------------------------------

### Bootstrap Cloud Upgrade

Source: https://github.com/gentleman-programming/engram/blob/main/DOCS.md

Initiate a resumable, checkpointed flow for enrolling, pushing, and verifying cloud upgrades. Use the `--resume` flag to continue a previous operation.

```bash
engram cloud upgrade bootstrap --project <project> [--resume]
```

--------------------------------

### Invalid Branch Name Examples

Source: https://github.com/gentleman-programming/engram/blob/main/skills/commit-hygiene/SKILL.md

Shows examples of branch names that do not conform to the required `type/description` format and would be rejected.

```text
feature/add-login                ← "feature" not allowed, use "feat"
fix/Add-Login                    ← uppercase not allowed
my-branch                        ← no type prefix
fix_something                    ← missing "/" separator
```

--------------------------------

### Manage Cloud Replication with `engram cloud`

Source: https://context7.com/gentleman-programming/engram/llms.txt

Opt-in cloud replication management. Configure server, enroll projects, check status, perform upgrade workflows, and serve the cloud backend.

```bash
engram cloud config --server http://127.0.0.1:18080
```

```bash
engram cloud enroll my-app
```

```bash
engram cloud status
```

```bash
engram cloud upgrade doctor --project my-app
```

```bash
engram cloud upgrade repair --project my-app --dry-run
```

```bash
engram cloud upgrade repair --project my-app --apply
```

```bash
engram cloud upgrade bootstrap --project my-app
```

```bash
engram cloud upgrade status --project my-app
```

```bash
ENGRAM_DATABASE_URL='postgres://engram:pass@localhost:5432/engram_cloud?sslmode=disable' \
ENGRAM_JWT_SECRET='replace-with-32-byte-random-secret' \
ENGRAM_CLOUD_TOKEN='your-bearer-token' \
ENGRAM_CLOUD_ALLOWED_PROJECTS='my-app,other-project' \
ENGRAM_CLOUD_HOST='0.0.0.0' \
engram cloud serve
```

```bash
docker compose -f docker-compose.cloud.yml up -d
engram cloud config --server http://127.0.0.1:18080
engram cloud enroll smoke-project
engram sync --cloud --project smoke-project
```

--------------------------------

### Synchronize Relations Across Machines via Cloud

Source: https://github.com/gentleman-programming/engram/blob/main/README.md

Enroll your project in the cloud and sync relations. This demonstrates setting up Engram on a second machine to access synced memories.

```bash
./engram-beta cloud enroll beta-test
./engram-beta sync --cloud --project beta-test
./engram-beta cloud status

# Simulate a "second machine"
ENGRAM_DATA_DIR=/tmp/engram-beta-data-2 ./engram-beta cloud enroll beta-test
ENGRAM_DATA_DIR=/tmp/engram-beta-data-2 ./engram-beta sync --cloud --project beta-test
ENGRAM_DATA_DIR=/tmp/engram-beta-data-2 ./engram-beta search "Architecture"
```

--------------------------------

### Run All Tests for Command-Line and Cloud Components

Source: https://github.com/gentleman-programming/engram/blob/main/openspec/changes/cloud-upgrade-path-existing-users/apply-progress.md

Execute all tests for the command-line interface and cloud-related components. This provides a comprehensive check of the integrated system.

```go
go test ./cmd/engram ./internal/sync ./internal/cloud/autosync
```

--------------------------------

### Invalid Conventional Commit Examples

Source: https://github.com/gentleman-programming/engram/blob/main/skills/commit-hygiene/SKILL.md

Shows examples of commit messages that violate the Conventional Commits standard and would be rejected by the GitHub ruleset.

```text
Fix bug                          ← no type prefix
feat: Add login                  ← description should be lowercase
FEAT(cli): add flag              ← type must be lowercase
feat (cli): add flag             ← no space before scope
feat(CLI): add flag              ← scope must be lowercase
update docs                      ← no conventional commit format
```