Skip to content

Tugboat — JetBrains plugin (IntelliJ platform) #588

Closed as not planned
Closed as not planned

Description

@thomas-stegemann

Split out of #101, which now covers the VS Code extension only.

Why separate

The two distributions in #101 read as "the same thing twice", but they share no code and almost no toolchain:

VS Code JetBrains
Language TypeScript Kotlin / Java
Build npm + vsce Gradle + IntelliJ Platform Plugin SDK
Embedding WebView JCEF
Distribution VS Code Marketplace (Azure DevOps publisher) JetBrains Marketplace (separate account + review)
Target one IDE the whole IntelliJ family (IDEA, Rider, GoLand, PyCharm, …)

Bundling them meant one ticket could not finish until both ecosystems were stood up. Splitting lets the VS Code extension ship while this one is scoped properly.

Scope

Same shape as the VS Code extension once that lands: the plugin starts a local bowire process with the project root as its working directory and hosts the workbench in a JCEF panel. Collections, environments and recordings therefore live in the project's .bowire/ folder and travel with the repo — no IDE-proprietary storage.

Open questions

  • JCEF availability across the IntelliJ family and minimum platform version
  • Whether the plugin bundles a Bowire binary or requires one on PATH — inherit whatever Tugboat — VS Code workbench extension #101 settles on
  • JetBrains Marketplace account, publisher identity and review lead time (this is an org-level setup step, not code)

Acceptance (when scoped)

  • Plugin on the JetBrains Marketplace, opens the Bowire workbench in a tool window
  • Same UI, shortcuts and behaviour as the VS Code extension and the standalone tool
  • Collections + envs persist in the project's .bowire/ folder
  • Shares the Kuestenlogik.Bowire version with the other targets — no protocol-plugin drift

Related

Activity

  1. thomas-stegemann commented on Sep 2, 2026

    @thomas-stegemann
    MemberAuthor

    Not planned for now.

    The scope here is sound and the split from #101 was right — the two IDE distributions genuinely share no code. But the table in the issue is also the argument against starting: Kotlin/Java, Gradle and the IntelliJ Platform Plugin SDK, JCEF instead of a WebView, and a separate marketplace account with its own review process. That is a second toolchain to stand up, learn and keep current, for a plugin whose job is to host the same workbench the VS Code extension already hosts.

    Bowire is better served right now by depth on what exists than by a second front. The workbench, the CLI and MCP are three surfaces already held to parity; a fourth distribution channel adds maintenance without adding capability.

    Nothing here is wasted if it comes back: the shape is settled — start a local bowire with the project root as its working directory, host it in a JCEF panel, and let collections and environments live in the project's .bowire/ folder so they travel with the repo. That is the same contract the VS Code extension is built on, so whoever picks this up inherits a working design rather than a blank page.

    Removed from the v2.6 milestone so the version's history reflects what shipped. Reopen when there is a reason to carry a second toolchain — a user asking for it by name would be a good one.

  2. moved this from Backlog to Done in Bowireon Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    • Status
      Done

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions