39 lines
1.1 KiB
Markdown
39 lines
1.1 KiB
Markdown
# docs/context/USER.md - Human Context
|
|
|
|
- Name: `<user-name>`
|
|
- Preferred name: `<preferred-name>`
|
|
- Current objective: Copilot-only OpenClaw setup on work machine
|
|
|
|
## Priorities
|
|
|
|
- OpenClaw reliability
|
|
- Copilot Enterprise auth and model routing
|
|
- Senior iOS engineering persona quality
|
|
- Clear fallback strategy for provider/model issues
|
|
|
|
## Working Style
|
|
|
|
- Wants direct fixes and exact commands
|
|
- Comfortable in terminal workflows
|
|
- Values architecture/refactor quality over shortcuts
|
|
|
|
## Secrets Inputs (Placeholders Only)
|
|
|
|
Use this section for setup prompts. Do not commit real secrets.
|
|
|
|
- `COPILOT_AUTH`: browser login required (`copilot auth login`) — no static token stored here
|
|
- `TELEGRAM_BOT_TOKEN`: `<set-at-runtime-if-using-telegram>`
|
|
- `OPENCLAW_GATEWAY_TOKEN`: `<generated-by-openclaw-rotate-if-exposed>`
|
|
|
|
## Setup Prompt Checklist
|
|
|
|
When assisting a new user, prompt for:
|
|
|
|
1. Whether Telegram is needed (`yes/no`)
|
|
2. If yes, ask for `TELEGRAM_BOT_TOKEN` at runtime
|
|
3. Confirm Copilot browser login is completed
|
|
|
|
Telegram clarification:
|
|
- Existing personal Telegram account is sufficient.
|
|
- No new phone number/user account is needed to run a bot.
|