← All concepts

plugin architecture

29 articles · 15 co-occurring · 0 contradictions · 5 briefs

local plugins...sync automatically across desktop and CLI" — Article exemplifies plugin architecture by showing local plugin installation, automatic synchronization across desktop and CLI interfaces.

2026-W15
136

local plugins...sync automatically across desktop and CLI" — Article exemplifies plugin architecture by showing local plugin installation, automatic synchronization across desktop and CLI interfaces.

Adding settings.json as a distributable component in plugin.json (like commands, agents, skills, hooks, mcpServers) would solve this" — Article proposes extending plugin.json schema to include setting

Adapt pi to your workflow, share your wares with others. No forking, no recompilation. Just push to NPM or git and anyone can benefit" — Article demonstrates extensibility mechanism where users can cr

Your AI coding agent can manage skills for you. All you need is this managing-skills skill!" — Demonstrates concrete implementation where agents use a skill management system to dynamically add/remove

makes it actually easy to publish, discover and install extensions" — Article demonstrates improved developer experience for plugin lifecycle (publishing, discovery, installation) through thoughtful p

import skills from @openclaw hub & @vercel" — LettaBot's skill marketplace allows importing capabilities from external hubs, enabling extensibility

Instead of hardcoding integrations, you build an MCP Server that says, "Hey, here are the tools I have, and here is how you use them." The AI model then reads that "menu" and decides when to order off

A new claude code plugin we built that enables two use cases" — Demonstrates plugin-based extension approach to enhance Claude Code capabilities with new functionality

If an MCP connector for a service doesn't exist, in some cases, it's possible to get Claude to create one for you and run your own MCP server to connect to that service." — Demonstrates MCP as a plugi

ChatGPT apps directly in the terminal" — The ability to load external ChatGPT apps into Codex terminal demonstrates a plugin-based architecture where third-party applications can extend core functiona

Tiny core, able to write plugins for itself as you use it." — Pi exemplifies dynamic plugin generation where an agent autonomously creates functionality to extend its own capabilities, enabling self-d

Bundle your extensions, skills, prompt templates, and skills as pi packages, distribute via NPM or git" — Shows practical plugin distribution mechanism through standard package managers (NPM/git), ena

I asked it to create a hook." — Demonstrates practical use of hook mechanism as a real implementation pattern for extending agent behavior.

You can already do status line, widget above editor, full editor replacement, custom message rendering, fully custom UI for commands. Now you can swap out the full footer and do whatever you want." —

Bundle your extensions, skills, prompt templates, and skills as pi packages, distribute via NPM or git" — Article demonstrates practical implementation of extensible plugin architecture through pi's p

We're bringing full feature parity with MacOS: file access, multi-step task execution, plugins, and MCP connectors." — Cowork implements plugins as a standard feature across platforms, showing practic

full feature parity with MacOS: file access, multi-step task execution, plugins, and MCP connectors" — Plugins are a primary feature being launched on Windows platform

claude just hangs if you forget to include the owner attributes in the marketplace.json of a plugin" — Direct evidence of a specific plugin configuration requirement (owner attributes in marketplace.j

wanted to bring the compound engineering plugin that @kieranklaassen made for claude code over to pi" — Concrete example of cross-platform plugin portability and reuse patterns in AI-assisted developm

install with pi install npm:pi-monitor" — Demonstrates plugin architecture pattern where agent capabilities are extended through npm-installable modules, showing modularity and extensibility in agent

[DIRECT] "Hooks are a killer feature" — Hooks feature enables extensibility in pi agent, core plugin/extension pattern

Upload your skills and use vector search to find new ones" — Article showcases skill sharing and discovery mechanism as core feature

it uses your existing Claude Code plugins and setup" — TinyClaw leverages an existing plugin architecture, demonstrating that lightweight agent implementations can maintain compatibility with establis

Easy to build your own voice agent using Agent Skills and Pi Extensions." — Pi Extensions provides a concrete plugin/extension mechanism for customizing agent behavior

Hot-reload everything via /reload" — System supports dynamic hot-reload of extensions without restart, enabling rapid development iteration

had the clanker build an extension that implements a minimal tool output mode" — Article demonstrates practical use of extension system to add feature-specific functionality without modifying core

Built extension for tool approvals to make pi more appealing for non-techies and DevOps people" — Article demonstrates practical extension mechanism built for the pi coding agent, showing extensibilit

[DIRECT] "claude just hangs if you forget to include the owner attributes in the marketplace.json of a plugin" — Demonstrates a specific plugin configuration requirement (owner attributes in marketpla

[INFERRED] "This might end up being one of the largest contribution PRs to the repo so far 👀" — The scale of contribution (43 skills, 6 subagents) demonstrates a modular framework design that support

query this concept
$ db.articles("plugin-architecture")
$ db.cooccurrence("plugin-architecture")
$ db.contradictions("plugin-architecture")