> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enconvo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# CLI and Local APIs

> Discover installed commands and local API schemas.

Enconvo includes a command-line interface with the desktop app. Open **Settings → Developer → CLI Guide** to see the installed extensions that expose CLI commands.

## Discover commands

```bash theme={null}
enconvo -h
enconvo knowledge_base -h
```

Append `-h` to the command you are investigating to see its current subcommands and options. The installed extension list is the authority for what your app supports.

If your shell cannot find `enconvo`, open the app's CLI Guide and check your installed app version and command-line setup. Keep Enconvo running for commands that use its local runtime.

## Inspect APIs

Open **Settings → Developer → APIs** to inspect the available routes and request schemas. Use the schema for your installed build when writing an integration; route parameters can change as extensions evolve.

For an AI client that only needs knowledge-base retrieval, use the dedicated [Knowledge Base MCP](/advanced/knowledge-base-mcp) connection instead of exposing the general local API.

## Develop an extension

See [Developing Extensions](/extensions/developing) for project layout and build commands, and [Extension API Reference](/extensions/extension-api-reference) for SDK entry points. [Hooks](/configuration/hooks) handles lifecycle automation; [Scheduled Jobs](/workflows/scheduled-jobs) handles work that runs at a chosen time.

Treat local API and shell access as powerful capabilities: commands can read or modify local data according to their implementation. Keep scripts explicit about the command, input, and destination.