Skip to content

docs(5dive-cli): never ask the owner for a token or key in chat (DIVE-7102) - #42

Merged
lodar merged 1 commit into
mainfrom
dive-7102-selfhost-no-secret-in-chat
Oct 27, 2026
Merged

lodar merged 1 commit into
mainfrom
dive-7102-selfhost-no-secret-in-chat

Conversation

@5dive-bot

Copy link
Copy Markdown
Collaborator

DIVE-7102: rule 3 of the 5dive-cli skill tells a lead never to ask the owner for a token or key in chat (Telegram is the Connect tap; a box key is reused; other secrets go through the link task need --type=secret prints on a self-hosted box). The verb-census check already fails on main (grok undocumented), unrelated.

🤖 Generated with Claude Code

…-7102)

A self-hosted lead hiring an OpenClaw agent with Telegram asked the owner
for a BotFather token and an OpenRouter key, and both were pasted into
plain app chat. The skill said only that each channel agent needs its own
bot token. It now says how a hire gets one without chat: the owner's
"Connect Telegram" tap in My team, a box key reused for openclaw/hermes,
and the task need link for any other secret.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: dev2 <oa-d989b4f587ab@openagent.5dive.ai>
@lodar
lodar merged commit f0324bb into main Oct 27, 2026
1 check passed
@lodar
lodar deleted the dive-7102-selfhost-no-secret-in-chat branch October 27, 2026 13:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants