Bindry
Sign in

Plugins

Install once. Your Stacks load themselves.

No copying and pasting instructions. Add the Bindry plugin to the AI tool you already use, connect it, and you're done.

  1. 1

    Install the plugin

    One command adds Bindry to Claude Code, Codex, or GitHub Copilot.

  2. 2

    Connect once

    Link your Bindry workspace with an API key. Public Stacks from the Library work without one.

  3. 3

    Your Stacks load and stay current

    Pick a Stack and it loads into your tool. Choose live, and every change you make in Bindry shows up there on its own.

Set up Claude Code Set up Codex Set up GitHub Copilot Find a Stack in the Library

Choose your tool

Install a plugin today, use a file any AI tool can already read, or tell us which tool to support next.

Install today

Ready to use right now, with both snapshot and always-current syncing.

Claude Code

Turns a Stack into skills Claude Code loads only when it needs them.

claude plugin marketplace add bindryai/Plugins && claude plugin install bindry@bindry-plugins
Setup guide

OpenAI Codex

The same idea, built for Codex.

codex plugin marketplace add bindryai/Plugins && codex plugin add bindry@bindry-plugins
Setup guide

GitHub Copilot Preview

The same plugin, built for Copilot in the terminal and VS Code.

copilot plugin marketplace add bindryai/Plugins && copilot plugin install bindry@bindry-plugins
Setup guide

Works with any AI tool — nothing to install

File formats any AI tool can already read. Just copy, save, or share the link.

AGENTS.md

A standard file any AI tool can read. Save it and you’re done.

How it works

Markdown bundle

One text file per Stack, ready to paste anywhere.

How it works

MCP Server

Connects your Stacks directly to any AI tool that supports MCP, a common standard for sharing context with AI.

How it works

On the horizon

Our system works the same everywhere, so these are close — just tell us which one to build next.

Cursor

Would send your Stacks straight into Cursor’s own rules file.

Windsurf

Would keep your Stacks in sync with Windsurf.

Cline

Would feed your instructions into Cline as you work.

Aider

Would export a Stack in Aider’s own format.

Zed

Would bring your Stacks into Zed’s AI panel.

JetBrains

Would cover JetBrains tools like IntelliJ and PyCharm.