v0.6.16-staging.38567355491.1.70d207f11d1f

Dockpipe v0.6.16

Visit dockpipe.com for the Dockpipe website.

The 0.6.x release brings Dockpipe's workflow tools together in a desktop launcher
and a standalone CLI. Run your own project commands, add reusable workflows from
the Marketplace, select secret environments and try running selected work on
another machine. You can use the installed application without a Dockpipe source
checkout or Go compiler.

Workflow editor, execution monitoring and a refreshed desktop

Build and run workflows visually

The Workflows page now opens a visual editor for commands, scripts, packaged
workflow calls and parallel groups. Switch to YAML for advanced settings, validate
before saving, and run through the same local or paired-machine controls. Your
workflow remains an ordinary YAML file; canvas positions are local preferences.

See what is running and where resources are going

Open Executions → Processes & resources to inspect recent Dockpipe-managed
processes, their lifecycle and available CPU/memory measurements. The System
view adds a searchable process list with sortable columns and overall CPU, memory,
swap, disk, network and uptime information. Sorting and selection survive refreshes.

Runs & logs brings local run logs and stop controls together with remote job
status, cancellation and result downloads. It replaces the separate Activity page.
Empty history explains how to start a run, and actions follow the selected run.

Inspect containers and paired machines

The Containers page replaces the Docker navigation label. Its resource canvas
shows containers, networks, volumes and their relationships, with selectable
details, logs, lifecycle controls and a shell action for local running containers.
Layer filters and movable panels help keep larger views readable.

System monitoring and container inventory can switch between this computer and a
paired remote machine. Remote monitoring requires updated broker/worker binaries
and an explicit opt-in on the worker using dockpipe remote monitoring --system --docker. Remote container views are read-only; remote start, stop, shell and raw
container logs are not included. dockpipe remote monitoring --disable turns off
sharing without removing the pairing.

More room for your workspace

The View menu now matches the sidebar. Hide or restore the sidebar using the
spaced header control, View → Show sidebar, or Ctrl+B; the preference is
remembered. Shared icons, canvas controls and light/dark surfaces keep the editor,
container views and execution pages consistent.

Current limits

Native system/process resource collection is available on Linux. macOS and Windows
retain supported lifecycle information but do not yet have native system metrics.
Docker inventory uses the configured Docker engine. QEMU measurements describe
its host process, not the guest OS. Discovered system processes are read-only and
are never treated as Dockpipe-owned. Local run logs cover runs started by the
current launcher session; telemetry is bounded recent history, not an audit archive.

Earlier maintenance updates

Flatpak terminal commands now retain the selected project folder, including mounted
drives and paths containing spaces. dockpipe init no longer falls back to the home
directory when the shortcut starts Flatpak. The launcher upgrades its previous
generated shortcut automatically while preserving native or user-modified commands.
An unavailable project folder fails before initialization.

Package listings now use clearer display names and descriptions, with Apps,
Workflows, Integrations and Core discovery types. Package authors can maintain
titles, descriptions and purpose categories in their source metadata; compiled
catalogs and installed-package inventory retain these fields without changing
package IDs or installation commands. Older catalogs remain supported.

Compatible workflows now declare macOS support and describe their host prerequisites.
Linux-specific workflows remain restricted. Remote-machine setup better handles
service executable updates and paired-worker status, and the Machines page avoids
an unnecessary scrollbar when its content fits.

The launcher shows package download and stored archive sizes in the Marketplace
and Installed views. Older catalogs without size information show an explicit
unavailable value instead of a misleading zero.

Remote-access setup now links directly to compatible provider packages in the
Marketplace and selects a newly installed provider when you return. Existing remote
addresses stay visible and pre-fill setup, with a review action for connections whose
provider details have not been recorded. Provider setup continues through the same
guided authentication, tunnel and connection checks used by the CLI.

Installation examples default to production. Website builds can select staging
download URLs, APT settings and Marketplace instructions explicitly, while keeping
staging-only Homebrew commands out of production pages. Maintainers can configure
an immediate Homebrew sync after successful staging publication; the tap retains
its native Mac checks and scheduled fallback before publishing package updates.

The Flatpak launcher now sets up the dockpipe terminal shortcut automatically
on first launch when no existing host command is found. Bash, Zsh and Fish receive
the missing PATH configuration; open a new terminal after launching Dockpipe.
Existing commands and conflicting shell configuration are preserved, with setup
failures shown in the launcher. Desktop sessions without a working tray keep the
window accessible, and a known harmless Qt Wayland warning is filtered narrowly.

Pipeon's desktop dependencies have been updated and its native clipboard bridge
is restricted to the configured local editor origin. Native builds and clipboard
access checks now run on Linux, macOS and Windows. Dependency update PRs target
dev for qualification before release; GitHub security updates still initially
target the repository's default branch.

Pipeon's Linux desktop shell includes a compatibility backport for the GLib
string-iterator vulnerability RUSTSEC-2024-0429, with an optimized regression test.
Cloud storage cache rules now honor publisher cache-control headers by default,
so mutable release catalogs can refresh without waiting for a forced CDN TTL.
Existing infrastructure requires applying the updated rules and purging old
mutable cache entries.

Release setup and cloud storage workflows now require your own repository, endpoint,
bucket and state settings. Personal environment identifiers and machine paths have
been replaced with placeholders. A public-content check guards source and package
archives against these configuration leaks. Official installation URLs are unchanged.

What's new

A desktop workspace for your workflows

The launcher brings Apps, Workflows, Machines, Containers and Executions into one
window. Save project contexts, choose a workflow and execution machine, start or
stop runs, and inspect progress and logs. The same workflows remain available from
the CLI for terminals, servers and CI.

Desktop installers include the launcher and matching CLI. Choose a CLI-only
installation when you do not need the desktop app.

Install the tools you need from the Marketplace

Open Packages → Marketplace to browse optional workflows and tool integrations.
Inspect their platform and dependencies, then install selected packages into your
user store. Downloads are checked against the catalog checksum. The Installed
view shows both user-installed and installer-managed packages.

Base installations include required core. Optional packages, their external tools
and provider sign-ins are separate. Removing an optional user package preserves its
data and settings. See using packages.

Create and reuse your own workflows

Use dockpipe init hello to create a workflow in your project, validate its YAML
before running it, and combine host commands, container steps and packaged
workflows. Host workflows can run without Docker when container preflight is
disabled; container workflows need a reachable engine.

Workflow outputs and reusable container image artifacts help connect steps and
avoid unnecessary image rebuilds. The first-workflow guide
starts with a small host command, then adds a container.

Select a secret environment for each run

Named environments bind selected secret values to workflow environment variables.
Adapters are available for 1Password Environments, AWS Secrets Manager,
Azure Key Vault and Infisical. Select a configured environment with
--secret-environment NAME; configuration stores references rather than secret
values. Existing 1Password vault templates remain supported.

Install and authenticate the matching provider CLI first. The 1Password adapter
requires an op build with op run --environment; AWS bindings currently require
string fields in a JSON secret. See secret environments
for setup and provider limits.

Remote workflow delivery — preview

Pair a worker using a verification code and explicit approval, without transferring
an invitation file or opening inbound SSH on the worker. Preview the selected
workflow sources, assets and package dependencies before submission, then inspect
job results and cancellation through the CLI or launcher.

Remote setup currently targets Linux and macOS. The Cloudflare Tunnel resolver
uses your own Cloudflare account and managed domain; workers connect outbound.
Use the same updated CLI on the broker and worker. Windows workers, a hosted
Dockpipe Cloud service and complete...

v0.6.15-staging.38500140985.1.9cfcdcbb5441

Dockpipe v0.6.15

Visit dockpipe.com for the Dockpipe website.

The 0.6.x release brings Dockpipe's workflow tools together in a desktop launcher
and a standalone CLI. Run your own project commands, add reusable workflows from
the Marketplace, select secret environments and try running selected work on
another machine. You can use the installed application without a Dockpipe source
checkout or Go compiler.

Maintenance update

Flatpak terminal commands now retain the selected project folder, including mounted
drives and paths containing spaces. dockpipe init no longer falls back to the home
directory when the shortcut starts Flatpak. The launcher upgrades its previous
generated shortcut automatically while preserving native or user-modified commands.
An unavailable project folder fails before initialization.

Package listings now use clearer display names and descriptions, with Apps,
Workflows, Integrations and Core discovery types. Package authors can maintain
titles, descriptions and purpose categories in their source metadata; compiled
catalogs and installed-package inventory retain these fields without changing
package IDs or installation commands. Older catalogs remain supported.

Compatible workflows now declare macOS support and describe their host prerequisites.
Linux-specific workflows remain restricted. Remote-machine setup better handles
service executable updates and paired-worker status, and the Machines page avoids
an unnecessary scrollbar when its content fits.

The launcher shows package download and stored archive sizes in the Marketplace
and Installed views. Older catalogs without size information show an explicit
unavailable value instead of a misleading zero.

Remote-access setup now links directly to compatible provider packages in the
Marketplace and selects a newly installed provider when you return. Existing remote
addresses stay visible and pre-fill setup, with a review action for connections whose
provider details have not been recorded. Provider setup continues through the same
guided authentication, tunnel and connection checks used by the CLI.

