@capabletooling/cli

Unified command-line interface for the CapableCore platform. Ships multiple binaries — one per vertical — from a single package:

• mding — markdown.ing workspace sync, editor bridge, GitHub import
• acing — agentconfig.ing command surface

Bin shims set CAPABLE_CLI_MODE and dispatch to the vertical's register() entrypoint under src/verticals/<vertical>/. Shared code (auth, config, theme, hooks, components) lives in src/core/.

Install

The canonical package:

npm i -g @capabletooling/cli

Alias packages exist so legacy / vertical-specific names still work. They are thin wrappers that depend on @capabletooling/cli and expose a single bin:

npm i -g mding                    # installs `mding`
npm i -g acing-cli                # installs `acing` (agentconfig.ing)
npm i -g @capabletooling/agentconfiging  # installs `acing` (agentconfig.ing, scoped)
npm i -g fding-cli                # installs `fding` (filediff.ing)

Pick whichever name matches how you think about the tool. They all install the same underlying code — agentconfig users can use either acing-cli or the scoped @capabletooling/agentconfiging.

Usage

mding --help
mding login
mding sync

acing --help
acing status

Each vertical registers its own subcommands; run <bin> --help for the current surface.

Environments

Every command accepts --server <url>, --dev, or --test (mutually exclusive). With no flag, the stored config default — or the prod URL — is used.

| Vertical | prod (default) | --dev | --test | |-------------|------------------------------|---------------------------------------------|------------------------------| | markdowning | https://app.markdown.ing | http://dev.markdown.ing.junoddev:4010 | https://test.markdown.ing | | agentconfig | https://app.agentconfig.ing| http://dev.agentconfig.ing.junoddev:4012 | https://test.agentconfig.ing | | filediff | https://app.filediff.ing | http://dev.filediff.ing.junoddev:4011 | https://test.filediff.ing |

--server <url> overrides everything else.

Platform-host endpoints (CLI auth + /ws/cli)

Starting with the endpoint split (Elixir Pre-PR 4), CLI auth endpoints (/api/cli/*) and the CLI WebSocket (/ws/cli) live on the CapableCore platform host — NOT on the vertical host:

| Env | Platform URL | |-------|----------------------------------------------| | prod | https://app.capabletool.ing | | dev | http://dev.capabletool.ing.junoddev:4000 | | test | https://test.capabletool.ing |

The CLI swaps --server (a vertical URL) for the matching platform URL for CLI auth / WS hops automatically. Operators on a custom --server can override the platform URL via the CAPABLE_PLATFORM_URL env var.

Requirements

• Node.js >= 20.3.0 (the device-login flow uses AbortSignal.any())

Links

• Platform: https://capabletool.ing
• markdown.ing: https://markdown.ing
• agentconfig.ing: https://agentconfig.ing
• Source: https://github.com/junoddev/markdown.ing (directory: cli/)

License

MIT