Chat and personalize your Kiddie
Use chat to describe the result you want. Your Kiddie chooses its available tools, asks for missing information, and explains what it completed.
On this page
Give a useful request
Include the goal, relevant context, and the form of the result. Add constraints when they matter.
| Goal | Example request |
|---|---|
| Understand something | “Explain bonding curves in plain language. Include the main risks.” |
| Organize a decision | “Turn these criteria into a comparison deck. Keep missing evidence visible.” |
| Research a token | “Inspect this contract on Robinhood Chain. Explain liquidity, taxes, and unknowns. Research only.” Then provide the full address. |
| Keep a record | “Summarize our decision and the unresolved questions in a report I can save.” |
| Change an existing result | “In the research deck, add a source and an as-of time for each finding.” |
| Check ongoing work | “What is running, when does it end, and does anything need my attention?” |
These are examples, not commands you must memorize. Ask for a plan if you don't know the available options. Requests that require an unsupported tool or account connection might need a different approach.
Make the intended action clear
“Explain,” “compare,” “quote,” and “show me a plan” ask for information. They don't authorize a trade.
On accounts with trading enabled, a specific buy or sell request can authorize that action. Your Kiddie doesn't need to ask you to confirm the same instruction twice. If you only want research, say “Don't trade.”
For ongoing work, specify whether you want research, paper trading, or real trading. A vague request such as “keep an eye on this” isn't enough to establish the scope or duration. Your Kiddie should clarify what it can run.
Follow progress
While your Kiddie works, chat shows activity and elapsed time. You can expand the activity summary when steps are available. A step describes work attempted or performed; it isn't a transaction receipt.
Let the current reply finish before sending a dependent request. If the connection drops, reload and check the saved conversation before repeating the action. For trading, ask your Kiddie to check the original transaction instead of submitting another one.
Set a name and preferences
- To give your Kiddie a name, say “I'll call you Byte.” Its NFT number still identifies which Kiddie it is.
- To set a report preference, say “Use America/New_York for times and ETH for native balances.”
- To change a preference, state the replacement: “Use UTC instead of America/New_York from now on.”
Your Kiddie records a small set of lasting preferences. It doesn't need a profile form. Ask it to confirm a preference if a later response doesn't follow it.
Understand memory and history
Saved history and memory serve different purposes. History lets you reread earlier exchanges. Your Kiddie uses recent conversation context, saved preferences, and task records to continue work.
Don't assume that every old message is available to the model on every turn. When returning to an important task, name the deck or strategy and ask your Kiddie to check its saved state.
Scroll toward the beginning of the conversation to load older saved exchanges. History has retention limits, and a failed or interrupted exchange might be missing. Save important reports separately.
Asking your Kiddie to change a preference isn't a request to erase chat history or every copy of that information. See Privacy and access.
Share information the current chat supports
The current composer accepts text, not file uploads or voice recordings. Paste a relevant excerpt and explain its source. Don't paste credentials or secrets.
Messages are limited to 16,000 characters. A longer paste can be cut off at that limit. Check the counter and the end of the message before sending. Split longer material into labeled parts and say when you've sent the final part.
Your Kiddie can send files back to you even though you can't upload files through this composer. See Save reports and files.
Next: Use cyberdecks.