Installation examples default to production. Website builds can select staging
download URLs, APT settings and Marketplace instructions explicitly, while keeping
staging-only Homebrew commands out of production pages. Maintainers can configure
an immediate Homebrew sync after successful staging publication; the tap retains
its native Mac checks and scheduled fallback before publishing package updates.

The Flatpak launcher now sets up the dockpipe terminal shortcut automatically
on first launch when no existing host command is found. Bash, Zsh and Fish receive
the missing PATH configuration; open a new terminal after launching Dockpipe.
Existing commands and conflicting shell configuration are preserved, with setup
failures shown in the launcher. Desktop sessions without a working tray keep the
window accessible, and a known harmless Qt Wayland warning is filtered narrowly.

Pipeon's desktop dependencies have been updated and its native clipboard bridge
is restricted to the configured local editor origin. Native builds and clipboard
access checks now run on Linux, macOS and Windows. Dependency update PRs target
dev for qualification before release; GitHub security updates still initially
target the repository's default branch.

Pipeon's Linux desktop shell includes a compatibility backport for the GLib
string-iterator vulnerability RUSTSEC-2024-0429, with an optimized regression test.
Cloud storage cache rules now honor publisher cache-control headers by default,
so mutable release catalogs can refresh without waiting for a forced CDN TTL.
Existing infrastructure requires applying the updated rules and purging old
mutable cache entries.

Release setup and cloud storage workflows now require your own repository, endpoint,
bucket and state settings. Personal environment identifiers and machine paths have
been replaced with placeholders. A public-content check guards source and package
archives against these configuration leaks. Official installation URLs are unchanged.

What's new

A desktop workspace for your workflows

The launcher brings Apps, Workflows, Machines and Activity into one
window. Save project contexts, choose a workflow and execution machine, start or
stop runs, and inspect progress and logs. The same workflows remain available from
the CLI for terminals, servers and CI.

Desktop installers include the launcher and matching CLI. Choose a CLI-only
installation when you do not need the desktop app.

Install the tools you need from the Marketplace

Open Packages → Marketplace to browse optional workflows and tool integrations.
Inspect their platform and dependencies, then install selected packages into your
user store. Downloads are checked against the catalog checksum. The Installed
view shows both user-installed and installer-managed packages.

Base installations include required core. Optional packages, their external tools
and provider sign-ins are separate. Removing an optional user package preserves its
data and settings. See using packages.

Create and reuse your own workflows

Use dockpipe init hello to create a workflow in your project, validate its YAML
before running it, and combine host commands, container steps and packaged
workflows. Host workflows can run without Docker when container preflight is
disabled; container workflows need a reachable engine.

Workflow outputs and reusable container image artifacts help connect steps and
avoid unnecessary image rebuilds. The first-workflow guide
starts with a small host command, then adds a container.

Select a secret environment for each run

Named environments bind selected secret values to workflow environment variables.
Adapters are available for 1Password Environments, AWS Secrets Manager,
Azure Key Vault and Infisical. Select a configured environment with
--secret-environment NAME; configuration stores references rather than secret
values. Existing 1Password vault templates remain supported.

Install and authenticate the matching provider CLI first. The 1Password adapter
requires an op build with op run --environment; AWS bindings currently require
string fields in a JSON secret. See secret environments
for setup and provider limits.

Remote workflow delivery — preview

Pair a worker using a verification code and explicit approval, without transferring
an invitation file or opening inbound SSH on the worker. Preview the selected
workflow sources, assets and package dependencies before submission, then inspect
job results and cancellation through the CLI or launcher.

Remote setup currently targets Linux and macOS. The Cloudflare Tunnel resolver
uses your own Cloudflare account and managed domain; workers connect outbound.
Use the same updated CLI on the broker and worker. Windows workers, a hosted
Dockpipe Cloud service and complete native Mac pairing/sleep-wake qualification
are not included in this release's verified remote experience. Start with
remote setup and limits.

Reusable AI workflows and persistent package data

Optional AI packages let you choose a provider, supply repeatable inputs and inspect
outputs. DorkPipe workflows can add task orchestration, model policies and review
steps. Provider accounts, authentication and any model charges remain separate;
available approval and isolation controls depend on the selected workflow and
runtime. See AI workflows.

Durable package settings and continuity data are separated from disposable project
builds and caches. dockpipe clean --dry-run previews the project files that ordinary
clean would remove; durable package state stays outside that cleanup.

Install

Choose the release asset for your OS and CPU. Native downloads cover Linux amd64
and arm64, macOS Intel and Apple Silicon, and Windows x64. Package availability
does not imply that every distribution, provider or workflow has been qualified.

Native host steps need Bash; Git for Windows provides it on Windows. Docker
is needed for container workflows, not the host-only example below. Provider
CLIs and Git are needed by workflows that use them.

Linux

The installer selects a native CLI package for supported package-manager families,
or a portable archive, and verifies its downloads against the release checksums:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.15/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.15 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

For the desktop on Ubuntu 22.04 / 24.04 or Pop!_OS 22.04, download the matching
CLI and desktop DEBs from this release, verify them against SHA256SUMS.txt, then
install both:

sudo apt install ./dockpipe_0.6.15_amd64.deb ./dockpipe-desktop_0.6.15_amd64.deb

Use arm64 filenames on ARM64. Open Dockpipe from the application menu.
RPM, APK and Arch packages are CLI-only. The same desktop DEBs are installation-tested
on Ubuntu 22.04 and 24.04; that does not establish every downstream desktop setup.

macOS

Install the CLI for Intel or Apple Silicon:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.15/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.15 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

Desktop artifacts are named `dockpipe-desktop_0.6.15_da...

v0.6.14-staging.38463452087.1.07771827fd20

Dockpipe v0.6.14

Visit dockpipe.com for the Dockpipe website.

The 0.6.x release brings Dockpipe's workflow tools together in a desktop launcher
and a standalone CLI. Run your own project commands, add reusable workflows from
the Marketplace, select secret environments and try running selected work on
another machine. You can use the installed application without a Dockpipe source
checkout or Go compiler.

Maintenance update

Flatpak terminal commands now retain the selected project folder, including mounted
drives and paths containing spaces. dockpipe init no longer falls back to the home
directory when the shortcut starts Flatpak. The launcher upgrades its previous
generated shortcut automatically while preserving native or user-modified commands.
An unavailable project folder fails before initialization.

Package listings now use clearer display names and descriptions, with Apps,
Workflows, Integrations and Core discovery types. Package authors can maintain
titles, descriptions and purpose categories in their source metadata; compiled
catalogs and installed-package inventory retain these fields without changing
package IDs or installation commands. Older catalogs remain supported.

Compatible workflows now declare macOS support and describe their host prerequisites.
Linux-specific workflows remain restricted. Remote-machine setup better handles
service executable updates and paired-worker status, and the Machines page avoids
an unnecessary scrollbar when its content fits.

The launcher shows package download and stored archive sizes in the Marketplace
and Installed views. Older catalogs without size information show an explicit
unavailable value instead of a misleading zero.

Remote-access setup now links directly to compatible provider packages in the
Marketplace and selects a newly installed provider when you return. Existing remote
addresses stay visible and pre-fill setup, with a review action for connections whose
provider details have not been recorded. Provider setup continues through the same
guided authentication, tunnel and connection checks used by the CLI.

Installation examples default to production. Website builds can select staging
download URLs, APT settings and Marketplace instructions explicitly, while keeping
staging-only Homebrew commands out of production pages. Maintainers can configure
an immediate Homebrew sync after successful staging publication; the tap retains
its native Mac checks and scheduled fallback before publishing package updates.

The Flatpak launcher now sets up the dockpipe terminal shortcut automatically
on first launch when no existing host command is found. Bash, Zsh and Fish receive
the missing PATH configuration; open a new terminal after launching Dockpipe.
Existing commands and conflicting shell configuration are preserved, with setup
failures shown in the launcher. Desktop sessions without a working tray keep the
window accessible, and a known harmless Qt Wayland warning is filtered narrowly.

Pipeon's desktop dependencies have been updated and its native clipboard bridge
is restricted to the configured local editor origin. Native builds and clipboard
access checks now run on Linux, macOS and Windows. Dependency update PRs target
dev for qualification before release; GitHub security updates still initially
target the repository's default branch.

Pipeon's Linux desktop shell includes a compatibility backport for the GLib
string-iterator vulnerability RUSTSEC-2024-0429, with an optimized regression test.
Cloud storage cache rules now honor publisher cache-control headers by default,
so mutable release catalogs can refresh without waiting for a forced CDN TTL.
Existing infrastructure requires applying the updated rules and purging old
mutable cache entries.

Release setup and cloud storage workflows now require your own repository, endpoint,
bucket and state settings. Personal environment identifiers and machine paths have
been replaced with placeholders. A public-content check guards source and package
archives against these configuration leaks. Official installation URLs are unchanged.

What's new

A desktop workspace for your workflows

The launcher brings Apps, Workflows, Machines and Activity into one
window. Save project contexts, choose a workflow and execution machine, start or
stop runs, and inspect progress and logs. The same workflows remain available from
the CLI for terminals, servers and CI.

Desktop installers include the launcher and matching CLI. Choose a CLI-only
installation when you do not need the desktop app.

Install the tools you need from the Marketplace

Open Packages → Marketplace to browse optional workflows and tool integrations.
Inspect their platform and dependencies, then install selected packages into your
user store. Downloads are checked against the catalog checksum. The Installed
view shows both user-installed and installer-managed packages.

Base installations include required core. Optional packages, their external tools
and provider sign-ins are separate. Removing an optional user package preserves its
data and settings. See using packages.

Create and reuse your own workflows

Use dockpipe init hello to create a workflow in your project, validate its YAML
before running it, and combine host commands, container steps and packaged
workflows. Host workflows can run without Docker when container preflight is
disabled; container workflows need a reachable engine.

Workflow outputs and reusable container image artifacts help connect steps and
avoid unnecessary image rebuilds. The first-workflow guide
starts with a small host command, then adds a container.

Select a secret environment for each run

Named environments bind selected secret values to workflow environment variables.
Adapters are available for 1Password Environments, AWS Secrets Manager,
Azure Key Vault and Infisical. Select a configured environment with
--secret-environment NAME; configuration stores references rather than secret
values. Existing 1Password vault templates remain supported.

Install and authenticate the matching provider CLI first. The 1Password adapter
requires an op build with op run --environment; AWS bindings currently require
string fields in a JSON secret. See secret environments
for setup and provider limits.

Remote workflow delivery — preview

Pair a worker using a verification code and explicit approval, without transferring
an invitation file or opening inbound SSH on the worker. Preview the selected
workflow sources, assets and package dependencies before submission, then inspect
job results and cancellation through the CLI or launcher.

Remote setup currently targets Linux and macOS. The Cloudflare Tunnel resolver
uses your own Cloudflare account and managed domain; workers connect outbound.
Use the same updated CLI on the broker and worker. Windows workers, a hosted
Dockpipe Cloud service and complete native Mac pairing/sleep-wake qualification
are not included in this release's verified remote experience. Start with
remote setup and limits.

Reusable AI workflows and persistent package data

Optional AI packages let you choose a provider, supply repeatable inputs and inspect
outputs. DorkPipe workflows can add task orchestration, model policies and review
steps. Provider accounts, authentication and any model charges remain separate;
available approval and isolation controls depend on the selected workflow and
runtime. See AI workflows.

Durable package settings and continuity data are separated from disposable project
builds and caches. dockpipe clean --dry-run previews the project files that ordinary
clean would remove; durable package state stays outside that cleanup.

Install

Choose the release asset for your OS and CPU. Native downloads cover Linux amd64
and arm64, macOS Intel and Apple Silicon, and Windows x64. Package availability
does not imply that every distribution, provider or workflow has been qualified.

Native host steps need Bash; Git for Windows provides it on Windows. Docker
is needed for container workflows, not the host-only example below. Provider
CLIs and Git are needed by workflows that use them.

Linux

The installer selects a native CLI package for supported package-manager families,
or a portable archive, and verifies its downloads against the release checksums:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.14/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.14 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

For the desktop on Ubuntu 22.04 / 24.04 or Pop!_OS 22.04, download the matching
CLI and desktop DEBs from this release, verify them against SHA256SUMS.txt, then
install both:

sudo apt install ./dockpipe_0.6.14_amd64.deb ./dockpipe-desktop_0.6.14_amd64.deb

Use arm64 filenames on ARM64. Open Dockpipe from the application menu.
RPM, APK and Arch packages are CLI-only. The same desktop DEBs are installation-tested
on Ubuntu 22.04 and 24.04; that does not establish every downstream desktop setup.

macOS

Install the CLI for Intel or Apple Silicon:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.14/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.14 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

Desktop artifacts are named `dockpipe-desktop_0.6.14_da...

