← 全部工具

plurnk/plurnk-service

热度 65 更新于 AI 与 Agent

Runtime for coding agents: one daemon, one model-facing operation language, addressable project context, and loops that survive the client. Runs on local or hosted models.

githubauto-collected

安装

暂未验证可直接使用的安装命令,请查看项目官方文档或 Release。

PLURNK

PLURNK is a runtime for software-development agents. It combines a model-facing operation language, addressable project context, persistent execution state, and thin clients over a single daemon.

Quick start

npx @plurnk/plurnk-service start   # the daemon
npx @plurnk/plurnk                 # the terminal client, from inside your project

The daemon starts without a model and says so, naming the configuration file it created on first run. Choose a profile there, or set PLURNKMODEL and your provider's key in the environment; plurnk-service config defaults prints every installed option.

An unedited recording of the published client and daemon against a three-file project, answering in seventeen seconds on a local model: Qwen3.8-27B at Q3KS, served by llama.cpp on one 16 GB consumer GPU. Beneath the prompt are the operations the model ran, its response, and a footer carrying turns, elapsed time and tokens. Any provider route works the same way.

Design

  • Models act through one small compositional language rather than a collection

of unrelated tool schemas.

  • Project context and execution results have durable addresses.
  • Agent work is persisted and recoverable rather than held in a client process.

Architecture

flowchart LR
    clients["CLI / TUI / web"] <--> agui["AG-UI"]
    agui <--> core["plurnk-service<br/>engine + durable state"]
    core <--> providers["Model providers"]
    plugins["Scheme / executor / mimetype plugins"] --> core
    modules["Optional daemon modules"] --> core
    project["Project files + Git"] <--> core
    core --> sqlite[(SQLite)]

The daemon owns durable agent state and composes package-owned capabilities. Clients submit actions and render events; plugins run in-process but retain their own contracts.

See ARCHITECTURE.md for the package map, process boundaries, and request flow.

Requirements

  • Node.js 26 or newer
  • npm
  • Git
  • a configured local or remote model endpoint for live runs

Configuration

See the configuration guide for installation, environment precedence, and Worker settings. plurnk-service config defaults prints every installed package's authoritative settings. The enabled plurnk skill exposes the same guide and catalog to the model on demand.