Turing CLI
turing-cli is the command-line tool for the Turing Platform. It exposes Agent Memory, document conversion, usage queries, and self-upgrade as scriptable terminal commands, making it suitable for local terminals, CI pipelines, and agent workflows.
turing-cli can be used together with agent skills. Relevant skills are available on SkillHub, or you can configure your own skills according to the conventions of your agent or IDE.
| Skill | Paired CLI capability | Link |
|---|---|---|
| Turing LTM | turing-cli memory login / install / doctor / recall / remember — share one personal memory across local agents | Turing CLI · SkillHub: Turing LTM · Docs |
| Turing Operations | turing-cli operations search / dashboards / grouped-usage — query usage, costs, tokens, and one- or two-dimensional breakdowns | SkillHub: Turing Operations |
| Documents | turing-cli documents convert — convert PDF / Word / Excel / PowerPoint to Markdown for agent consumption | SkillHub: Documents |
Capability Overview
| Sub-domain | Purpose | Common commands |
|---|---|---|
| Memory | Install the Portable Skill and share one personal memory across local agents with Recall / Remember | turing-cli memory |
| Documents | Convert PDF / Word / Excel / PowerPoint to Markdown | turing-cli documents convert |
| Operations | Query Turing Platform usage, costs, tokens, models, and request details | turing-cli operations |
| Upgrade & Version | Check for updates, install new versions, view the current version | turing-cli upgrade |
Installation
macOS / Linux:
curl -fsSL https://live-public-aigc-resources.s3.cn-north-1.amazonaws.com.cn/turing/turing-cli/install.sh | bash
turing-cli version
Windows PowerShell:
irm https://live-public-aigc-resources.s3.cn-north-1.amazonaws.com.cn/turing/turing-cli/install.ps1 | iex
turing-cli version
Configuring the API Key
The recommended approach is to write the key to ~/.turing-cli.yaml:
api_key: sk-...
You can also use an environment variable, which takes higher precedence:
export TURING_API_KEY="sk-..."
Override the API base URL only when temporarily connecting to a different environment:
export TURING_API_BASE="https://<other-env>/api/v1"
Quick Start
turing-cli version
turing-cli memory doctor
turing-cli documents convert report.pdf
turing-cli operations search -q zhangsan
turing-cli operations dashboards --type username --value san.zhang
turing-cli operations grouped-usage --type username --value san.zhang --group-by service,day
turing-cli upgrade check
Command Structure
turing-cli
├── memory
│ ├── login
│ ├── install
│ ├── doctor
│ ├── recall
│ └── remember
├── documents
│ └── convert
├── operations
│ ├── search
│ ├── dashboards
│ └── grouped-usage
├── upgrade
│ ├── check
│ └── apply
└── version
Global Flags
Global flags can be placed before any subcommand:
turing-cli --config ./turing-cli.yaml operations search -q zhangsan
| Flag | Default | Description |
|---|---|---|
--config FILE | $HOME/.turing-cli.yaml | Path to the configuration file |
-v, --verbose | false | Enable verbose output |
-h, --help | Show help for the current command |
Troubleshooting
| Symptom | Resolution |
|---|---|
command not found: turing-cli | Re-run the installation script and verify that the install directory is in PATH |
missing API Key | Set ~/.turing-cli.yaml or the TURING_API_KEY environment variable |
| Network connection failure | Check your network, proxy settings, and access to the target environment |
HTTP 403 | The current API Key does not have permission to query the target resource |
Uninstallation
macOS / Linux:
sudo rm /usr/local/bin/turing-cli
Windows: delete turing-cli.exe from %LOCALAPPDATA%\Programs\turing-cli and remove that directory from PATH.