v0.6.13-staging.38358889476.1.cbb7af7c6a95

Dockpipe v0.6.13

Visit dockpipe.com for the Dockpipe website.

The 0.6.x release brings Dockpipe's workflow tools together in a desktop launcher
and a standalone CLI. Run your own project commands, add reusable workflows from
the Marketplace, select secret environments and try running selected work on
another machine. You can use the installed application without a Dockpipe source
checkout or Go compiler.

Maintenance update

The launcher shows package download and stored archive sizes in the Marketplace
and Installed views. Older catalogs without size information show an explicit
unavailable value instead of a misleading zero.

Remote-access setup now links directly to compatible provider packages in the
Marketplace and selects a newly installed provider when you return. Existing remote
addresses stay visible and pre-fill setup, with a review action for connections whose
provider details have not been recorded. Provider setup continues through the same
guided authentication, tunnel and connection checks used by the CLI.

Installation examples default to production. Website builds can select staging
download URLs, APT settings and Marketplace instructions explicitly, while keeping
staging-only Homebrew commands out of production pages. Maintainers can configure
an immediate Homebrew sync after successful staging publication; the tap retains
its native Mac checks and scheduled fallback before publishing package updates.

The Flatpak launcher now sets up the dockpipe terminal shortcut automatically
on first launch when no existing host command is found. Bash, Zsh and Fish receive
the missing PATH configuration; open a new terminal after launching Dockpipe.
Existing commands and conflicting shell configuration are preserved, with setup
failures shown in the launcher. Desktop sessions without a working tray keep the
window accessible, and a known harmless Qt Wayland warning is filtered narrowly.

Pipeon's desktop dependencies have been updated and its native clipboard bridge
is restricted to the configured local editor origin. Native builds and clipboard
access checks now run on Linux, macOS and Windows. Dependency update PRs target
dev for qualification before release; GitHub security updates still initially
target the repository's default branch.

Pipeon's Linux desktop shell includes a compatibility backport for the GLib
string-iterator vulnerability RUSTSEC-2024-0429, with an optimized regression test.
Cloud storage cache rules now honor publisher cache-control headers by default,
so mutable release catalogs can refresh without waiting for a forced CDN TTL.
Existing infrastructure requires applying the updated rules and purging old
mutable cache entries.

Release setup and cloud storage workflows now require your own repository, endpoint,
bucket and state settings. Personal environment identifiers and machine paths have
been replaced with placeholders. A public-content check guards source and package
archives against these configuration leaks. Official installation URLs are unchanged.

What's new

A desktop workspace for your workflows

The launcher brings Apps, Workflows, Machines and Activity into one
window. Save project contexts, choose a workflow and execution machine, start or
stop runs, and inspect progress and logs. The same workflows remain available from
the CLI for terminals, servers and CI.

Desktop installers include the launcher and matching CLI. Choose a CLI-only
installation when you do not need the desktop app.

Install the tools you need from the Marketplace

Open Packages → Marketplace to browse optional workflows and tool integrations.
Inspect their platform and dependencies, then install selected packages into your
user store. Downloads are checked against the catalog checksum. The Installed
view shows both user-installed and installer-managed packages.

Base installations include required core. Optional packages, their external tools
and provider sign-ins are separate. Removing an optional user package preserves its
data and settings. See using packages.

Create and reuse your own workflows

Use dockpipe init hello to create a workflow in your project, validate its YAML
before running it, and combine host commands, container steps and packaged
workflows. Host workflows can run without Docker when container preflight is
disabled; container workflows need a reachable engine.

Workflow outputs and reusable container image artifacts help connect steps and
avoid unnecessary image rebuilds. The first-workflow guide
starts with a small host command, then adds a container.

Select a secret environment for each run

Named environments bind selected secret values to workflow environment variables.
Adapters are available for 1Password Environments, AWS Secrets Manager,
Azure Key Vault and Infisical. Select a configured environment with
--secret-environment NAME; configuration stores references rather than secret
values. Existing 1Password vault templates remain supported.

Install and authenticate the matching provider CLI first. The 1Password adapter
requires an op build with op run --environment; AWS bindings currently require
string fields in a JSON secret. See secret environments
for setup and provider limits.

Remote workflow delivery — preview

Pair a worker using a verification code and explicit approval, without transferring
an invitation file or opening inbound SSH on the worker. Preview the selected
workflow sources, assets and package dependencies before submission, then inspect
job results and cancellation through the CLI or launcher.

Remote setup currently targets Linux and macOS. The Cloudflare Tunnel resolver
uses your own Cloudflare account and managed domain; workers connect outbound.
Use the same updated CLI on the broker and worker. Windows workers, a hosted
Dockpipe Cloud service and complete native Mac pairing/sleep-wake qualification
are not included in this release's verified remote experience. Start with
remote setup and limits.

Reusable AI workflows and persistent package data

Optional AI packages let you choose a provider, supply repeatable inputs and inspect
outputs. DorkPipe workflows can add task orchestration, model policies and review
steps. Provider accounts, authentication and any model charges remain separate;
available approval and isolation controls depend on the selected workflow and
runtime. See AI workflows.

Durable package settings and continuity data are separated from disposable project
builds and caches. dockpipe clean --dry-run previews the project files that ordinary
clean would remove; durable package state stays outside that cleanup.

Install

Choose the release asset for your OS and CPU. Native downloads cover Linux amd64
and arm64, macOS Intel and Apple Silicon, and Windows x64. Package availability
does not imply that every distribution, provider or workflow has been qualified.

Native host steps need Bash; Git for Windows provides it on Windows. Docker
is needed for container workflows, not the host-only example below. Provider
CLIs and Git are needed by workflows that use them.

Linux

The installer selects a native CLI package for supported package-manager families,
or a portable archive, and verifies its downloads against the release checksums:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.13/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.13 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

