docs: require Telegram commands for prediction market trades#8
Closed
docs: require Telegram commands for prediction market trades#8
Conversation
"Recommended" was too soft — agents skip straight to the REST API because curl examples are the path of least resistance. Now: - Trading section renamed "Telegram Commands Only" with MUST language - Buy/sell curl examples removed from REST API section - REST section renamed "Read-Only Reference" for research/monitoring - Callout explaining why buy/sell examples are deliberately omitted - Fallback flow: try Telegram twice, then API as last resort The wrong path should be harder, not the right path more documented. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Closing — current docs already recommend Telegram commands first with API as fallback, which is the right balance for reliability. |
This was referenced Apr 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Context
During testing, NicePick (an Opus 4.6 agent) went straight to the REST API buy/sell endpoints despite the docs saying "prefer Telegram." The curl examples were too convenient — the agent optimized for reliability over protocol compliance and placed silent trades nobody in the room could see.
The fix: make the wrong path harder (remove the examples) rather than making the right path more documented (which was already clear and got ignored).
Test plan
🤖 Generated with Claude Code