docs: concept annexation, provider/reference docs, ACT-1 groundwork
Mosaic concepts pages now own the adapted content; source/license metadata under docs/reference/concepts. Adds ACT-1 agent-context planning capture, pinned concept test package + preparation utility, foundation observation notes (durability, evidence, federation, onboarding, workflow), and the #1495 consolidation assessment. TOOLS.md updated for the host-dev launcher.
This commit is contained in:
@@ -0,0 +1,149 @@
|
||||
---
|
||||
summary: "Tencent Cloud TokenHub and TokenPlan setup for hy3"
|
||||
title: "Tencent Cloud (TokenHub / TokenPlan)"
|
||||
read_when:
|
||||
- You want to use Tencent hy3 with OpenClaw
|
||||
- You need the TokenHub or TokenPlan API key setup
|
||||
---
|
||||
|
||||
Install the official Tencent Cloud provider plugin to access Tencent Hy3 through two endpoints — TokenHub (`tencent-tokenhub`) and TokenPlan (`tencent-tokenplan`) — using an OpenAI-compatible API.
|
||||
|
||||
| Property | Value |
|
||||
| ------------------------- | ----------------------------------------------------- |
|
||||
| Provider ids | `tencent-tokenhub`, `tencent-tokenplan` |
|
||||
| Package | `@openclaw/tencent-provider` |
|
||||
| TokenHub auth env var | `TOKENHUB_API_KEY` |
|
||||
| TokenPlan auth env var | `TOKENPLAN_API_KEY` |
|
||||
| TokenHub onboarding flag | `--auth-choice tokenhub-api-key` |
|
||||
| TokenPlan onboarding flag | `--auth-choice tokenplan-api-key` |
|
||||
| TokenHub direct CLI flag | `--tokenhub-api-key <key>` |
|
||||
| TokenPlan direct CLI flag | `--tokenplan-api-key <key>` |
|
||||
| API | OpenAI-compatible (`openai-completions`) |
|
||||
| TokenHub base URL | `https://tokenhub.tencentmaas.com/v1` |
|
||||
| TokenHub global base URL | `https://tokenhub-intl.tencentmaas.com/v1` (override) |
|
||||
| TokenPlan base URL | `https://api.lkeap.cloud.tencent.com/plan/v3` |
|
||||
| Default model | `tencent-tokenhub/hy3` |
|
||||
|
||||
## Quick start
|
||||
|
||||
<Steps>
|
||||
<Step title="Create a Tencent API key">
|
||||
Create an API key for Tencent Cloud TokenHub and TokenPlan. If you choose a limited access scope for the key, include **hy3** (and **hy3 preview** if you plan to use it on TokenHub) in the allowed models.
|
||||
</Step>
|
||||
<Step title="Run onboarding">
|
||||
<CodeGroup>
|
||||
|
||||
```bash TokenHub onboarding
|
||||
openclaw onboard --auth-choice tokenhub-api-key
|
||||
```
|
||||
|
||||
```bash TokenHub direct flag
|
||||
openclaw onboard --non-interactive --accept-risk --skip-health \
|
||||
--auth-choice tokenhub-api-key \
|
||||
--tokenhub-api-key "$TOKENHUB_API_KEY"
|
||||
```
|
||||
|
||||
```bash TokenPlan onboarding
|
||||
openclaw onboard --auth-choice tokenplan-api-key
|
||||
```
|
||||
|
||||
```bash TokenPlan direct flag
|
||||
openclaw onboard --non-interactive --accept-risk --skip-health \
|
||||
--auth-choice tokenplan-api-key \
|
||||
--tokenplan-api-key "$TOKENPLAN_API_KEY"
|
||||
```
|
||||
|
||||
```bash Env only
|
||||
export TOKENHUB_API_KEY=...
|
||||
export TOKENPLAN_API_KEY=...
|
||||
```
|
||||
|
||||
</CodeGroup>
|
||||
|
||||
</Step>
|
||||
<Step title="Verify the model">
|
||||
```bash
|
||||
openclaw models list --provider tencent-tokenhub
|
||||
openclaw models list --provider tencent-tokenplan
|
||||
```
|
||||
</Step>
|
||||
</Steps>
|
||||
|
||||
Onboarding preserves your model entries and leaves generated catalog rows to discovery. With `models.mode: "replace"`, it also writes the built-in catalog because that mode skips discovery.
|
||||
|
||||
## Non-interactive setup
|
||||
|
||||
```bash
|
||||
# TokenHub
|
||||
openclaw onboard --non-interactive \
|
||||
--mode local \
|
||||
--auth-choice tokenhub-api-key \
|
||||
--tokenhub-api-key "$TOKENHUB_API_KEY" \
|
||||
--skip-health \
|
||||
--accept-risk
|
||||
|
||||
# TokenPlan
|
||||
openclaw onboard --non-interactive \
|
||||
--mode local \
|
||||
--auth-choice tokenplan-api-key \
|
||||
--tokenplan-api-key "$TOKENPLAN_API_KEY" \
|
||||
--skip-health \
|
||||
--accept-risk
|
||||
```
|
||||
|
||||
<Note>
|
||||
`--accept-risk` is required alongside `--non-interactive`.
|
||||
</Note>
|
||||
|
||||
## Built-in catalog
|
||||
|
||||
| Model ref | Name | Input | Context | Max output | Notes |
|
||||
| ------------------------------ | ---------------------- | ----- | ------- | ---------- | -------------------------- |
|
||||
| `tencent-tokenhub/hy3-preview` | hy3 preview (TokenHub) | text | 256,000 | 128,000 | deprecated; use `hy3` |
|
||||
| `tencent-tokenhub/hy3` | hy3 (TokenHub) | text | 256,000 | 128,000 | reasoning-enabled; current |
|
||||
| `tencent-tokenplan/hy3` | hy3 (TokenPlan) | text | 256,000 | 128,000 | reasoning-enabled; current |
|
||||
|
||||
hy3 is Tencent Hunyuan's large MoE language model for reasoning, long-context instruction following, code, and agent workflows. Tencent's OpenAI-compatible examples use `hy3` as the model id and support standard chat-completions tool calling plus `reasoning_effort`.
|
||||
|
||||
<Tip>
|
||||
The model id is `hy3`. Do not confuse it with Tencent's `HY-3D-*` models, which are 3D generation APIs and are not the OpenClaw chat model configured by this provider.
|
||||
</Tip>
|
||||
|
||||
## Advanced configuration
|
||||
|
||||
<AccordionGroup>
|
||||
<Accordion title="Endpoint override">
|
||||
OpenClaw's built-in catalog uses Tencent Cloud's `https://tokenhub.tencentmaas.com/v1` endpoint. Override it only if your TokenHub account or region requires a different one:
|
||||
|
||||
```bash
|
||||
openclaw config set models.providers.tencent-tokenhub.baseUrl "https://your-endpoint/v1"
|
||||
```
|
||||
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Environment availability for the daemon">
|
||||
If the Gateway runs as a managed service (launchd, systemd, Docker), `TOKENHUB_API_KEY` and `TOKENPLAN_API_KEY` must be visible to that process. Set them in `~/.openclaw/.env` or via `env.shellEnv` so launchd, systemd, or Docker exec environments can read them.
|
||||
|
||||
<Warning>
|
||||
Keys exported only in an interactive shell are not visible to managed gateway processes. Use the env file or config seam for persistent availability.
|
||||
</Warning>
|
||||
|
||||
</Accordion>
|
||||
</AccordionGroup>
|
||||
|
||||
## Related
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="Model providers" href="/concepts/model-providers" icon="layers">
|
||||
Choosing providers, model refs, and failover behavior.
|
||||
</Card>
|
||||
<Card title="Configuration reference" href="/gateway/configuration-reference" icon="gear">
|
||||
Full config schema including provider settings.
|
||||
</Card>
|
||||
<Card title="Tencent TokenHub" href="https://cloud.tencent.com/product/tokenhub" icon="arrow-up-right-from-square">
|
||||
Tencent Cloud's TokenHub product page.
|
||||
</Card>
|
||||
<Card title="Hy3 preview model card" href="https://huggingface.co/tencent/Hy3-preview" icon="square-poll-horizontal">
|
||||
Tencent Hunyuan Hy3 preview details and benchmarks.
|
||||
</Card>
|
||||
</CardGroup>
|
||||
Reference in New Issue
Block a user