For the desktop on Ubuntu 22.04 / 24.04 or Pop!_OS 22.04, download the matching
CLI and desktop DEBs from this release, verify them against SHA256SUMS.txt, then
install both:

sudo apt install ./dockpipe_0.6.13_amd64.deb ./dockpipe-desktop_0.6.13_amd64.deb

Use arm64 filenames on ARM64. Open Dockpipe from the application menu.
RPM, APK and Arch packages are CLI-only. The same desktop DEBs are installation-tested
on Ubuntu 22.04 and 24.04; that does not establish every downstream desktop setup.

macOS

Install the CLI for Intel or Apple Silicon:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.13/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.13 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

Desktop artifacts are named dockpipe-desktop_0.6.13_darwin_arm64.dmg for Apple
Silicon and dockpipe-desktop_0.6.13_darwin_amd64.dmg for Intel, and require macOS 13
or newer. They contain Install Dockpipe.pkg for the app and CLI together.
Current desktop packaging is not Developer ID signed and notarized, so Gatekeeper
may block installation. Do not disable macOS security protections to install it.
Use one installation method; the DMG installer refuses an existing foreign CLI or app.

Windows

Download and run the installer in PowerShell:

$installer = Join-Path $env:TEMP 'dockpipe-install.ps1'
Invoke-WebRequest https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.13/install.ps1 -OutFile $installer
& $installer -Version 0.6.13 -SkipWSLSetup

The script verifies checksums and prefers the MSI when it is attached, with a
CLI-only ZIP fallback. The MSI includes the launcher by default; its interactive
installer lets you deselect that feature. Open a new terminal after installation.
WSL is optional and the command above skips its setup. Windows Authenticode signing
is n...

v0.6.12-staging.38347837443.1.06f33036ad16

Dockpipe v0.6.12

Visit dockpipe.com for the Dockpipe website.

The 0.6.x release brings Dockpipe's workflow tools together in a desktop launcher
and a standalone CLI. Run your own project commands, add reusable workflows from
the Marketplace, select secret environments and try running selected work on
another machine. You can use the installed application without a Dockpipe source
checkout or Go compiler.

Maintenance update

The launcher shows package download and stored archive sizes in the Marketplace
and Installed views. Older catalogs without size information show an explicit
unavailable value instead of a misleading zero.

Remote-access setup now links directly to compatible provider packages in the
Marketplace and selects a newly installed provider when you return. Existing remote
addresses stay visible and pre-fill setup, with a review action for connections whose
provider details have not been recorded. Provider setup continues through the same
guided authentication, tunnel and connection checks used by the CLI.

Installation examples default to production. Website builds can select staging
download URLs, APT settings and Marketplace instructions explicitly, while keeping
staging-only Homebrew commands out of production pages. Maintainers can configure
an immediate Homebrew sync after successful staging publication; the tap retains
its native Mac checks and scheduled fallback before publishing package updates.

The Flatpak launcher now sets up the dockpipe terminal shortcut automatically
on first launch when no existing host command is found. Bash, Zsh and Fish receive
the missing PATH configuration; open a new terminal after launching Dockpipe.
Existing commands and conflicting shell configuration are preserved, with setup
failures shown in the launcher. Desktop sessions without a working tray keep the
window accessible, and a known harmless Qt Wayland warning is filtered narrowly.

Pipeon's desktop dependencies have been updated and its native clipboard bridge
is restricted to the configured local editor origin. Native builds and clipboard
access checks now run on Linux, macOS and Windows. Dependency update PRs target
dev for qualification before release; GitHub security updates still initially
target the repository's default branch.

Pipeon's Linux desktop shell includes a compatibility backport for the GLib
string-iterator vulnerability RUSTSEC-2024-0429, with an optimized regression test.
Cloud storage cache rules now honor publisher cache-control headers by default,
so mutable release catalogs can refresh without waiting for a forced CDN TTL.
Existing infrastructure requires applying the updated rules and purging old
mutable cache entries.

Release setup and cloud storage workflows now require your own repository, endpoint,
bucket and state settings. Personal environment identifiers and machine paths have
been replaced with placeholders. A public-content check guards source and package
archives against these configuration leaks. Official installation URLs are unchanged.

What's new

A desktop workspace for your workflows

The launcher brings Apps, Workflows, Machines and Activity into one
window. Save project contexts, choose a workflow and execution machine, start or
stop runs, and inspect progress and logs. The same workflows remain available from
the CLI for terminals, servers and CI.

Desktop installers include the launcher and matching CLI. Choose a CLI-only
installation when you do not need the desktop app.

Install the tools you need from the Marketplace

Open Packages → Marketplace to browse optional workflows and tool integrations.
Inspect their platform and dependencies, then install selected packages into your
user store. Downloads are checked against the catalog checksum. The Installed
view shows both user-installed and installer-managed packages.

Base installations include required core. Optional packages, their external tools
and provider sign-ins are separate. Removing an optional user package preserves its
data and settings. See using packages.

Create and reuse your own workflows

Use dockpipe init hello to create a workflow in your project, validate its YAML
before running it, and combine host commands, container steps and packaged
workflows. Host workflows can run without Docker when container preflight is
disabled; container workflows need a reachable engine.

Workflow outputs and reusable container image artifacts help connect steps and
avoid unnecessary image rebuilds. The first-workflow guide
starts with a small host command, then adds a container.

Select a secret environment for each run

Named environments bind selected secret values to workflow environment variables.
Adapters are available for 1Password Environments, AWS Secrets Manager,
Azure Key Vault and Infisical. Select a configured environment with
--secret-environment NAME; configuration stores references rather than secret
values. Existing 1Password vault templates remain supported.

Install and authenticate the matching provider CLI first. The 1Password adapter
requires an op build with op run --environment; AWS bindings currently require
string fields in a JSON secret. See secret environments
for setup and provider limits.

Remote workflow delivery — preview

Pair a worker using a verification code and explicit approval, without transferring
an invitation file or opening inbound SSH on the worker. Preview the selected
workflow sources, assets and package dependencies before submission, then inspect
job results and cancellation through the CLI or launcher.

Remote setup currently targets Linux and macOS. The Cloudflare Tunnel resolver
uses your own Cloudflare account and managed domain; workers connect outbound.
Use the same updated CLI on the broker and worker. Windows workers, a hosted
Dockpipe Cloud service and complete native Mac pairing/sleep-wake qualification
are not included in this release's verified remote experience. Start with
remote setup and limits.

Reusable AI workflows and persistent package data

Optional AI packages let you choose a provider, supply repeatable inputs and inspect
outputs. DorkPipe workflows can add task orchestration, model policies and review
steps. Provider accounts, authentication and any model charges remain separate;
available approval and isolation controls depend on the selected workflow and
runtime. See AI workflows.

Durable package settings and continuity data are separated from disposable project
builds and caches. dockpipe clean --dry-run previews the project files that ordinary
clean would remove; durable package state stays outside that cleanup.

Install

Choose the release asset for your OS and CPU. Native downloads cover Linux amd64
and arm64, macOS Intel and Apple Silicon, and Windows x64. Package availability
does not imply that every distribution, provider or workflow has been qualified.

Native host steps need Bash; Git for Windows provides it on Windows. Docker
is needed for container workflows, not the host-only example below. Provider
CLIs and Git are needed by workflows that use them.

Linux

The installer selects a native CLI package for supported package-manager families,
or a portable archive, and verifies its downloads against the release checksums:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.12/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.12 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

For the desktop on Ubuntu 22.04 / 24.04 or Pop!_OS 22.04, download the matching
CLI and desktop DEBs from this release, verify them against SHA256SUMS.txt, then
install both:

sudo apt install ./dockpipe_0.6.12_amd64.deb ./dockpipe-desktop_0.6.12_amd64.deb

Use arm64 filenames on ARM64. Open Dockpipe from the application menu.
RPM, APK and Arch packages are CLI-only. The same desktop DEBs are installation-tested
on Ubuntu 22.04 and 24.04; that does not establish every downstream desktop setup.

macOS

Install the CLI for Intel or Apple Silicon:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.12/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.12 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

Desktop artifacts are named dockpipe-desktop_0.6.12_darwin_arm64.dmg for Apple
Silicon and dockpipe-desktop_0.6.12_darwin_amd64.dmg for Intel, and require macOS 13
or newer. They contain Install Dockpipe.pkg for the app and CLI together.
Current desktop packaging is not Developer ID signed and notarized, so Gatekeeper
may block installation. Do not disable macOS security protections to install it.
Use one installation method; the DMG installer refuses an existing foreign CLI or app.

Windows

Download and run the installer in PowerShell:

$installer = Join-Path $env:TEMP 'dockpipe-install.ps1'
Invoke-WebRequest https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.12/install.ps1 -OutFile $installer
& $installer -Version 0.6.12 -SkipWSLSetup

The script verifies checksums and prefers the MSI when it is attached, with a
CLI-only ZIP fallback. The MSI includes the launcher by default; its interactive
installer lets you deselect that feature. Open a new terminal after installation.
WSL is optional and the command above skips its setup. Windows Authenticode signing
is n...

v0.6.11

Dockpipe v0.6.11

Visit dockpipe.com for the Dockpipe website.

