Position guards watch your open trades around the clock. You define a stop-loss and take-profit probability for a position, and Kuroko polls the live market price every 60 seconds. When a threshold is crossed, it fires an exit order through your connected wallet — no manual intervention needed. If you don’t have a wallet connected, it records a paper trade exit and notifies you instead.Documentation Index
Fetch the complete documentation index at: https://0x-250ca30e.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
How guards work
Every active guard is evaluated against the current market probability on a 60-second cycle. The outcome depends on which threshold is crossed first:| Trigger | Action | Shares sold |
|---|---|---|
| Probability ≥ take-profit | SELL — lock in gains | 40% of position |
| Probability ≤ stop-loss | REDUCE — limit downside | 65% of position |
| Neither threshold crossed | HOLD — no action | — |
Guards poll every 60 seconds. A sudden spike that reverses within a 60-second window may still trigger a guard if the threshold is crossed at poll time. This is a polling-based system, not a real-time stream.
Setting a guard
Open the Guards panel
Go to
/portfolio. On desktop, the Guards panel is in the right column. On mobile, tap the Guards tab.Select your market
Type in the search box to find the market you hold a position in. Results show the current probability next to each market name. Click the market to select it.
Enter your position details
Fill in the number of Shares you hold and your Entry Price in cents (1–99). These values determine how many shares are sold when a guard fires.
Set your thresholds
Kuroko pre-fills sensible defaults based on the current market probability:
- Take-profit — defaults to
min(current probability + 10, 99) - Stop-loss — defaults to
max(current probability − 10, 1)
Threshold validation
Kuroko validates your thresholds before saving:- Stop-loss must be strictly less than take-profit
- Both values must be between 1 and 99 (inclusive)
Guard actions explained
SELL
Take-profit triggered. Sells 40% of your position at the current market probability. Keeps 60% in place to capture further upside if the market continues moving.
REDUCE
Stop-loss triggered. Sells 65% of your position. Cuts most of your exposure while retaining a small position in case the market reverses.
HOLD
No threshold crossed. The guard is active and monitoring, but no order is placed this cycle.
Setting guards via AI chat
You can create a guard without opening the Portfolio panel. In the AI chat at/, use natural language:
Managing active guards
Each guard card in the panel shows:- The market question
- Your stop-loss and take-profit thresholds
- The current live probability (labeled Now X%)
- The current guard status: HOLD, SELL, or REDUCE
- An On / Off toggle to temporarily pause the guard without deleting it
Storage
Guards are stored in your browser’s localStorage under the keykuroko_position_guards. They persist across page reloads and navigation but are specific to the device and browser you’re using. Nothing is synced to a server.
What happens if my wallet disconnects while a guard is active?
What happens if my wallet disconnects while a guard is active?
The guard continues to evaluate on every 60-second poll. If a threshold is crossed while your wallet is disconnected, Kuroko records a paper trade exit and displays a notification in the terminal instead of submitting a live order. Reconnect your wallet and re-create the guard if you want future triggers to execute live orders.
Can I have multiple guards on the same market?
Can I have multiple guards on the same market?
Yes. You can set more than one guard per market — for example, one with conservative thresholds and one more aggressive. Each guard is evaluated independently on every poll cycle. Be aware that multiple guards on the same position can trigger at the same time if the probability moves through both thresholds in a single 60-second window.
How are guards stored, and do they survive a page reload?
How are guards stored, and do they survive a page reload?
Guards are saved to your browser’s localStorage and survive page reloads, tab closes, and navigation between pages. They are not stored on a server, so they are tied to the specific browser and device where you created them. Clearing your browser data or switching devices will remove your guards.