pickfit

BrowseDeveloper CLIs

darkubectl

Terminal CLI to list, inspect, tail logs, shell into and create Darkube apps.

Tested on macOS and Linux

Use it

macOS arm64

You need first

  • Keys or accounts: Darkube API key
  1. Install darkubectl via Homebrew tap rahacloud/tap/darkubectl

    brew install rahacloud/tap/darkubectl
    

Check that it works

darkubectl --version

The output should contain “darkubectl version 0.13.0”.

First thing to try

darkubectl completion bash

Run darkubectl in a terminal to see the available commands.

Linux x86_64

You need first

  • Keys or accounts: Darkube API key
  1. Download darkubectl tarball

    mkdir -p ~/.local/bin /tmp/darku && curl -sSfL https://github.com/rahacloud/darkubectl/releases/download/v0.13.0/darkubectl_0.13.0_linux_amd64.tar.gz -o /tmp/darku/darkubectl.tar.gz
  2. Extract and install darkubectl binary

    tar xzf /tmp/darku/darkubectl.tar.gz -C /tmp/darku && install /tmp/darku/darkubectl ~/.local/bin/darkubectl

Check that it works

darkubectl --version

The output should contain “darkubectl version 0.13.0”.

First thing to try

darkubectl completion bash

Run darkubectl in a terminal to see the available commands.

What it does

  • List, inspect and create apps from the terminal
    Not tested
  • Tail and follow app logs
    Not tested
  • Open an interactive shell in an app
    Not tested
  • Find orphaned Helm releases
    Not tested

How far pickfit got

macOS arm64

  1. Installs
  2. Starts
  3. 0 of 4 features work
  4. Works offline

Linux x86_64

  1. Installs
  2. Starts
  3. 0 of 4 features work
  4. Works offline

Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • list apps from the terminal
  • tail app logs
  • open interactive shell in app
  • find orphaned Helm releases
  • create app from Docker image

An alternative to kubectl.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

macOS arm64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version 0.13.0

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.13.0

Differences the test machine hit

  • README: Binary install ends with `sudo install darkubectl /usr/local/bin/`
    In the test: Installed to ~/.local/bin/darkubectl without sudo (no root in box).

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.