unlegacy-cli

Installable CLI for connecting local coding agents to Unlegacy MCP.

Unlegacy generates repository documentation, API references, knowledge graph data, and Vault investigation docs in the platform. This CLI configures external coding agents so they can consume that MCP surface.

Install

Published package:

uv tool install unlegacy-cli

or:

pip install unlegacy-cli

After install, the command is saved on the user's machine as:

unlegacy --help

From a checkout:

pip install .

or:

uv tool install .

One-shot setup without preinstalling:

uv tool run --from 'unlegacy-cli>=0.7.3' unlegacy setup

Distribution

Build the package artifacts:

uv build

Version 0.7.0 introduces device sign-in and project scope. Deploy the matching backend and publish this version before distributing the frontend setup command. For local verification before publication, use uv run unlegacy setup from this checkout with --project /path/to/project and the local --endpoint.

The build creates dist/unlegacy_cli-<version>.tar.gz and dist/unlegacy_cli-<version>-py3-none-any.whl. Publish those artifacts to the Python package index used by Unlegacy clients.

Setup

unlegacy setup

The interactive client picker supports Windows, macOS and Linux. Version 0.7.1 fixes the Windows termios import error; Windows users can use the same setup command without extra flags. To refresh a cached one-shot installation:

uv tool run --refresh --from 'unlegacy-cli>=0.7.3' unlegacy setup

Version 0.7.2 adds actionable MCP and device sign-in transport diagnostics, including Cloudflare blocks and correlation IDs. Version 0.7.3 identifies all MCP and device sign-in HTTP requests as unlegacy-cli/<installed version> so proxies can recognize the CLI. Cloudflare Access policies must still permit the device sign-in flow.

Keep any existing --endpoint option when upgrading a customer installation.

Run setup from your project folder. The wizard chooses only this project by default, or all projects for this user, then lets you select clients. The choice applies to both MCP configuration and the bundled skills.

On first setup, the CLI displays an eight-character code and opens the browser at /mcp?step=code. Sign in, choose the organization and approve your code. The terminal then installs the selected clients and runs doctor. Nothing is approved merely by opening the page. Use --no-browser on a headless terminal.

The credential is saved privately in ~/.config/unlegacy/credentials.json, separately for each endpoint. Running setup in another project reuses that connection after validating it; no new browser approval is needed. An expired or revoked credential requires approval again. Use --reconnect to change the connected organization. A network failure does not create another connection. The production endpoint defaults to https://app.unlegacy.ai/ai/mcp.

# Configure the current project, or another folder, without repeating sign-in.
unlegacy setup --scope project --client claude-code --client codex
unlegacy setup --project /path/to/another-repository --client codex

# Explicitly make MCP and skills available in every project.
unlegacy setup --scope global --client claude-code --client codex

# Preview paths without authentication, network requests or writes.
unlegacy setup --project /path/to/repository --client all --dry-run

# Use this checkout's development server.
unlegacy setup --endpoint http://localhost:25250/ai/mcp

For automation, an existing credential can still be supplied with UNLEGACY_MCP_TOKEN (or --token). The CLI never prints the token. HTTPS is required except on loopback development hosts, and credential requests do not follow redirects.

Moving an existing global installation

Project setup detects global Unlegacy configuration and skills. The wizard asks to migrate them; unattended setup requires --remove-global. Global entries are removed only after project setup and doctor succeed. Other MCP servers and unrelated skills are preserved; backups go under ~/.config/unlegacy/backups. Shared compatibility skill directories are included, so moving one may also remove the global Unlegacy skill from another client that reads the same folder. The wizard explains this before proceeding. Restart affected clients afterward.

unlegacy setup --scope project --client codex --remove-global

Native installation locations

PROJECT means the enclosing Git repository root, or the specified/current folder outside Git. HOME means your user profile. Client trust prompts still apply; Codex loads project configuration only for trusted projects.

The VS Code default user profile is Library/Application Support/Code/User on macOS, %APPDATA%/Code/User on Windows and .config/Code/User on Linux. Custom profiles, portable installs and custom client directory overrides are not detected by this release. Scope controls where clients load Unlegacy; it does not narrow the credential's organization/repository permissions.

