Hydra marketplace · community

Your workflow.
Your Hydra.

Discover useful building blocks. Make a local integration. Give your project a home in the Hydra community.

Explore the catalog

1 source starter · 0 published plugins
Source starter · not an installable plugin

Local control

Build a tool around real retained terminal sessions: list sessions, attach a client, receive events and send generation-bound input. Start with the dependency-free Python client and its isolated demo.

  • macOS / Linux
  • Python 3.10+
  • Protocol 3
  • MIT source

Local-process demo tested on macOS and Ubuntu Linux. Use session discovery and events as building blocks for your own workspace tools, test-runner helpers and agent integrations.

Bring your workflow to the community.

Already building an integration? Share what it makes possible, link the source and help other developers try it.

Build with the community.

Real source. Clear next steps.

01

Run a working example

List sessions, connect independent clients and watch a retained task continue between connections. The Python starter shows the session protocol in action.

Open the starter guide →
02

Explore the local core

Start with the public desktop source and its development guide. See how Hydra's terminal, sessions and interface fit together.

Read the development guide ↗
03

Share what you build

Contribute improvements to the local app, or propose a community integration with a source link and clear setup instructions.

Read the contribution guide ↗
Developer quickstart: from source to a working demo
  1. Get the public source and prerequisites. Follow the development guide for your platform. Use Python 3.10+ and build both binaries from the same checkout.
  2. Run the starter. From the repository root, after installing the native build prerequisites:
    cargo build -p maestro-app -p pty-daemon
    python3 examples/local-control/demo.py --app target/debug/maestro-app --daemon target/debug/pty-daemon
    The example sets up and cleans up its own test session. No Python packages or cloud setup needed.
  3. Make it your own. Connect your tool to a session, observe events and send input using the client API guide. The guide includes the input-delivery contract and complete Python examples.
  4. Make the project reproducible. Include a license, exact source revision, supported platform/Hydra versions, setup and removal steps, dependencies, and a working test. Then submit your project.
A note on local integrations

Local plugins and integrations run with your user account's privileges. Review what you install, and don't include credentials or private terminal content in submissions.

For makers, by makers

You build it.
Help others find it.

Submit a working local integration or propose the next one. The draft below opens on GitHub with a checklist to complete; nothing is posted until you submit it there.

GitHub requires a GitHub account to post. Email is an alternative; no Hydra account, payment or subscription is required.

GitHub submissions are public; email is available for a private initial discussion. Projects are considered for the catalog after submission.

Other feedback or bug report ↗

Ready to share?

  • A useful workflow and whether it works today or is a proposal
  • A public source link, exact revision, publisher and license
  • Setup and removal steps, dependencies, operating systems and Hydra versions
  • Terminal, filesystem and network access; how credentials are handled
  • A reproducible test and known limitations
  • Any missing integration hooks or API capabilities