English | 中文README
Connect stable, tunable search, recommendation, and conversational retrieval to your agent system or business system.
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.
- The command-line integration surface for AI Search on Volcengine.
- A stable path for external systems to access search, recommendation, and conversational retrieval capabilities.
- An agent-friendly workflow layer built around installable skills and automation-safe command output.
- A reviewable execution model with dry-runs, confirmation gates, and read-after-write verification.
- Developers integrating AI-powered information distribution into business systems.
- Teams building agent systems that need stable, configurable search, recommendation, and retrieval workflows.
- Operators and solution teams who need a reviewable way to onboard data, configure applications, and verify runtime behavior before production use.
- Item and catalog search on top of structured business data.
- Recommendation flows connected to application scenes and user behavior.
- Conversational retrieval experiences grounded in application search.
- Agent workflows that can onboard data, configure applications, and validate runtime behavior with explicit review steps.
viking item profile | plan | applyfor structured item onboarding.viking app,viking dataset, andviking datafor application and dataset management.viking search run,viking recommend run, andviking chat runfor runtime verification.- Installable
Viking skillsso external agents can use the same workflows.
- Node.js 20 or newer
git- Volcengine AK/SK with access to AI Search
git clone <public-repo-url> viking_cli
cd viking_cli
bash ./scripts/install.shIf the current shell already has VIKING_AK and VIKING_SK:
viking auth import-env
viking auth status --json
viking doctor --jsonOtherwise, run interactive login in a real terminal:
viking auth loginviking item profile --file ./items.json --pretty
viking item plan --file ./items.json --goal "Build item search"
viking item apply --plan-dir ./.viking/item-plans/<plan> --dry-run
viking item apply --plan-dir ./.viking/item-plans/<plan> --confirm-review --wait-ready --run-trialsIf you need a video dataset, do not rely on the default type. Always pass --type video explicitly:
viking item profile --file ./videos.jsonl --type video --pretty
viking item plan --file ./videos.jsonl --type video --goal "Build video search"
viking item apply --plan-dir ./.viking/item-plans/<plan> --dry-run
viking item apply --plan-dir ./.viking/item-plans/<plan> --confirm-review --wait-ready --run-trialsIf an external agent needs to operate AI Search through this repository:
git clone <public-repo-url> viking_cli
cd viking_cli
bash ./scripts/install.shnpx skills add "<public-repo-url>" -y -gThe default public skill bundle is:
viking-sharedviking-item-onboardingviking-searchviking-chatviking-recommend
If the current shell already has VIKING_AK and VIKING_SK, prefer:
viking auth import-envOtherwise:
viking auth loginviking --help
viking auth status --json
viking doctor --json
viking skill listviking authviking doctorviking skillviking itemviking appviking datasetviking dataviking searchviking chatviking recommend
If you are maintaining the open-source repository itself, the local skill tooling is:
viking skill list
viking skill init viking-demo-skill
viking skill validate
viking skill install allBuild and run repository checks:
npm install
npm run validate:skills
npm run build
npm run test:acceptance:distPlease 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.
If you discover a potential security issue in this project, or think you may have discovered a security issue, we ask that you notify Bytedance Security via our security center or vulnerability reporting email.
Please do not create a public GitHub issue.
This project is licensed under the Apache-2.0 License.