The 0.6.x release brings Dockpipe's workflow tools together in a desktop launcher
and a standalone CLI. Run your own project commands, add reusable workflows from
the Marketplace, select secret environments and try running selected work on
another machine. You can use the installed application without a Dockpipe source
checkout or Go compiler.

Maintenance update

The Flatpak launcher now sets up the dockpipe terminal shortcut automatically
on first launch when no existing host command is found. Bash, Zsh and Fish receive
the missing PATH configuration; open a new terminal after launching Dockpipe.
Existing commands and conflicting shell configuration are preserved, with setup
failures shown in the launcher. Desktop sessions without a working tray keep the
window accessible, and a known harmless Qt Wayland warning is filtered narrowly.

Pipeon's desktop dependencies have been updated and its native clipboard bridge
is restricted to the configured local editor origin. Native builds and clipboard
access checks now run on Linux, macOS and Windows. Dependency update PRs target
dev for qualification before release; GitHub security updates still initially
target the repository's default branch.

Pipeon's Linux desktop shell includes a compatibility backport for the GLib
string-iterator vulnerability RUSTSEC-2024-0429, with an optimized regression test.
Cloud storage cache rules now honor publisher cache-control headers by default,
so mutable release catalogs can refresh without waiting for a forced CDN TTL.
Existing infrastructure requires applying the updated rules and purging old
mutable cache entries.

Release setup and cloud storage workflows now require your own repository, endpoint,
bucket and state settings. Personal environment identifiers and machine paths have
been replaced with placeholders. A public-content check guards source and package
archives against these configuration leaks. Official installation URLs are unchanged.

What's new

A desktop workspace for your workflows

The launcher brings Apps, Workflows, Machines and Activity into one
window. Save project contexts, choose a workflow and execution machine, start or
stop runs, and inspect progress and logs. The same workflows remain available from
the CLI for terminals, servers and CI.

Desktop installers include the launcher and matching CLI. Choose a CLI-only
installation when you do not need the desktop app.

Install the tools you need from the Marketplace

Open Packages → Marketplace to browse optional workflows and tool integrations.
Inspect their platform and dependencies, then install selected packages into your
user store. Downloads are checked against the catalog checksum. The Installed
view shows both user-installed and installer-managed packages.

Base installations include required core. Optional packages, their external tools
and provider sign-ins are separate. Removing an optional user package preserves its
data and settings. See using packages.

Create and reuse your own workflows

Use dockpipe init hello to create a workflow in your project, validate its YAML
before running it, and combine host commands, container steps and packaged
workflows. Host workflows can run without Docker when container preflight is
disabled; container workflows need a reachable engine.

Workflow outputs and reusable container image artifacts help connect steps and
avoid unnecessary image rebuilds. The first-workflow guide
starts with a small host command, then adds a container.

Select a secret environment for each run

Named environments bind selected secret values to workflow environment variables.
Adapters are available for 1Password Environments, AWS Secrets Manager,
Azure Key Vault and Infisical. Select a configured environment with
--secret-environment NAME; configuration stores references rather than secret
values. Existing 1Password vault templates remain supported.

Install and authenticate the matching provider CLI first. The 1Password adapter
requires an op build with op run --environment; AWS bindings currently require
string fields in a JSON secret. See secret environments
for setup and provider limits.

Remote workflow delivery — preview

Pair a worker using a verification code and explicit approval, without transferring
an invitation file or opening inbound SSH on the worker. Preview the selected
workflow sources, assets and package dependencies before submission, then inspect
job results and cancellation through the CLI or launcher.

Remote setup currently targets Linux and macOS. The Cloudflare Tunnel resolver
uses your own Cloudflare account and managed domain; workers connect outbound.
Use the same updated CLI on the broker and worker. Windows workers, a hosted
Dockpipe Cloud service and complete native Mac pairing/sleep-wake qualification
are not included in this release's verified remote experience. Start with
remote setup and limits.

Reusable AI workflows and persistent package data

Optional AI packages let you choose a provider, supply repeatable inputs and inspect
outputs. DorkPipe workflows can add task orchestration, model policies and review
steps. Provider accounts, authentication and any model charges remain separate;
available approval and isolation controls depend on the selected workflow and
runtime. See AI workflows.

Durable package settings and continuity data are separated from disposable project
builds and caches. dockpipe clean --dry-run previews the project files that ordinary
clean would remove; durable package state stays outside that cleanup.

Install

Choose the release asset for your OS and CPU. Native downloads cover Linux amd64
and arm64, macOS Intel and Apple Silicon, and Windows x64. Package availability
does not imply that every distribution, provider or workflow has been qualified.

Native host steps need Bash; Git for Windows provides it on Windows. Docker
is needed for container workflows, not the host-only example below. Provider
CLIs and Git are needed by workflows that use them.

Linux

The installer selects a native CLI package for supported package-manager families,
or a portable archive, and verifies its downloads against the release checksums:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.11/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.11 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

For the desktop on Ubuntu 22.04 / 24.04 or Pop!_OS 22.04, download the matching
CLI and desktop DEBs from this release, verify them against SHA256SUMS.txt, then
install both:

sudo apt install ./dockpipe_0.6.11_amd64.deb ./dockpipe-desktop_0.6.11_amd64.deb

Use arm64 filenames on ARM64. Open Dockpipe from the application menu.
RPM, APK and Arch packages are CLI-only. The same desktop DEBs are installation-tested
on Ubuntu 22.04 and 24.04; that does not establish every downstream desktop setup.

macOS

Install the CLI for Intel or Apple Silicon:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.11/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.11 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

Desktop artifacts are named dockpipe-desktop_0.6.11_darwin_arm64.dmg for Apple
Silicon and dockpipe-desktop_0.6.11_darwin_amd64.dmg for Intel, and require macOS 13
or newer. They contain Install Dockpipe.pkg for the app and CLI together.
Current desktop packaging is not Developer ID signed and notarized, so Gatekeeper
may block installation. Do not disable macOS security protections to install it.
Use one installation method; the DMG installer refuses an existing foreign CLI or app.

Windows

Download and run the installer in PowerShell:

$installer = Join-Path $env:TEMP 'dockpipe-install.ps1'
Invoke-WebRequest https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.11/install.ps1 -OutFile $installer
& $installer -Version 0.6.11 -SkipWSLSetup

The script verifies checksums and prefers the MSI when it is attached, with a
CLI-only ZIP fallback. The MSI includes the launcher by default; its interactive
installer lets you deselect that feature. Open a new terminal after installation.
WSL is optional and the command above skips its setup. Windows Authenticode signing
is not yet part of the release packaging.

Staging channels and Flatpak

The installation guide
also documents the signed staging APT repository, staging Homebrew formula
and cask, and the Linux amd64 Flatpak preview. These are separate staging
choices; do not mix staging and production APT sources.

The Flatpak contains the launcher, CLI and core, requires KDE Platform 6.10, and
uses a matching Marketplace catalog. Get it from the staging package host using
the guide; do not assume it is attached to this GitHub release or listed on Flathub.
App updates require downloading and verifying a newer bundle. There is no ARM64
Flatpak catalog, and full Bazzite/Podman/SELinux qualification remains outstanding.

Try your first workflow

In a folder you own, run dockpipe init hello, then replace
workflows/hello/config.yml with:

name: hello
docker_preflight: false
steps:
  - id: greet
    kind: host
    ...

v0.6.10-staging.38324529693.1.b0c88abc124f

Dockpipe v0.6.10

Visit dockpipe.com for the Dockpipe website.

The 0.6.x release brings Dockpipe's workflow tools together in a desktop launcher
and a standalone CLI. Run your own project commands, add reusable workflows from
the Marketplace, select secret environments and try running selected work on
another machine. You can use the installed application without a Dockpipe source
checkout or Go compiler.

Maintenance update

The Flatpak launcher now sets up the dockpipe terminal shortcut automatically
on first launch when no existing host command is found. Bash, Zsh and Fish receive
the missing PATH configuration; open a new terminal after launching Dockpipe.
Existing commands and conflicting shell configuration are preserved, with setup
failures shown in the launcher. Desktop sessions without a working tray keep the
window accessible, and a known harmless Qt Wayland warning is filtered narrowly.

Pipeon's desktop dependencies have been updated and its native clipboard bridge
is restricted to the configured local editor origin. Native builds and clipboard
access checks now run on Linux, macOS and Windows. Dependency update PRs target
dev for qualification before release; GitHub security updates still initially
target the repository's default branch.

Pipeon's Linux desktop shell includes a compatibility backport for the GLib
string-iterator vulnerability RUSTSEC-2024-0429, with an optimized regression test.
Cloud storage cache rules now honor publisher cache-control headers by default,
so mutable release catalogs can refresh without waiting for a forced CDN TTL.
Existing infrastructure requires applying the updated rules and purging old
mutable cache entries.

Release setup and cloud storage workflows now require your own repository, endpoint,
bucket and state settings. Personal environment identifiers and machine paths have
been replaced with placeholders. A public-content check guards source and package
archives against these configuration leaks. Official installation URLs are unchanged.

What's new

A desktop workspace for your workflows

The launcher brings Apps, Workflows, Machines and Activity into one
window. Save project contexts, choose a workflow and execution machine, start or
stop runs, and inspect progress and logs. The same workflows remain available from
the CLI for terminals, servers and CI.

Desktop installers include the launcher and matching CLI. Choose a CLI-only
installation when you do not need the desktop app.

