cyborgy 0.1.24

Extend the claude and codex CLIs: skills marketplace, memory, and extension APIs via the Cyborgy MCP.

Cyborgy CLI

cyborgy extends coding-agent CLIs such as Claude Code and Codex with the Cyborgy MCP, workspace roles, skills, memory, extension APIs, and temporary tunnels.

This package provides:

• cyborgy: the main CLI.
• cyborgy-mcp: the MCP server used by supported coding agents.
• cyborgy-dev and cyborgy-mcp-dev: development-environment entry points.

Install

pip install cyborgy

For local Cyborgy development tooling:

pip install "cyborgy[dev]"

Basic usage

cyborgy login
cyborgy mcp install --target codex
cyborgy codex exec "summarize this repository"

The CLI stores login state locally, installs the Cyborgy MCP configuration into the current repository, and syncs the skills assigned to that workspace.

Worker auto-update

cyborgy worker start is the launcher form: it starts or verifies one background worker for the current profile, worker name, and repository root, then exits 0. A second cyborgy worker start for the same context is a no-op when that worker PID is still alive; stale pid records are replaced safely.

cyborgy worker and cyborgy worker run remain the foreground form for supervised shells and debugging.

Workers can opt into pip package auto-updates:

CYBORGY_WORKER_AUTO_UPDATE=1 cyborgy worker start

When enabled, the worker periodically checks the installed cyborgy package against PyPI. If a newer version exists, it runs python -m pip install --upgrade cyborgy in a waited subprocess. The Python is resolved from CYBORGY_WORKER_PYTHON, the configured/current cyborgy executable's shebang, the active pyenv Python when the executable is a pyenv shim, or the current PATH before falling back to sys.executable. After a successful install, the worker stops polling for new commands, lets any current agent subprocess finish, and re-execs itself at the next idle boundary through CYBORGY_WORKER_EXECUTABLE or the current PATH's cyborgy wrapper. It does not broad-kill processes or interrupt running agent commands.

To keep a development-extra install on the same release track, start the worker with CYBORGY_WORKER_AUTO_UPDATE_PACKAGE=cyborgy[dev]. Version checks still use the cyborgy distribution on PyPI, while pip upgrades the configured package spec (cyborgy by default, or cyborgy[dev] when requested).

Optional knobs:

• CYBORGY_WORKER_AUTO_UPDATE_INTERVAL: seconds between checks, minimum 60.
• CYBORGY_WORKER_AUTO_UPDATE_INITIAL_DELAY: seconds before the first check.
• CYBORGY_WORKER_AUTO_UPDATE_TIMEOUT: seconds before the pip install attempt times out.
• CYBORGY_WORKER_AUTO_UPDATE_PACKAGE: pip package spec, default cyborgy.
• CYBORGY_WORKER_AUTO_UPDATE_INDEX_URL: pip index URL for installation.
• CYBORGY_WORKER_EXECUTABLE: explicit cyborgy wrapper to use for worker re-exec.
• CYBORGY_WORKER_PYTHON: explicit Python interpreter to use for auto-update installs.

Status

This is an alpha package. The public CLI surface is expected to evolve with the Cyborgy service.