op_pi

Files (164)

• lsp-client.json · .codex/
• ci.yml · .github/workflows/
• release.yml · .github/workflows/
• .gitignore
• lsp.json · .opencode/
• AGENTS.md
• ARCHITECTURE.md
• CHANGELOG.md
• Cargo.lock
• Cargo.toml
• LICENSE
• README.md
• SKILL.md
• op_pi-hero.svg · assets/
• Cargo.toml · crates/evidence-ledger/
• README.md · crates/evidence-ledger/
• 0001_evidence_inbox.sql · crates/evidence-ledger/migrations/
• 0002_outbox_and_mirror.sql · crates/evidence-ledger/migrations/
• 0003_payload_binding_and_relay_leases.sql · crates/evidence-ledger/migrations/
• 0004_transactional_acceptance_binding.sql · crates/evidence-ledger/migrations/
• error.rs · crates/evidence-ledger/src/
• inbox.rs · crates/evidence-ledger/src/
• intake.rs · crates/evidence-ledger/src/
• lib.rs · crates/evidence-ledger/src/
• mirror.rs · crates/evidence-ledger/src/
• outbox.rs · crates/evidence-ledger/src/
• payload.rs · crates/evidence-ledger/src/
• relay.rs · crates/evidence-ledger/src/
• relay_store.rs · crates/evidence-ledger/src/
• durable_inbox.rs · crates/evidence-ledger/tests/
• intake_service.rs · crates/evidence-ledger/tests/
• mirror_parity.rs · crates/evidence-ledger/tests/
• outbox_mirror.rs · crates/evidence-ledger/tests/
• outbox_relay.rs · crates/evidence-ledger/tests/
• mod.rs · crates/evidence-ledger/tests/support/
• op_pi.service · deploy/
• dist-workspace.toml
• agent-runbook.md · docs/
• aws-cloudflare-intake.md · docs/
• canonical-contract-cleanup.md · docs/
• event-contract-v1.md · docs/
• MEMORY.example.md · docs/examples/
• README.example.md · docs/examples/memory/
• example-channel.md · docs/examples/memory/channels/
• 2026-03-10.md · docs/examples/memory/daily/
• op_pi.md · docs/examples/memory/projects/
• lessons.md · docs/examples/memory/topics/
• rules.md · docs/examples/memory/topics/
• geobench.md · docs/
• google-calendar-intake.md · docs/
• linear-intake.md · docs/
• live-verification.md · docs/
• memory-offload-architecture.md · docs/
• memory-offload-guide.md · docs/
• native-event-contract.md · docs/
• op_pi.yaml · geobench/
• install.sh
• install_hooks.sh · integrations/git/
• post_checkout.sh · integrations/git/
• post_commit.sh · integrations/git/
• …and 104 more

SKILL.md (first lines)

# op_pi skill attachment surface

## Intent

Use this repo as:
- executable/runtime repo
- daemon process for Discord notification routing
- attachable skill surface for OpenClaw / Clawdbot

## Prerequisites

⭐ If you want to support op_pi, star this repository. The interactive repo-local installer and `op_pi install` can offer an optional post-install GitHub star prompt via authenticated `gh api` access when `gh` is installed and authenticated. Skip it with `--skip-star-prompt` or `OP_PI_SKIP_STAR_PROMPT=1`.

```bash
gh api --method PUT /user/starred/IYENTeam/op_pi --silent
```

## Primary install flow

Preferred operator instruction:

```text
@openclaw install https://github.com/IYENTeam/op_pi
```

Expected automation flow:

1. clone repo
2. run `./install.sh`
3. read this `SKILL.md`
4. attach skill
5. scaffold `~/.op_pi/config.toml`
6. start daemon
7. run live verification presets

## Runtime surface

Default daemon URL:

```text
http://127.0.0.1:25294
```

Core commands:

```bash
op_pi
op_pi start
op_pi status
op_pi config
op_pi send --channel <id> --message "..."
op_pi github issue-opened ...
op_pi github pr-status-changed ...
op_pi git commit ...
op_pi tmux keyword ...
op_pi tmux stale ...
op_pi tmux new -s <session> --channel <id> --keywords error,complete --shell /bin/zsh -- command
op_pi tmux watch -s <existing-session> --channel <id> --mention '<@id>' --keywords error,complete
```

## Lifecycle surface

```bash
op_pi install
op_pi install --systemd
op_pi install --skip-star-prompt
op_pi update --restart
op_pi uninstall --remove-systemd --remove-config
./install.sh
./install.sh --systemd
./install.sh --skip-star-prompt
```

## Discord bot token (recommended setup)

⚠️ **Create a dedicated Discord bot for op_pi notifications.** Do not reuse your Clawdbot / OpenClaw bot token.

Why:
- op_pi sends high-volume notifications (commits, PRs, tmux events)
- Using the same bot token as your gateway pollutes the bot's identity
- A separate bot (e.g. "CCNotifier") keeps notifications cleanly separated from AI chat
- If op_pi restarts or crashes, it won't affect your main bot

Setup:
1. Go to [Discord Developer Portal](https://discord.com/developers/applications)
2. Create a new application (e.g. "op_pi-notifier" or "CCNotifier")
3. Create a bot, copy the token
4. Invite the bot to your server with Send Messages permission
5. Use this token in `~/.op_pi/config.toml`:

```toml
[providers.discord]
bot_token = "your-dedicated-op_pi-bot-token"
```

## Config scaffold expectations

Key sections:
- `[providers.discord]`
- `[daemon]`
- `[defaults]`
- `[[routes]]`
- `[monitors]`
- `[[monitors.git.repos]]`
- `[[monitors.tmux.sessions]]`

Typical preset route:

```toml
[[routes]]
event = "github.*"
filter = { repo = "op_pi" }
channel = "1480171113253175356"
mention = "<@1465264645320474637>"
format = "compact"
```

## Dynamic template opt-in

From IYENTeam/op_pi, MIT.

More from IYENTeam/op_pi