Install the tools you need from the Marketplace

Open Packages → Marketplace to browse optional workflows and tool integrations.
Inspect their platform and dependencies, then install selected packages into your
user store. Downloads are checked against the catalog checksum. The Installed
view shows both user-installed and installer-managed packages.

Base installations include required core. Optional packages, their external tools
and provider sign-ins are separate. Removing an optional user package preserves its
data and settings. See using packages.

Create and reuse your own workflows

Use dockpipe init hello to create a workflow in your project, validate its YAML
before running it, and combine host commands, container steps and packaged
workflows. Host workflows can run without Docker when container preflight is
disabled; container workflows need a reachable engine.

Workflow outputs and reusable container image artifacts help connect steps and
avoid unnecessary image rebuilds. The first-workflow guide
starts with a small host command, then adds a container.

Select a secret environment for each run

Named environments bind selected secret values to workflow environment variables.
Adapters are available for 1Password Environments, AWS Secrets Manager,
Azure Key Vault and Infisical. Select a configured environment with
--secret-environment NAME; configuration stores references rather than secret
values. Existing 1Password vault templates remain supported.

Install and authenticate the matching provider CLI first. The 1Password adapter
requires an op build with op run --environment; AWS bindings currently require
string fields in a JSON secret. See secret environments
for setup and provider limits.

Remote workflow delivery — preview

Pair a worker using a verification code and explicit approval, without transferring
an invitation file or opening inbound SSH on the worker. Preview the selected
workflow sources, assets and package dependencies before submission, then inspect
job results and cancellation through the CLI or launcher.

Remote setup currently targets Linux and macOS. The Cloudflare Tunnel resolver
uses your own Cloudflare account and managed domain; workers connect outbound.
Use the same updated CLI on the broker and worker. Windows workers, a hosted
Dockpipe Cloud service and complete native Mac pairing/sleep-wake qualification
are not included in this release's verified remote experience. Start with
remote setup and limits.

Reusable AI workflows and persistent package data

Optional AI packages let you choose a provider, supply repeatable inputs and inspect
outputs. DorkPipe workflows can add task orchestration, model policies and review
steps. Provider accounts, authentication and any model charges remain separate;
available approval and isolation controls depend on the selected workflow and
runtime. See AI workflows.

Durable package settings and continuity data are separated from disposable project
builds and caches. dockpipe clean --dry-run previews the project files that ordinary
clean would remove; durable package state stays outside that cleanup.

Install

Choose the release asset for your OS and CPU. Native downloads cover Linux amd64
and arm64, macOS Intel and Apple Silicon, and Windows x64. Package availability
does not imply that every distribution, provider or workflow has been qualified.

Native host steps need Bash; Git for Windows provides it on Windows. Docker
is needed for container workflows, not the host-only example below. Provider
CLIs and Git are needed by workflows that use them.

Linux

The installer selects a native CLI package for supported package-manager families,
or a portable archive, and verifies its downloads against the release checksums:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.10/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.10 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

For the desktop on Ubuntu 22.04 / 24.04 or Pop!_OS 22.04, download the matching
CLI and desktop DEBs from this release, verify them against SHA256SUMS.txt, then
install both:

sudo apt install ./dockpipe_0.6.10_amd64.deb ./dockpipe-desktop_0.6.10_amd64.deb

Use arm64 filenames on ARM64. Open Dockpipe from the application menu.
RPM, APK and Arch packages are CLI-only. The same desktop DEBs are installation-tested
on Ubuntu 22.04 and 24.04; that does not establish every downstream desktop setup.

macOS

Install the CLI for Intel or Apple Silicon:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.10/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.10 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

Desktop artifacts are named dockpipe-desktop_0.6.10_darwin_arm64.dmg for Apple
Silicon and dockpipe-desktop_0.6.10_darwin_amd64.dmg for Intel, and require macOS 13
or newer. They contain Install Dockpipe.pkg for the app and CLI together.
Current desktop packaging is not Developer ID signed and notarized, so Gatekeeper
may block installation. Do not disable macOS security protections to install it.
Use one installation method; the DMG installer refuses an existing foreign CLI or app.

Windows

Download and run the installer in PowerShell:

$installer = Join-Path $env:TEMP 'dockpipe-install.ps1'
Invoke-WebRequest https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.10/install.ps1 -OutFile $installer
& $installer -Version 0.6.10 -SkipWSLSetup

The script verifies checksums and prefers the MSI when it is attached, with a
CLI-only ZIP fallback. The MSI includes the launcher by default; its interactive
installer lets you deselect that feature. Open a new terminal after installation.
WSL is optional and the command above skips its setup. Windows Authenticode signing
is not yet part of the release packaging.

Staging channels and Flatpak

The installation guide
also documents the signed staging APT repository, staging Homebrew formula
and cask, and the Linux amd64 Flatpak preview. These are separate staging
choices; do not mix staging and production APT sources.

The Flatpak contains the launcher, CLI and core, requires KDE Platform 6.10, and
uses a matching Marketplace catalog. Get it from the staging package host using
the guide; do not assume it is attached to this GitHub release or listed on Flathub.
App updates require downloading and verifying a newer bundle. There is no ARM64
Flatpak catalog, and full Bazzite/Podman/SELinux qualification remains outstanding.

Try your first workflow

In a folder you own, run dockpipe init hello, then replace
workflows/hello/config.yml with:

name: hello
docker_preflight: false
steps:
  - id: greet
    kind: host
    ...

v0.6.9

Dockpipe v0.6.9

Visit dockpipe.com for the Dockpipe website.

The 0.6.x release brings Dockpipe's workflow tools together in a desktop launcher
and a standalone CLI. Run your own project commands, add reusable workflows from
the Marketplace, select secret environments and try running selected work on
another machine. You can use the installed application without a Dockpipe source
checkout or Go compiler.

Maintenance update

The Flatpak launcher now sets up the dockpipe terminal shortcut automatically
on first launch when no existing host command is found. Bash, Zsh and Fish receive
the missing PATH configuration; open a new terminal after launching Dockpipe.
Existing commands and conflicting shell configuration are preserved, with setup
failures shown in the launcher. Desktop sessions without a working tray keep the
window accessible, and a known harmless Qt Wayland warning is filtered narrowly.

Pipeon's desktop dependencies have been updated and its native clipboard bridge
is restricted to the configured local editor origin. Native builds and clipboard
access checks now run on Linux, macOS and Windows. Dependency update PRs target
dev for qualification before release; GitHub security updates still initially
target the repository's default branch.

Release setup and cloud storage workflows now require your own repository, endpoint,
bucket and state settings. Personal environment identifiers and machine paths have
been replaced with placeholders. A public-content check guards source and package
archives against these configuration leaks. Official installation URLs are unchanged.

What's new

A desktop workspace for your workflows

The launcher brings Apps, Workflows, Machines and Activity into one
window. Save project contexts, choose a workflow and execution machine, start or
stop runs, and inspect progress and logs. The same workflows remain available from
the CLI for terminals, servers and CI.

Desktop installers include the launcher and matching CLI. Choose a CLI-only
installation when you do not need the desktop app.

Install the tools you need from the Marketplace

Open Packages → Marketplace to browse optional workflows and tool integrations.
Inspect their platform and dependencies, then install selected packages into your
user store. Downloads are checked against the catalog checksum. The Installed
view shows both user-installed and installer-managed packages.

Base installations include required core. Optional packages, their external tools
and provider sign-ins are separate. Removing an optional user package preserves its
data and settings. See using packages.

Create and reuse your own workflows

Use dockpipe init hello to create a workflow in your project, validate its YAML
before running it, and combine host commands, container steps and packaged
workflows. Host workflows can run without Docker when container preflight is
disabled; container workflows need a reachable engine.

Workflow outputs and reusable container image artifacts help connect steps and
avoid unnecessary image rebuilds. The first-workflow guide
starts with a small host command, then adds a container.

Select a secret environment for each run

Named environments bind selected secret values to workflow environment variables.
Adapters are available for 1Password Environments, AWS Secrets Manager,
Azure Key Vault and Infisical. Select a configured environment with
--secret-environment NAME; configuration stores references rather than secret
values. Existing 1Password vault templates remain supported.

Install and authenticate the matching provider CLI first. The 1Password adapter
requires an op build with op run --environment; AWS bindings currently require
string fields in a JSON secret. See secret environments
for setup and provider limits.

Remote workflow delivery — preview

Pair a worker using a verification code and explicit approval, without transferring
an invitation file or opening inbound SSH on the worker. Preview the selected
workflow sources, assets and package dependencies before submission, then inspect
job results and cancellation through the CLI or launcher.

Remote setup currently targets Linux and macOS. The Cloudflare Tunnel resolver
uses your own Cloudflare account and managed domain; workers connect outbound.
Use the same updated CLI on the broker and worker. Windows workers, a hosted
Dockpipe Cloud service and complete native Mac pairing/sleep-wake qualification
are not included in this release's verified remote experience. Start with
remote setup and limits.

Reusable AI workflows and persistent package data

Optional AI packages let you choose a provider, supply repeatable inputs and inspect
outputs. DorkPipe workflows can add task orchestration, model policies and review
steps. Provider accounts, authentication and any model charges remain separate;
available approval and isolation controls depend on the selected workflow and
runtime. See AI workflows.

