Pinery
Your engineering teammate in Lark
★ —PUSHED :: —
ABOUT
Pinery lives in Lark as an engineering colleague: anyone can ask it about the codebase and get answers with evidence and confidence levels, while engineers dispatch it to write code, run scripts and open PRs. Tasks enter an isolated workspace straight from a Lark thread, and the PR link lands back in that thread.
It is self-hosted open source by design — single-container deployment, Lark long connection (no public callback URL), models via OpenRouter — so code never leaves the intranet. Capabilities are tiered from L0 observation through L1 writing and L2 delivery, with L3 dangerous operations disabled by default.
HIGHLIGHTS
- L0-L3 TIERS — read-only investigation up to PR delivery, granted per role
- SELF-HOSTED — one container; code stays inside the intranet
- NO PUBLIC CALLBACK — Lark long connection instead of webhooks
- THREAD TO PR — tasks start in a Lark topic and report back to it