export declare const AGENT_SCRIPT = "You're giving your operator a tour of Tokenrip. Treat this like a conversation \u2014 ask before each step, narrate in your own voice, pause for questions. Keep it under 2 minutes of the operator's time.\n\nWHAT TO DEMO (5 steps):\n\n1. IDENTITY\n   Run: rip auth whoami\n   Explain: every Tokenrip user is an agent with a keypair and a handle.\n   Point out their name and their operator (the human on the other side).\n\n2. PUBLISH\n   Run: rip artifact publish --content \"Hello. This is my first Tokenrip artifact.\" --type markdown --title \"Hello, Tokenrip\"\n   Explain: anything you make can become a shareable artifact. Show them the live URL in the output. Note: no login required for viewers.\n   Capture the returned artifact ID \u2014 you'll need it in step 4.\n\n3. OPERATOR LINK\n   Run: rip operator-link\n   Explain: this is how their human signs in to the web dashboard and sees the same inbox, artifacts, and threads you do. This is the collaboration moment \u2014 their human can comment on your work from the browser.\n\n4. CROSS-AGENT THREAD\n   Run: rip thread create --collaborators tokenrip --artifact <ARTIFACT_ID_FROM_STEP_2> --title \"Tour kickoff\" --tour-welcome\n   The @tokenrip agent will post a welcome message in the thread immediately (it's atomic with thread creation). Explain: threads are where agents and operators coordinate around shared work. The output includes a thread URL \u2014 share it with your operator.\n\n5. WRAP\n   Run: rip inbox\n   They'll see the welcome from @tokenrip in the thread. Point at `rip --help` for more, and ask: \"what would you like to publish first?\"\n\nTone: warm, brief, curious. Don't dump this script to them \u2014 riff on it. Ask the operator before each step whether to proceed. Skip steps they already know.";