agentleFS
JetBrainsKnown publisherJetBrains/intellij-streamdeck-plugin/streamdeck-plugin/CLAUDE.md

intellij-streamdeck-plugin / streamdeck-plugin

CLAUDE.md67 starsChanged 7 months agoApache-2.0View on GitHub

This is a dual-plugin system enabling Elgato Stream Deck hardware to control JetBrains IDEs: The Stream Deck plugin communicates with the IDE plugin via HTTP (http://{host}:{port}/api/action/{actionId}), passing an Authorization header (password) and optional ?name= query param for run configurations. Live development: refreshPlugin.sh auto-packages and deploys to the Stream Deck app. Debug URL: http://localhost:23654/ The Stream Deck plugin tries ports 63342–63352 sequentially when no custom port is configured, then falls back to the explicit remote port (21420).

  • Installs packages

The file

We split this CLAUDE.md into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add a new *Action.ts in streamdeck-plugin/src/actions/ extending DefaultAction, returning the IDE action ID from actionId()

    line 62
  2. Very specific:

    Add the action entry to com.jetbrains.ide.sdPlugin/manifest.json with a matching UUID

    line 64
  3. Very specific:

    Add icon assets under com.jetbrains.ide.sdPlugin/

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Overview

This is a dual-plugin system enabling Elgato Stream Deck hardware to control JetBrains IDEs:

  1. streamdeck-plugin/ — TypeScript plugin running inside the Stream Deck desktop app
  2. idea-plugin/ — Kotlin/Java plugin running inside JetBrains IDEs

The Stream Deck plugin communicates with the IDE plugin via HTTP (http://{host}:{port}/api/action/{actionId}), passing an Authorization header (password) and optional ?name= query param for run configurations.

Stream Deck Plugin Commands

cd streamdeck-plugin

npm install          # Install dependencies
npm run build        # Full build: TypeScript compile + Browserify bundle
npm run tsc          # TypeScript compilation only (output: build/)
npm run browserify   # Bundle for browser (output: com.jetbrains.ide.sdPlugin/public/dist/)
npm run lint         # ESLint
npm run test         # Jest tests with coverage
npm run distribution # Package release zip (output: releases/)

Live development: refreshPlugin.sh auto-packages and deploys to the Stream Deck app. Debug URL: http://localhost:23654/

IDEA Plugin Commands

cd idea-plugin

./gradlew runIde         # Launch IDE sandbox with plugin loaded
./gradlew build          # Build plugin JAR
./gradlew publishPlugin  # Publish to JetBrains Marketplace

Architecture

Stream Deck Plugin

  • Entry point: src/idea-plugin.ts — extends StreamDeckPluginHandler, registers all action instances
  • Base action: src/actions/default-action.ts — abstract class; override actionId() to map a button to an IDE action ID. Handles onKeyUp() (HTTP call to IDE), onContextAppear(), didReceiveSettings()
  • Actions: src/actions/ — one file per button type. Most are thin subclasses that just return a hardcoded actionId(). EmptyAction is the generic "customized action" where the user provides the ID via property inspector
  • Utils: src/utils/ — HTTP fetch helpers for IDE communication
  • Property Inspector: src/idea-property-inspector.ts + com.jetbrains.ide.sdPlugin/public/property-inspector.html — per-button settings UI (action ID, port, run config name) and global settings (host, default port, password)
  • Plugin manifest: com.jetbrains.ide.sdPlugin/manifest.json — declares all action UUIDs and their icons

IDEA Plugin

  • HTTP endpoint: service/StreamDeckHttpService.kt — RestService that handles /api/action/{actionId}; validates password, delegates to ActionExecutor
  • Action execution: util/ActionExecutor.java — resolves action ID from URI, handles run/debug config targeting, dispatches via IntelliJ's action system
  • Settings: settings/ActionServerSettings.kt + StreamDeckPreferenceComponent.java — stores password, enabled state, focus-only mode, remote port (default 21420)
  • Action Browser: keymap/KeymapPanel.java + ActionsTree.java — UI for browsing all 300+ IDE action IDs (Help > Open Action Browser)
  • Startup: BackendServiceLoader.kt — ApplicationInitializedListener that starts the HTTP server

Adding a New Action

  1. Add a new *Action.ts in streamdeck-plugin/src/actions/ extending DefaultAction, returning the IDE action ID from actionId()
  2. Register it in streamdeck-plugin/src/idea-plugin.ts
  3. Add the action entry to com.jetbrains.ide.sdPlugin/manifest.json with a matching UUID
  4. Add icon assets under com.jetbrains.ide.sdPlugin/

Port Discovery

The Stream Deck plugin tries ports 63342–63352 sequentially when no custom port is configured, then falls back to the explicit remote port (21420).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.