Ext Ops Panel
Open dashboard
Comparison

cyberian-control vs Harness

cyberian-control is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.

cyberian-control is a plugin bundle for AI coding tools published by contextualizer-ai. No marketplace we read lists it any more. Harness is an MCP server published by harness.autonomous.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacecyberian-controlHarness
Community marketplace contextualizer-ai/cyberian Removed on 2026-10-20
Version: not stated
Forks (GitHub): 1
Stars (GitHub): 5
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.20
Forks (GitHub): 125
Stars (GitHub): 1 362
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

cyberian-control vs Harness
Factcyberian-controlno longer listed · Harness
Marketplaces that list it (differs)01
Stars (GitHub) (differs)51 362
Forks (GitHub) (differs)1125
Last release (differs)Not published2026-10-19
Where it runs (differs)Installs as a plugin bundleOn your machine (@autonomous-ai/harness-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/contextualizer-ai/cyberiangithub.com/autonomous-ai/openharness
Changes in the last 7 days (differs)23
First seen (differs)2026-10-152026-10-19

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of cyberian-control

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • ccam-runner

    Operate dashboard-launched Claude Code and Codex runs with safe launch, follow-up, stop, resume, model discovery, and persistent run-history workflows.

    by Son Nguyen · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • ai-cli

    CLI tool for running Claude Code SDK sessions with configurable modes

    by Silas Rhyneer · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • daymade-claude-code

    Claude Code operations suite that bundles cross-project prior-work retrieval across code, docs, Skills, meetings, WeChat archives, and conversation history; provider-separated…

    by daymade · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • claude-code-tools

    Meta-tools for running Claude Code well: audit your permission allowlist, fix local toolchain gaps, analyze usage costs, and prune stale saved memories.

    by Fin 2x · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • linker

    Bridge multiple Claude Code instances together — share context, send messages, ask and answer questions across sessions without copy-pasting

    by nautilux2 · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • claude-army io.github.robbhimself-1337/claude-army

    Orchestrate multiple Claude Code agents in parallel from chat

    by robbhimself-1337 · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

cyberian-control

In its own words, on Community GitHub marketplaces:

Control and coordinate multiple Claude Code sessions via cyberian's agentapi wrapper

Harness

In its own words, on Official MCP Registry:

Start Claude Code and Codex agents the person can watch, wait for them and read their answers.

How to run each

cyberian-control

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Harness As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio harness -- npx -y @autonomous-ai/harness-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: cyberian-control · What it can do: Harness · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built