Credential-bearing config files and backups use owner-only permissions on POSIX. Project configs are added to Git's local info/exclude; setup refuses tracked config files instead of inserting credentials into version control. Untrack a personal config before setup, or keep a shared config and configure credentials manually. Symlinked project targets outside the project are refused. Packaged skills contain no credentials and may be versioned if desired.

Native behavior references: Claude scopes, Codex configuration, Codex skills, Cursor skills, VS Code skills, and OpenCode MCP.

Supported client values:

• claude-code
• codex
• cursor
• vscode-copilot
• opencode
• all

Commands

unlegacy setup
unlegacy doctor
unlegacy install-skills --client codex
unlegacy status

Bundled skill

unlegacy setup and unlegacy install-skills install one versioned skill bundle:

• unlegacy - authorized repository Knowledge and content retrieval

The bundle is self-contained; installing the external Superpowers plugin is not required.

The skill is used only when you explicitly ask to consult Unlegacy: for example, "ask Unlegacy about authentication", "pergunte ao legacy", "faça um legacy", or $unlegacy. General code questions, mentions of legacy code, and work on the Unlegacy project itself do not activate it. The request covers the current task and its follow-ups, not unrelated later tasks. Codex also receives agents/openai.yaml with implicit invocation disabled; use $unlegacy to explicitly load the skill there. Natural-language selection depends on the client's skill discovery behavior.

Canonical MCP contract

The bundled skill targets Backend-authorized Catalog, Knowledge and content reads. list_repos, find_repos and repo_brief resolve repository names and availability. search and org_survey discover evidence in one repository, a project or the organization. Survey coverage is the top 20 rank-fused hits, not an exhaustive inventory or confidence estimate.

get_symbol returns literal symbols and canonical entity refs. Pass those complete refs to symbol_context and impact. File and docs tools use canonical version IDs, paths, revisions and page cursors. No client constructs object-store keys or sends physical graph identifiers.

Arbitrary cypher currently returns CYPHER_NOT_SUPPORTED; it does not call KG. Vault-specific tools are not registered by this MCP server. unlegacy doctor checks the repository tool inventory, not permissions or the full runtime pipeline. Install this skill version with the matching server.

Troubleshooting connection errors

CLI MCP requests and device sign-in requests identify themselves with User-Agent: unlegacy-cli/<installed version>. This identifies the application instead of relying on Python's generic HTTP identity. It is not a credential: Cloudflare Access and other proxy policies must still permit the CLI's authentication flow without an interactive browser challenge on these routes.

HTTP and network failures during MCP validation and device sign-in show the request method and route, a suggested next step, and the UTC time. Valid Cloudflare Ray IDs and application request IDs are included when returned. Share these details with the installation administrator to correlate logs. Response bodies, authorization headers, device codes and URL query parameters are not included in these transport diagnostics.

For example, a confirmed Cloudflare 1010 response reports:

Cloudflare blocked this request (HTTP 403, error 1010: browser_signature_banned).
Request: POST https://your-installation.example/ai/mcp/
Ask the Cloudflare administrator to review Browser Integrity Check and allow CLI access to this route without browser challenges.
Cloudflare Ray ID: <returned Ray ID>
Time (UTC): <request failure time>

A Cloudflare header alone does not establish that Cloudflare blocked the request. Generic 403 responses ask the administrator to check both application permissions and proxy/access policies. Explicit browser challenges and Access login redirects have separate guidance. Credential requests never follow redirects, and TLS certificate verification remains enabled.

A 403 does not discard a saved connection or start another approval. Only a 401 during saved MCP credential validation triggers reauthentication. Device approval can also fail if the server returns an approval URL on a different origin; the message asks the administrator to configure the public domain. DNS failures, timeouts, TLS failures, missing routes and unavailable servers have their own messages. This change improves diagnosis; it does not change Cloudflare policies or repair server configuration.

Development

uv run pytest