Durable package settings and continuity data are separated from disposable project
builds and caches. dockpipe clean --dry-run previews the project files that ordinary
clean would remove; durable package state stays outside that cleanup.

Install

Choose the release asset for your OS and CPU. Native downloads cover Linux amd64
and arm64, macOS Intel and Apple Silicon, and Windows x64. Package availability
does not imply that every distribution, provider or workflow has been qualified.

Native host steps need Bash; Git for Windows provides it on Windows. Docker
is needed for container workflows, not the host-only example below. Provider
CLIs and Git are needed by workflows that use them.

Linux

The installer selects a native CLI package for supported package-manager families,
or a portable archive, and verifies its downloads against the release checksums:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.9/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.9 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

For the desktop on Ubuntu 22.04 / 24.04 or Pop!_OS 22.04, download the matching
CLI and desktop DEBs from this release, verify them against SHA256SUMS.txt, then
install both:

sudo apt install ./dockpipe_0.6.9_amd64.deb ./dockpipe-desktop_0.6.9_amd64.deb

Use arm64 filenames on ARM64. Open Dockpipe from the application menu.
RPM, APK and Arch packages are CLI-only. The same desktop DEBs are installation-tested
on Ubuntu 22.04 and 24.04; that does not establish every downstream desktop setup.

macOS

Install the CLI for Intel or Apple Silicon:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.9/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.9 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

Desktop artifacts are named dockpipe-desktop_0.6.9_darwin_arm64.dmg for Apple
Silicon and dockpipe-desktop_0.6.9_darwin_amd64.dmg for Intel, and require macOS 13
or newer. They contain Install Dockpipe.pkg for the app and CLI together.
Current desktop packaging is not Developer ID signed and notarized, so Gatekeeper
may block installation. Do not disable macOS security protections to install it.
Use one installation method; the DMG installer refuses an existing foreign CLI or app.

Windows

Download and run the installer in PowerShell:

$installer = Join-Path $env:TEMP 'dockpipe-install.ps1'
Invoke-WebRequest https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.9/install.ps1 -OutFile $installer
& $installer -Version 0.6.9 -SkipWSLSetup

The script verifies checksums and prefers the MSI when it is attached, with a
CLI-only ZIP fallback. The MSI includes the launcher by default; its interactive
installer lets you deselect that feature. Open a new terminal after installation.
WSL is optional and the command above skips its setup. Windows Authenticode signing
is not yet part of the release packaging.

Staging channels and Flatpak

The installation guide
also documents the signed staging APT repository, staging Homebrew formula
and cask, and the Linux amd64 Flatpak preview. These are separate staging
choices; do not mix staging and production APT sources.

The Flatpak contains the launcher, CLI and core, requires KDE Platform 6.10, and
uses a matching Marketplace catalog. Get it from the staging package host using
the guide; do not assume it is attached to this GitHub release or listed on Flathub.
App updates require downloading and verifying a newer bundle. There is no ARM64
Flatpak catalog, and full Bazzite/Podman/SELinux qualification remains outstanding.

Try your first workflow

In a folder you own, run dockpipe init hello, then replace
workflows/hello/config.yml with:

name: hello
docker_preflight: false
steps:
  - id: greet
    kind: host
    cmd: printf 'Hello from Dockpipe!\n'

Validate and run it:

dockpipe --version
dockpipe workflow validate workflows/hello/config.yml
dockpipe --workflow hello --

This prints Hello from Dockpipe! and needs no container engine. For Flatpak,
replace dockpipe with flatpak run --command=dockpipe com.dockpipe.Dockpipe.

Upgrading and known limits

• Moving from 0.5.x: install the matching native application an...

v0.6.8-staging.38309329321.1.9ff64e91c254

Dockpipe v0.6.8

Visit dockpipe.com for the Dockpipe website.

The 0.6.x release brings Dockpipe's workflow tools together in a desktop launcher
and a standalone CLI. Run your own project commands, add reusable workflows from
the Marketplace, select secret environments and try running selected work on
another machine. You can use the installed application without a Dockpipe source
checkout or Go compiler.

Maintenance update

The Flatpak launcher now sets up the dockpipe terminal shortcut automatically
on first launch when no existing host command is found. Bash, Zsh and Fish receive
the missing PATH configuration; open a new terminal after launching Dockpipe.
Existing commands and conflicting shell configuration are preserved, with setup
failures shown in the launcher. Desktop sessions without a working tray keep the
window accessible, and a known harmless Qt Wayland warning is filtered narrowly.

Pipeon's desktop dependencies have been updated and its native clipboard bridge
is restricted to the configured local editor origin. Native builds and clipboard
access checks now run on Linux, macOS and Windows. Dependency update PRs target
dev for qualification before release; GitHub security updates still initially
target the repository's default branch.

Release setup and cloud storage workflows now require your own repository, endpoint,
bucket and state settings. Personal environment identifiers and machine paths have
been replaced with placeholders. A public-content check guards source and package
archives against these configuration leaks. Official installation URLs are unchanged.

What's new

A desktop workspace for your workflows

The launcher brings Apps, Workflows, Machines and Activity into one
window. Save project contexts, choose a workflow and execution machine, start or
stop runs, and inspect progress and logs. The same workflows remain available from
the CLI for terminals, servers and CI.

Desktop installers include the launcher and matching CLI. Choose a CLI-only
installation when you do not need the desktop app.

Install the tools you need from the Marketplace

Open Packages → Marketplace to browse optional workflows and tool integrations.
Inspect their platform and dependencies, then install selected packages into your
user store. Downloads are checked against the catalog checksum. The Installed
view shows both user-installed and installer-managed packages.

Base installations include required core. Optional packages, their external tools
and provider sign-ins are separate. Removing an optional user package preserves its
data and settings. See using packages.

Create and reuse your own workflows

Use dockpipe init hello to create a workflow in your project, validate its YAML
before running it, and combine host commands, container steps and packaged
workflows. Host workflows can run without Docker when container preflight is
disabled; container workflows need a reachable engine.

Workflow outputs and reusable container image artifacts help connect steps and
avoid unnecessary image rebuilds. The first-workflow guide
starts with a small host command, then adds a container.

Select a secret environment for each run

Named environments bind selected secret values to workflow environment variables.
Adapters are available for 1Password Environments, AWS Secrets Manager,
Azure Key Vault and Infisical. Select a configured environment with
--secret-environment NAME; configuration stores references rather than secret
values. Existing 1Password vault templates remain supported.

Install and authenticate the matching provider CLI first. The 1Password adapter
requires an op build with op run --environment; AWS bindings currently require
string fields in a JSON secret. See secret environments
for setup and provider limits.

Remote workflow delivery — preview

Pair a worker using a verification code and explicit approval, without transferring
an invitation file or opening inbound SSH on the worker. Preview the selected
workflow sources, assets and package dependencies before submission, then inspect
job results and cancellation through the CLI or launcher.

Remote setup currently targets Linux and macOS. The Cloudflare Tunnel resolver
uses your own Cloudflare account and managed domain; workers connect outbound.
Use the same updated CLI on the broker and worker. Windows workers, a hosted
Dockpipe Cloud service and complete native Mac pairing/sleep-wake qualification
are not included in this release's verified remote experience. Start with
remote setup and limits.

Reusable AI workflows and persistent package data

Optional AI packages let you choose a provider, supply repeatable inputs and inspect
outputs. DorkPipe workflows can add task orchestration, model policies and review
steps. Provider accounts, authentication and any model charges remain separate;
available approval and isolation controls depend on the selected workflow and
runtime. See AI workflows.

Durable package settings and continuity data are separated from disposable project
builds and caches. dockpipe clean --dry-run previews the project files that ordinary
clean would remove; durable package state stays outside that cleanup.

Install

Choose the release asset for your OS and CPU. Native downloads cover Linux amd64
and arm64, macOS Intel and Apple Silicon, and Windows x64. Package availability
does not imply that every distribution, provider or workflow has been qualified.

Native host steps need Bash; Git for Windows provides it on Windows. Docker
is needed for container workflows, not the host-only example below. Provider
CLIs and Git are needed by workflows that use them.

Linux

The installer selects a native CLI package for supported package-manager families,
or a portable archive, and verifies its downloads against the release checksums:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.8/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.8 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

For the desktop on Ubuntu 22.04 / 24.04 or Pop!_OS 22.04, download the matching
CLI and desktop DEBs from this release, verify them against SHA256SUMS.txt, then
install both:

sudo apt install ./dockpipe_0.6.8_amd64.deb ./dockpipe-desktop_0.6.8_amd64.deb

Use arm64 filenames on ARM64. Open Dockpipe from the application menu.
RPM, APK and Arch packages are CLI-only. The same desktop DEBs are installation-tested
on Ubuntu 22.04 and 24.04; that does not establish every downstream desktop setup.

macOS

Install the CLI for Intel or Apple Silicon:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.8/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.8 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

Desktop artifacts are named dockpipe-desktop_0.6.8_darwin_arm64.dmg for Apple
Silicon and dockpipe-desktop_0.6.8_darwin_amd64.dmg for Intel, and require macOS 13
or newer. They contain Install Dockpipe.pkg for the app and CLI together.
Current desktop packaging is not Developer ID signed and notarized, so Gatekeeper
may block installation. Do not disable macOS security protections to install it.
Use one installation method; the DMG installer refuses an existing foreign CLI or app.

