# Install Proomptal

Linux x86-64 with glibc. Bun is required; the package was exercised with Bun1.4.2. Get Bun from [its official installation guide](https://bun.sh/docs/installation). This local app uses a private SQLite store and ports127.0.0.1:34801/34802.

[Download the local app](/downloads/proomptal-linux-x64-glibc.tar.gz) · [SHA256](/downloads/proomptal-linux-x64-glibc.tar.gz.sha256)

SHA256: `2b8148866df104d9ecc63e4276763dc6e749e4884e85f00d5c73b1f5247acc91`
Source commit: `6428f4d73d3f66644e06948ad02f04e3e1736a55`; source tree: `4a909a06f2e9aec68f5f2d5ec090a8de3b5a1f6c`.

Download both files to the same directory, then:

```bash
sha256sum --check proomptal-linux-x64-glibc.tar.gz.sha256
tar -xzf proomptal-linux-x64-glibc.tar.gz
cd proomptal
bun runtime/launcher.ts init --data-dir /absolute/private-data
bun runtime/launcher.ts check --data-dir /absolute/private-data
bun runtime/launcher.ts serve --data-dir /absolute/private-data --project /absolute/project
```

Choose real absolute paths. Open http://127.0.0.1:34802. Save a template, fill its variables, then Copy or Install. Both the web and CLI share your selected store. Repeating init preserves a compatible database. Keep the ports local on your own machine.

When upgrading an existing store, stop the app and back up its complete private data directory. Run `bun runtime/launcher.ts migrate --data-dir /absolute/path/to/private-data` before `check` or `serve`. The explicit migration preserves current prompts and collections, recording only their current snapshots as a history baseline. Unknown schemas are refused without resetting data; earlier edits cannot be recovered.

In a prompt detail, keep Your rating (1–5 or no rating) and a personal usage note. Save or clear your feedback without changing the template, content history or managed installations. The local CLI uses `feedback <id> [--rating 1..5|none] [--note "text"]` or `feedback <id> --clear`.

In a prompt detail, compare saved revisions and restore an earlier template as a new revision. Concurrent edits require refreshing history. CLI commands use the same store: `history <id>`, `compare <id> --version <revision-id>`, and `restore <id> --version <revision-id> --expected-version <latest-revision-id>`. Pass the existing `--managed-dir` to a CLI restore to refresh its managed installations. The web interface reports invalid-fill conflicts and preserves the installation’s prior bytes.

## Install in your tools

Project targets: Claude Code commands (`.claude/commands/NAME.md`) and skills (`.claude/skills/NAME/SKILL.md`), Cursor manual MDC rules (`.cursor/rules/NAME.mdc`), Windsurf manual rules (`.windsurf/rules/NAME.md`), Copilot (`.github/copilot-instructions.md`), Codex (`AGENTS.md`), and a custom project-relative file. ChatGPT uses Copy.

Optional global scope: start with `--profile /absolute/tool-profile`. This is the selected tool's own directory: Claude configuration root, Windsurf memories directory, or Codex home. Claude creates commands/skills; Windsurf uses global_rules.md; Codex uses AGENTS.md. Cursor global rules use its settings; Copilot here uses project instructions. No personal directory is inferred.

Existing files require an explicit append choice. Managed links use the runtime's private deployment store, refresh on saved prompt changes, and can be removed from the prompt's panel. Conflicting external edits or missing new required values preserve existing installation bytes and show a conflict. Copy installations stay independent. Claude commands/skills and manual rules are invoked by their generated names. Windsurf's `.devin/rules` may take precedence over its supported legacy path; rules are limited to12,000 project/6,000 global characters. Codex's default combined instruction budget is32KiB. Actual model consumption depends on the selected tool's configuration.

## CLI

```bash
bun runtime/launcher.ts cli --data-dir /absolute/private-data -- list
bun runtime/launcher.ts cli --data-dir /absolute/private-data -- show PROMPT_ID
bun runtime/launcher.ts cli --data-dir /absolute/private-data -- render PROMPT_ID --values '{"topic":"review"}'
bun runtime/launcher.ts cli --data-dir /absolute/private-data -- deploy PROMPT_ID --target codex --project /absolute/project --values '{"topic":"review"}'
```

Use CLI --help for explicit append, global profile and managed-link removal options. Package third-party notices are retained with their genuine dependencies. Product source is an Aylith product; no new open-source license is implied.