Troubleshoot Script Kiddies
Start with the message shown in the app. A wallet-access problem, a service outage, and a trading failure need different actions.
On this page
If money might have moved, check the original transaction before repeating the request. A missing reply isn't evidence that nothing happened.
Sign-in problems
| Problem | What to do |
|---|---|
| Your wallet doesn't connect | Open the app in a browser that exposes your wallet connection. On a phone, try the wallet's browser. Unlock the wallet and check the selected account. |
| No Kiddie appears in the list | The list is read from the chain. If this wallet holds a Kiddie that isn't shown, enter its token ID; the app still verifies ownership. If the wallet holds none, sign in with the one that does. |
| The Kiddie is below tier 5, or isn't activated | Activate it at scriptkiddies.com/desk with the wallet that holds it, then sign in again. Upgrading from a lower tier costs only the difference. If you're an early-access tester, the chat names the date your grace period ends. |
| The app names a different associated Kiddie | Open the number it names. Ask in the Script Kiddies Discord if the association needs review; it doesn't change automatically. |
| The app says this wallet can't sign in | Sign in with the wallet that holds your Kiddie. If it does and the app still refuses, ask in the Discord with your wallet address and Kiddie number. |
| The wallet refuses the network or signature | Check that the sign-in account is correct and the wallet can use Robinhood Chain. Review the requested network. Cancel any unexpected transaction request. |
| The challenge expired or you canceled the signature | Begin the sign-in attempt again and sign the new message if its details are correct. |
| Boot-up didn't finish | The screen names the step that didn't complete. Select Check on it to try again; the machine is created once, and a retry continues from what already exists. If it fails repeatedly, ask in the Discord with your Kiddie number and the step named. |
| The app says no agent could be assigned | Wait a few minutes and try again. If it persists, ask in the Discord. |
| Ownership or tier can't be checked | Wait and retry later. A service-side chain lookup failure isn't a request to move the NFT or fund a wallet. |
| Too many sign-in attempts | Wait at least a minute before trying again. |
Chat problems
Your Kiddie is taking longer than expected
Check the activity indicator. Tool use and waking the agent can take time. Avoid sending repeated copies of the request.
If the app reports a lost stream, reload to check for the saved reply. The server might finish the turn after the browser connection ends. If the request involved trading, ask for its recorded outcome before authorizing another trade.
You reached a usage limit
Follow the app's message. A short-term request limit and a daily usage allowance are different. Repeated retries don't restore a daily allowance, and the research-watch cap isn't the same limit as chat usage.
The app asks you to sign in again
Reconnect with the wallet that holds your Kiddie. Sessions expire, and an ownership or activation change can invalidate access.
If the message instead says that the agent or deck service has an authentication problem, ask in the Discord. Repeated wallet signatures don't repair a service credential mismatch.
Your message was cut off
The composer accepts up to 16,000 characters. Check the character counter and split longer text into labeled parts. File upload isn't available in the current composer.
Earlier conversation is missing
If the chat opens empty with the line "reading your history…", your Kiddie's machine is still waking up. The conversation appears on its own, usually within a few seconds and at most about a minute. If the line changes to "could not read your history — reload to try again", reload the page.
Scroll toward the beginning of the chat to load older saved exchanges. If the history ends, it might have reached the retained record. A failed exchange might not have been saved.
Ask your Kiddie to inspect a named task, deck, or strategy rather than assume that its entire conversation memory is available. Save important reports locally.
Deck and file problems
The cyberdeck is blank after signing in
If the deck's title reads "reaching your decks…", your Kiddie's machine is still waking up; the deck loads on its own within a few seconds. If it stays that way for more than a minute, reload the page.
| Problem | What to do |
|---|---|
| A requested deck isn't visible | Open All decks and search for its name. On a smaller screen, select Decks first. Ask your Kiddie whether publication completed. |
| A deck is stale | Ask for a refresh with source timestamps. If you need updates while away, check whether a watch or session is actually running. |
| Echoes remain queued | Send a chat message so your Kiddie can read the notes. Echoes don't wake it immediately. |
| A strategy control seemed to do nothing | Check the draft in chat. Select Send to request the action, then verify its acknowledgment. |
| A deck reports an error | Tell your Kiddie the deck name and visible error so it can inspect and repair it. |
| An attachment won't load | Check that your session is active, then ask your Kiddie to verify the file. A missing or oversized file needs repair, not repeated downloads. |
| A report changed since you first opened it | The file might have been updated under the same name. Use a downloaded copy when you need a fixed version. |
Trading and strategy problems
These checks apply to agents with the Kiddie toolkit: every agent booted up from the app, and early-access agents once they've been moved over.
| Problem | What to do |
|---|---|
| Native trading tools aren't available | Your agent is from the early-access program and hasn't been moved to the toolkit yet. Continue with research or other tasks; don't deposit as a workaround. Ask in the Discord about when it moves. |
| Wallet exists but isn't ready | Ask for the current network, balance, pending operations, and active strategy. Creation alone doesn't establish readiness. |
| A deposit isn't reflected | Compare the original transfer's destination and network with fresh wallet details. Ask your Kiddie to check the actual balance. Don't send it again yet. |
| A listed token can't be traded | Ask which route or token property is unsupported. Discovery covers more assets than execution. |
| A quote expired | Ask for a new quote and review changed amounts before authorizing execution. |
| A submission timed out | Ask your Kiddie to reconcile the original operation and transaction hash. Don't create a replacement request to force a response. |
| Another strategy controls the wallet | Inspect that strategy. Pausing entries can leave exits active and the wallet reserved. Decide whether to stop or close it. |
| An entry or exit hit a gas cap | Check what remains held. Increase the cap only if you choose to authorize it; an increase doesn't itself guarantee execution. |
| A session is queued, interrupted, or needs attention | Ask for worker health, the last completed check, and unresolved transactions. Follow the recovery procedure before resuming live work. |
| A stopped session still shows assets | Stop ends management without selling. Ask to close the remaining managed positions if you want a sale. |
| An external holding is missing | Ask to record the specific untracked quantity. The view isn't an exhaustive wallet index. |
| An expected alert didn't arrive | Check configuration, opt-in, and worker activity. Silence doesn't establish success or failure of a trade. |
For recovery steps, see Recover interrupted work.
Report a problem
Ask in the Script Kiddies Discord. Include:
- Your Kiddie number.
- The time of the issue and your timezone.
- What you requested and what happened instead.
- The exact error text and the affected deck or file name, if relevant.
- For a transaction issue, its public hash, chain, and session ID if available.
If you share a screenshot, remove unrelated private information first. Don't post passwords, seed phrases, private keys, session tokens, bot credentials, or webhook secrets.
If access is lost after an NFT transfer, say that in your report. Don't assume that signing in from a new wallet restores the previous trading account.