volcengine/SearchCLI(新しいタブで開きます)
主要言語: TypeScript
Open CLI for integrating AI search, recommendation, and conversational retrieval into agent systems and business systems
- star 数
- 1,188
- watcher 数
- 13
- fork 数
- 38
- issue 数
- 11
- 最終更新
- 2026/10/16
主要言語: TypeScript
Open CLI for integrating AI search, recommendation, and conversational retrieval into agent systems and business systems
English | 简体中文 | 日本語 | Deutsch | 한국어 | Français | Русский | Italiano | Español | Português | Türkçe | ไทย | Bahasa Indonesia
Connect stable, tunable search, recommendation, and conversational retrieval to your agent system or business system.
Community · Quick Start · AI Agent Setup · Full Agent Guide · Contributing · Security
SearchCLI is the open CLI for AI Search on Volcengine.
If your agent system or business system needs stable, tunable information distribution services, SearchCLI gives you a practical path to integrate production-grade search, recommendation, and conversational retrieval into real workflows.
With SearchCLI and its installable Viking skills, external agents can onboard data, build and validate search and recommendation flows, run conversational retrieval, tune strategy configuration, inspect bad cases, and iterate on retrieval quality in a stable, reviewable way.
Follow the SearchCLI WeChat Official Account
Scan the QR code below with WeChat to get SearchCLI project updates, usage guides, and announcements.
Follow the official account to keep up with SearchCLI updates.
vs dataset, vs app, and vs data for application and dataset management.vs search run, vs recommend run, and vs chat run for runtime verification.vs search tune query-generate | plan | run | report for first-version automated text-similarity evaluation and tuning.Viking skills so external agents can use the same workflows.gitgit clone git@github.com:volcengine/SearchCLI.git vs
cd vs
bash ./scripts/install.shIf the current shell already has VIKING_AK and VIKING_SK:
vs auth import-env vs auth status --json vs doctor --json
Otherwise, run interactive login in a real terminal:
vs auth login
If you will use search tuning query generation or LLM relevance judging, configure an OpenAI-compatible LLM API without placing the API key in plain config:
vs llm login vs llm status --json vs search tune llm-check --live --json
If the current shell already has VIKING_LLM_BASE_URL, VIKING_LLM_API_KEY, and VIKING_LLM_MODEL, use vs llm import-env instead. The API key is stored in the local secure credential store; base URL and model are stored as non-secret config.
Onboard a JSONL file into a fresh app using the V2 backend-driven schema inference flow:
vs dataset import-url --file-name items.jsonl curl -X PUT --data-binary "@./items.jsonl" "<FileUrl from previous step>" vs dataset infer-schema --tos-key <FileKey> --type multi_modal --theme e_commerce --language zh --name <dataset-name> vs dataset infer-result --task-id <TaskID> --render-schema vs dataset create --data @dataset-create.json vs data write --dataset-id <DatasetId> --fields @items.jsonl vs app create --name <app-name> --industry e_commerce --language zh vs app attach-dataset --data @attach.json
If you only need a dataset (no app), stop after vs data write.
For user-event datasets, use --type user_event and omit --theme.
If an external agent needs to operate AI Search through this repository:
git clone git@github.com:volcengine/SearchCLI.git vs
cd vs
bash ./scripts/install.shnpx skills add "git@github.com:volcengine/SearchCLI.git" -y -gThe default public skill bundle is:
vs-sharedvs-item-onboardingvs-searchvs-search-tuningvs-chatvs-recommendIf the current shell already has VIKING_AK and VIKING_SK, prefer:
vs auth import-env
Otherwise:
vs auth login
vs --help vs auth status --json vs llm status --json vs doctor --json vs skill list
vs authvs llmvs doctorvs skillvs itemvs appvs datasetvs datavs searchvs chatvs recommendIf you are maintaining the open-source repository itself, the local skill tooling is:
vs skill list vs skill init viking-demo-skill vs skill validate vs skill install all
Build and run repository checks:
npm install npm run validate:skills npm run build npm run test:acceptance:dist
Please check Contributing for more details.
External contributors must complete the Contributor License Agreement (CLA) before a pull request can be accepted.
Please check Code of Conduct for more details.
This project takes security seriously. For vulnerability reporting and supported versions, see SECURITY.md
This project is licensed under the Apache-2.0 License.