Run and manage strategies
Strategies are part of the Kiddie toolkit: every agent booted up from the app has them; an agent from the early-access program doesn't until it's moved over. Ask your Kiddie to check availability before planning a session.
On this page
A strategy session is a saved set of instructions with a scope, limits, and end time. It can run between chat messages. A proposal alone doesn't start it.
Choose a strategy
| Strategy | What it does | Important boundary |
|---|---|---|
| Discovery | Checks for launches, records candidates, and explains why they qualify or are rejected. | Research only; doesn't buy. |
| Launch sniping | Attempts an entry when a qualifying launch is detected. | Uses periodic checks, not guaranteed first-block execution. |
| Graduation entry | Attempts an entry after a supported launch moves from its curve to a pool. | Different from buying at initial launch. |
| Copy-follow | Detects selected wallets buying on supported Pons launch curves, recorded as CurveBuy events, and applies your own rules. | Doesn't mirror their sells or every trade on other exchanges or chains. |
| Exit management | Applies exit rules to selected recorded position quantities. | Doesn't buy or manage every asset in your wallet. |
Discovery uses research mode. Entry strategies support paper or live mode. Paper uses quotes without sending real trades. It doesn't reproduce gas costs, competition for execution, or all live-market risks.
Sessions can run for up to seven days. Your browser doesn't need to stay open, but the worker and its data sources must remain available.
Plan and start a session
- Ask your Kiddie to check available strategies and any existing sessions.
- Describe your goal and mode: research, paper, or live. Provide source wallet addresses for copy-follow, or the positions you want managed for exit rules.
- Ask it to propose a plan and explain the choices listed below. Adjust the plan in chat.
- If you choose live mode, complete wallet setup and funding and confirm that your account is ready.
- Authorize the specific plan when you're ready to run it. If your original request already supplied the complete authorization, another confirmation isn't required.
- Check the session ID, end time, and worker acknowledgment. Ask your Kiddie to publish the strategy deck.
For an entry strategy, review these choices:
- The amount per entry and total entry-spending limit.
- The separate gas budget for live execution, unless the account is configured with unlimited budgets.
- The maximum number of open positions.
- The duration and intended checking interval.
- The target wallets or launch filters, including what to do when evidence is missing.
- The allowed slippage and maximum token tax.
- The exit rules: profit target, loss trigger, trailing trigger, time limit, or supported risk conditions.
- Whether expiry should leave assets held or attempt to close managed positions.
Research discovery doesn't need trading amounts or exits. Exit-only management doesn't need an entry budget. Your Kiddie should ask for the choices relevant to your request, not every field in every case.
Example planning request:
Show me a paper launch-sniping plan for 30 minutes. Model 0.001 ETH per entry, 0.005 ETH total, and at most two open positions. Propose the filters and exits, explain the tradeoffs, and don't start it yet.
The example amounts aren't recommended settings or a deposit requirement. You choose the plan. A paper session never becomes a live session automatically.
Read the strategy deck
The standard strategy deck has five views:
| View | What to check |
|---|---|
| Mandate | Mode, targets, spending and gas limits, exit rules, and expiry. “Mandate” means the instructions you authorized. |
| Opportunities | Candidates, rejection reasons, and any bounded wait for opening taxes to fall. |
| Positions | The quantities managed by this session, estimated exit values, and risk evidence. |
| Activity | Recorded actions, transaction identities, errors, and unresolved operations. |
| Review | Outcomes and recorded decisions, with paper results and estimates distinguished from real fills. |
Check the worker's last completed poll as well as the session state. “Queued” means the instructions are saved but not yet acknowledged. “Running” should be supported by recent worker activity, not just an old label.
Pause, stop, or close
These requests have different effects:
| Request | New entries | Existing exit rules | Assets |
|---|---|---|---|
| Pause entries | Stop | Continue under the authorized rules | Remain managed by those exits. |
| Stop the strategy | Stop | Stop | Remain held. |
| Close the strategy's positions | Stop | Attempts to sell the remaining managed quantities | Can remain partly or fully held if execution fails. |
To use a deck control, select it, review the draft in chat, and select Send. Then check whether your Kiddie reports the change as acknowledged. Selecting the control alone doesn't stop a worker or submit a sale.
Be explicit about which session you mean if more than one exists. Stopping a strategy doesn't cancel a transaction already broadcast to the network. Closing uses a bounded attempt window; it isn't an order that retries indefinitely.
Understand budgets and expiry
Entry spend is cumulative: selling an asset doesn't replenish the entry budget. Gas has a separate cap, including conservative reservations for transactions. Reserved gas isn't the same as gas actually spent.
An account configured with unlimited budgets has no aggregate entry-spend or gas cap. Your Kiddie shouldn't ask you to supply those caps or invent them. The deck displays unlimited, while actual spend and fees remain recorded. You still specify entry size and the strategy's scope, duration, position limits, and exit rules. Unlimited budgets don't create funds or authorize trades you didn't request. You can choose a cap for a particular strategy if you want one.
A gas cap can prevent an exit. Your Kiddie must explain that condition instead of silently raising the cap. If you choose a larger cap, explicitly authorize the change and any required resume or close action.
Only one live strategy can control the trading wallet at a time. A paused strategy still controls it while its exit rules remain active. Manual trades or another live session can be blocked until that control is released.
Expiry continues to approach while a session is paused. If the plan ends by keeping assets, those assets remain held without continuing management. A close-on-expiry instruction is an attempted sale, not a guaranteed outcome.
Recover interrupted work
A live-worker restart interrupts execution. An unavailable or interrupted worker can't be relied on to manage exits.
- Ask your Kiddie to inspect the session and any pending transaction.
- Ask it to reconcile the existing operation. Reconciliation checks or recovers the saved result; it doesn't authorize a replacement trade.
- Review the remaining balance, budgets, positions, and expiry.
- If you want the unexpired session to continue, explicitly request resume. Otherwise, request stop or close as appropriate.
Reconciliation alone doesn't re-arm an interrupted session. Resuming doesn't reset money already spent or extend the original expiry.
Review results
Ask for the session's outcome, reasons for skipped entries, unresolved transactions, gas, and the evidence period. Separate realized results from estimates for assets still held.
Percentage-based exit triggers compare estimated exit proceeds with the recorded acquisition cost before gas. If that cost is unknown, those triggers aren't available. Supported risk or time rules can still be used. An exit trigger doesn't guarantee a sale at its threshold price.
Recorded-event replay explains saved decisions. It isn't a historical backtest against a complete market data set. Paper performance doesn't establish that the same result would occur with real money.
For optional updates outside the app, see Enable optional notifications.