Windows

Download and run the installer in PowerShell:

$installer = Join-Path $env:TEMP 'dockpipe-install.ps1'
Invoke-WebRequest https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.8/install.ps1 -OutFile $installer
& $installer -Version 0.6.8 -SkipWSLSetup

The script verifies checksums and prefers the MSI when it is attached, with a
CLI-only ZIP fallback. The MSI includes the launcher by default; its interactive
installer lets you deselect that feature. Open a new terminal after installation.
WSL is optional and the command above skips its setup. Windows Authenticode signing
is not yet part of the release packaging.

Staging channels and Flatpak

The installation guide
also documents the signed staging APT repository, staging Homebrew formula
and cask, and the Linux amd64 Flatpak preview. These are separate staging
choices; do not mix staging and production APT sources.

The Flatpak contains the launcher, CLI and core, requires KDE Platform 6.10, and
uses a matching Marketplace catalog. Get it from the staging package host using
the guide; do not assume it is attached to this GitHub release or listed on Flathub.
App updates require downloading and verifying a newer bundle. There is no ARM64
Flatpak catalog, and full Bazzite/Podman/SELinux qualification remains outstanding.

Try your first workflow

In a folder you own, run dockpipe init hello, then replace
workflows/hello/config.yml with:

name: hello
docker_preflight: false
steps:
  - id: greet
    kind: host
    cmd: printf 'Hello from Dockpipe!\n'

Validate and run it:

dockpipe --version
dockpipe workflow validate workflows/hello/config.yml
dockpipe --workflow hello --

This prints Hello from Dockpipe! and needs no container engine. For Flatpak,
replace dockpipe with flatpak run --command=dockpipe com.dockpipe.Dockpipe.

Upgrading and known limits

• Moving from 0.5.x: install the matching native application an...

v0.6.7-staging.38287365063.1.3382b63c54b3

Dockpipe v0.6.7

Visit dockpipe.com for the Dockpipe website.

The 0.6.x release brings Dockpipe's workflow tools together in a desktop launcher
and a standalone CLI. Run your own project commands, add reusable workflows from
the Marketplace, select secret environments and try running selected work on
another machine. You can use the installed application without a Dockpipe source
checkout or Go compiler.

Maintenance update

Release setup and cloud storage workflows now require your own repository, endpoint,
bucket and state settings. Personal environment identifiers and machine paths have
been replaced with placeholders. A public-content check guards source and package
archives against these configuration leaks. Official installation URLs are unchanged.

What's new

A desktop workspace for your workflows

The launcher brings Apps, Workflows, Machines and Activity into one
window. Save project contexts, choose a workflow and execution machine, start or
stop runs, and inspect progress and logs. The same workflows remain available from
the CLI for terminals, servers and CI.

Desktop installers include the launcher and matching CLI. Choose a CLI-only
installation when you do not need the desktop app.

Install the tools you need from the Marketplace

Open Packages → Marketplace to browse optional workflows and tool integrations.
Inspect their platform and dependencies, then install selected packages into your
user store. Downloads are checked against the catalog checksum. The Installed
view shows both user-installed and installer-managed packages.

Base installations include required core. Optional packages, their external tools
and provider sign-ins are separate. Removing an optional user package preserves its
data and settings. See using packages.

Create and reuse your own workflows

Use dockpipe init hello to create a workflow in your project, validate its YAML
before running it, and combine host commands, container steps and packaged
workflows. Host workflows can run without Docker when container preflight is
disabled; container workflows need a reachable engine.

Workflow outputs and reusable container image artifacts help connect steps and
avoid unnecessary image rebuilds. The first-workflow guide
starts with a small host command, then adds a container.

Select a secret environment for each run

Named environments bind selected secret values to workflow environment variables.
Adapters are available for 1Password Environments, AWS Secrets Manager,
Azure Key Vault and Infisical. Select a configured environment with
--secret-environment NAME; configuration stores references rather than secret
values. Existing 1Password vault templates remain supported.

Install and authenticate the matching provider CLI first. The 1Password adapter
requires an op build with op run --environment; AWS bindings currently require
string fields in a JSON secret. See secret environments
for setup and provider limits.

Remote workflow delivery — preview

Pair a worker using a verification code and explicit approval, without transferring
an invitation file or opening inbound SSH on the worker. Preview the selected
workflow sources, assets and package dependencies before submission, then inspect
job results and cancellation through the CLI or launcher.

Remote setup currently targets Linux and macOS. The Cloudflare Tunnel resolver
uses your own Cloudflare account and managed domain; workers connect outbound.
Use the same updated CLI on the broker and worker. Windows workers, a hosted
Dockpipe Cloud service and complete native Mac pairing/sleep-wake qualification
are not included in this release's verified remote experience. Start with
remote setup and limits.

Reusable AI workflows and persistent package data

Optional AI packages let you choose a provider, supply repeatable inputs and inspect
outputs. DorkPipe workflows can add task orchestration, model policies and review
steps. Provider accounts, authentication and any model charges remain separate;
available approval and isolation controls depend on the selected workflow and
runtime. See AI workflows.

Durable package settings and continuity data are separated from disposable project
builds and caches. dockpipe clean --dry-run previews the project files that ordinary
clean would remove; durable package state stays outside that cleanup.

Install

Choose the release asset for your OS and CPU. Native downloads cover Linux amd64
and arm64, macOS Intel and Apple Silicon, and Windows x64. Package availability
does not imply that every distribution, provider or workflow has been qualified.

Native host steps need Bash; Git for Windows provides it on Windows. Docker
is needed for container workflows, not the host-only example below. Provider
CLIs and Git are needed by workflows that use them.

Linux

The installer selects a native CLI package for supported package-manager families,
or a portable archive, and verifies its downloads against the release checksums:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.7/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.7 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

For the desktop on Ubuntu 22.04 / 24.04 or Pop!_OS 22.04, download the matching
CLI and desktop DEBs from this release, verify them against SHA256SUMS.txt, then
install both:

sudo apt install ./dockpipe_0.6.7_amd64.deb ./dockpipe-desktop_0.6.7_amd64.deb

Use arm64 filenames on ARM64. Open Dockpipe from the application menu.
RPM, APK and Arch packages are CLI-only. The same desktop DEBs are installation-tested
on Ubuntu 22.04 and 24.04; that does not establish every downstream desktop setup.

macOS

Install the CLI for Intel or Apple Silicon:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.7/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.7 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

Desktop artifacts are named dockpipe-desktop_0.6.7_darwin_arm64.dmg for Apple
Silicon and dockpipe-desktop_0.6.7_darwin_amd64.dmg for Intel, and require macOS 13
or newer. They contain Install Dockpipe.pkg for the app and CLI together.
Current desktop packaging is not Developer ID signed and notarized, so Gatekeeper
may block installation. Do not disable macOS security protections to install it.
Use one installation method; the DMG installer refuses an existing foreign CLI or app.

Windows

Download and run the installer in PowerShell:

$installer = Join-Path $env:TEMP 'dockpipe-install.ps1'
Invoke-WebRequest https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.7/install.ps1 -OutFile $installer
& $installer -Version 0.6.7 -SkipWSLSetup

The script verifies checksums and prefers the MSI when it is attached, with a
CLI-only ZIP fallback. The MSI includes the launcher by default; its interactive
installer lets you deselect that feature. Open a new terminal after installation.
WSL is optional and the command above skips its setup. Windows Authenticode signing
is not yet part of the release packaging.

Staging channels and Flatpak

The installation guide
also documents the signed staging APT repository, staging Homebrew formula
and cask, and the Linux amd64 Flatpak preview. These are separate staging
choices; do not mix staging and production APT sources.

The Flatpak contains the launcher, CLI and core, requires KDE Platform 6.10, and
uses a matching Marketplace catalog. Get it from the staging package host using
the guide; do not assume it is attached to this GitHub release or listed on Flathub.
App updates require downloading and verifying a newer bundle. There is no ARM64
Flatpak catalog, and full Bazzite/Podman/SELinux qualification remains outstanding.

Try your first workflow

In a folder you own, run dockpipe init hello, then replace
workflows/hello/config.yml with:

name: hello
docker_preflight: false
steps:
  - id: greet
    kind: host
    cmd: printf 'Hello from Dockpipe!\n'

Validate and run it:

dockpipe --version
dockpipe workflow validate workflows/hello/config.yml
dockpipe --workflow hello --

This prints Hello from Dockpipe! and needs no container engine. For Flatpak,
replace dockpipe with flatpak run --command=dockpipe com.dockpipe.Dockpipe.

Upgrading and known limits

• Moving from 0.5.x: install the matching native application and core, then
  review the workflow guide
  and install the optional packages your workflows use. --workflow selects a
  workflow; --template remains a compatibility alias for the low-level image
  override and is not an interchangeable workflow selector.
• Existing package data: keep legacy data until its migration has succeeded.
  Inspect dockpipe clean --dry-run before cleanup: ordinary clean removes the
  entire disposable bin/.dockpipe/ tree. Back up project and package data before
  upgrading; do not assume everything inside an older generated directory is
  expendable.
• Remote provider name: new Cloudflare setup uses
  dockpipe.cloudflare.remote-edge. Existing cloudflare resolver installations
  are not rename...