kaneo

原文涵盖的主题

• Kaneo
• Auth
• REST (default)
• MCP (optional)
• Authenticated browser fallback
• Invoice / ops log

Self-hosted Kaneo (usekaneo/kaneo). Prefer REST with an API key. MCP is optional. Instance values (URL, workspace id, project ids, token env) live in a private rules file outside this repo. This skill ships no hostnames or ids. Copy references/workspace.kaneo-rules.example.md to onboard an instance. Read the whole rules file before any write. Do not vendor usekaneo/kaneo .agents/skills - those are Kaneo-the-product UI skills (animation, design), not tracker ops. 1. Load $HOME/.config/vd/kaneo-rules/ .kaneo-rules.md. 2. Source its environment file and export the named token env var. Never print it. 3. Send Authorization: Bearer $TOKEN on every call. Kaneo also accepts the same value as x-api-key. Create keys under Settings -> Account -> Developer. Refuse when the rules file or token env is missing. Base is the rules baseurl with no trailing slash. Paths are under /api. Use the task UUID returned by the API for task routes, not the display key such as -123. Common write routes: | Action | Request | |---|---| | Create task | POST /api/task/{projectId} | | Change status | PUT /api/task/status/{taskId} with {"status":" "} | | Assign or unassign | PUT /api/task/assignee/{taskId} with {"u

这里只展示节选，请以完整原文和当前要求为准。