this is a pluginapi component
The PluginApi and pluginHandler used for both host and ext side plugin functionality
Amp Plugin API
`@gencode/plugin-sdk` 提供插件作者需要的稳定类型导出，避免直接依赖 `@gencode/agents` 的内部文件路径。
[](https://github.com/hywax/vitepress-yandex-metrika)
DrPublish Plugin API ====================
Figma API stub
WrongStack core: kernel, types, defaults, and shared utilities for the WrongStack CLI agent.
Bidirectional IPC communication between UI and core in Figma plugins. Lightweight and typed.
SDK for building Harness plugins with React
Obsidian helper for inter-plugin API communication
Hirey Hi as a native OpenClaw plugin: registers Hi tools, the agent-events claim service, and webhook ingress directly inside the gateway process — zero independent daemons, no `mcp.servers.hi` indirection, no per-run frozen tool inventory boundary. Same
[](https://www.npmjs.com/package/@weedzcokie/plugin-loader)
TypeScript definitions for Super Productivity plugin development
Hirey Hi as a native OpenClaw plugin: registers Hi tools, the agent-events claim service, and webhook ingress directly inside the gateway process — zero independent daemons, no `mcp.servers.hi` indirection, no per-run frozen tool inventory boundary. Same
Twenty CRM plugin for OpenClaw — full CRUD on people / companies / opportunities / notes / tasks, custom objects + fields via the Metadata API, dashboards (charts, tabs, widgets), and workflows (triggers, steps, edges, runs, logic functions) with workspac
This package helps you type your external plugin that uses SQLSeal internally.
jsPsych plugin for getting permission to initialize the user's microphone
火一五·克劳德·龙虾增强插件 v6.7.16 — bot-upload-link error path 漏判 hotfix：v6.7.15 本地实测三轮（直连/远程全链路/中途中断），前两轮完美，但第三轮发现 req.on('error') / ws.on('error') 触发后 Promise done，外面 `if (aborted)` 不拦截 error case 继续走 renameSync(partial, file) → ENOENT 误报 stderr（partial 已被 rmSync
jsPsych plugin for getting permission to initialize the user's camera
ts and vue project
Parse Figma Variables Plugin API and REST API into design tokens.
SDK for authoring Midnight Cutter Studio plugins — types + Vite build preset.
基于webpack5开发的一款专注于打包、运行的工具
The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.42) is used. For example, calling `/info` is the same as calling `/v1.42/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```
API utils and shared types for Horizon plugins
Rust bindings for the WSL Plugin API
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.