No-Code Agentist

Part 2 is here! Let's learn the art of supervising someone smarter than you. https://t.co/UeV4pJ4NFx

https://t.co/6PVClv4PJO

GROK BOT HOW TO USE Sources: official https://t.co/2EN1BbJ794 + https://t.co/0OVb26msAp + your Grok Bot bookmark folder (859 posts) Updated: 2026-09-10 WHAT NEW TODAY - Folder 859 posts (8 new vs Sep 9) - Grok Bot team (poteto): account switching is finally here; Official (bot) drafts messages inline for approve-before-send - Official (bot via lingxi): Share a file directly with Grok Bot on mobile - Coinbase: Coinbase for Agents on Grok — connect Coinbase; tell Grok to trade, analyze, automate; no MCP setup - SpaceXAI notes (blankspeaker): Grok Bot 0.47.0 — auto lock team review; auto review team rules - SpaceXAI notes (blankspeaker): Grok Bot 0.44.0 — marketplace of bots; multi-person Bot; voice overheard/speech tags WHAT IT IS - A Bot is a named, persistent teammate, not a one-off chat - You message it like a coworker and it finishes work in real apps - All of your Bots share one cloud computer (browser, files, terminal) - Each Bot has its own screen on that shared computer - Work keeps going when your laptop or the app is closed - It only comes back when it needs approval or a human step - Do not confuse Grok Bot with Digital Optimus (real-time video human emulation) - Testers (joehansen): do not confuse Grok Bot with an X Chat Agent (an X account you add to a group chat). Grok Bot is the machine that does the work - Official Elon: Your Bot will identify issues to resolve, notify you when they are fixed, and continue on with your project ACCESS AND INSTALL - Official bot (Aug 26): All SuperGrok and Cursor Pro subscribers now have access - Testers (mattyp): Grok Bot is free to try; every Grok & Cursor plan includes Grok Bot - Testers quoting SpaceXAI (cb_doge): SuperGrok, SuperGrok Plus, SuperGrok Heavy, Cursor Pro, Cursor Pro+, Cursor Ultra, Cursor Teams Standard and Premium - Cursor CEO Michael Truell: everyone with a standard Grok or Cursor subscription - Testers: included at no extra cost with those plans; circulating plan prices $20/month Cursor Pro and $25/month SuperGrok (nextbigfuture) - Official bot + Elon: weekly / free usage limits reset for all Grok Bot users - Sign in with your Cursor account (that account owns plan and usage) - Official desktop download: https://t.co/C9n6VM80SO - Also listed at https://t.co/jeYLjt4xIM - Official desktop is macOS and Windows (Apple silicon or Intel; Windows x64 or Arm64) - Testers (mattyp): Linux is now supported (official docs may lag) - iPhone: iOS 18+, App Store app "Grok Bot" - Official (bot, Sep 2): Grok Bot is now available on Android - Testers (mark_k): install from Play Store; full Grok Bot experience on Android - Play Store: https://t.co/CM2CGVPiuU - Official docs may still lag on Android; Testers (mattyp, Sep 4): Grok Bot is now available for iPad - SuperGrok Heavy users can choose Get access with SuperGrok Heavy, then Link Grok Account - Linking SuperGrok Heavy can unlock free Cursor Ultra (one Grok account to one Cursor account) - Legacy Privacy Mode blocks Grok Bot; switch to a supported Cursor data setting first - Grok Bot checks for updates automatically; Check for Updates is in Settings → Beta - Official Elon (Sep 4): Grok Bot Enterprise is now available - Testers (mark_k, Sep 3): Version 0.36.0 is now live — bugfixes and improvements - SpaceXAI notes (blankspeaker, Sep 9): Version 0.47.0 — auto lock team review; auto review team rules - SpaceXAI notes (blankspeaker, Sep 9): Version 0.44.0 — marketplace of bots; multi-person Bot; voice overheard/speech tags - Testers (mattyp, Sep 4): iPad app available(official docs may still lag) SIGN IN [] Desktop: Get started, then Sign In with Cursor in the browser [] iOS: Login with Cursor, finish in the browser, return to the app [] Official: Cmd-D turns on voice dictation [] Official: it is easier to use the remote computer from your phone [] Use the same Cursor account that should own usage [] First-run tour asks which tools you use; that only shapes teammate suggestions [] Computer setup runs in the background, then Meet a future teammate opens CREATE A BOT [] New in the sidebar, or Cmd/Ctrl+N [] In New chat, choose Create new agent [] Edit Profile: name, title, description, avatar [] Give a short name, one primary job, and how it should work [] Description = standing rules (never send without approval) [] Chat messages = this-task instructions (draft follow-ups for these 12 accounts) [] Focused Bots beat one catch-all General Helper [] Testers (XFreeze): do not design a Bot from scratch; ask a Bot to create a capable one for you (it already has your context) [] Bookmark testers: start with about six roles; give each Bot recurring work [] Pin important Bots; hide unused ones (hiding does not pause routines) [] Bookmark testers: resize the sidebar, give titles, and group Bots into sections [] Duplicate a Bot to reuse a role for a new scope (copy does not include memory or history) [] Delete only if you are sure; files and logins on the shared computer stay [] Account limit: 50 Bots and group chats combined [] Name language can steer reply language (bookmark testers reported this) [] Bookmark testers: no model picker yet; testers still list voice mode, BYOK, multiplayer, and hang-error messages as missing (iPad now available per mattyp) [] Testers (XEthanai / XFreeze): shareable Bot templates - build once, fine-tune, share the full setup for others to use or customize [] Testers (GrokBotDev): Official Marketplace launched (about 69 bots listed; community has catalogued 420+ searchable from a Bot) [] SpaceXAI notes (blankspeaker): v0.44.0 worked on browse a marketplace of bots; use a Bot with more than one person; overheard/speech tags on voice [] Testers (XFreeze): Marketplace framing earlier — browse specialized Grok Bots by category and add them to your team [] Testers (RoundtableSpace): Marketplace framing — hand-picked bots by category with routines/workflows built in (app store for AI teammates) [] Testers (kloss_xyz): 8 official-ish bot templates (calls, X, writing, images, coding, networking, tool testing, parking tickets) HOW TO WRITE A TASK [] Outcome: what should be finished [] Sources: which apps, sites, files, or chats matter [] Constraints: what it must not do, or must ask first [] Deliverable: what it should return [] Review point: when it should stop for you [] Safe first task: attach a file and ask for a cited summary; do not change the file [] Next task: one real tool, read-only, with a sign-in handoff if needed [] After a good result, name the lasting format preference in chat [] Then save it as a skill or routine [] Official bot examples: email cleanup, Starlink-likely flights, build a site then buy the domain and deploy, meeting notes, sales prospecting, refunds, podcast audio digest [] Testers: paste a viral video link and ask the Bot to recreate it [] Testers: start from an org chart or make one Bot the boss of a repo, not a long to-do list [] Testers: one clear job, explicit allowed sources, no-guessing rule, approval gate before any real action [] Testers: 5 calibrations - confidence threshold, checkpoint long tasks, show negative examples, gate destructive actions separately, test edge cases first [] Testers: one Bot, one job - two jobs claimed worse at both; put recurring work on a schedule [] Testers quoting claimed SpaceXAI employee: version prompts and tool configs like code; scratchpad separate from the user-facing answer; retry with a different strategy; measure cost per successful outcome; review failure logs on a schedule [] Testers (mvanhorn): Compound Engineering - force a plan first; three-layer instructions (base, role, current focus); screenshot instead of retyping what's on screen; ping only on a real hit [] Testers (AlexFinn): anything you are about to do on your computer, ask Grok Bot first [] Testers (AlexFinn): example week - Reddit microSaaS, 3D digital office to watch Bots, Omarchy setup, product returns, daily AI news post, Cursor cloud-agent bug fixes, X model-release watch, brand-deal negotiation, contract redlines [] Testers (Michael_Fenech_): give it business responsibilities (checking, chasing, updating, coordinating), not just questions AGENT COMPUTER AND LOGINS [] Open Agent Computer from the conversation to watch the desktop [] Take over for password, passkey, 2FA, CAPTCHA, payment, or human-only pages [] Complete only the blocked step, then return control [] Never paste passwords or one-time codes into chat [] Official (bot, Sep 8): fill out forms and logins for your Bot without ever leaving the chat, with support for any password manager [] Testers (XFreeze): when a site needs your account, Bot pauses; you auth with 1Password / Apple Passwords / any manager; Bot continues — no pasting credentials into chat [] Testers (LaceyPresley / muskonomy): in-chat logins/forms also cover checkouts and booking flights [] Grok Bot team (poteto, Sep 9): account switching is finally here [] Official (bot, Sep 9): Share a file directly with Grok Bot on mobile [] Use a secure secret request when the app offers one [] Browser sessions persist and are shared across all your Bots [] Prefer a connector/plugin when one exists; use the browser when it does not [] Coinbase (coinbase, Sep 9): Coinbase for Agents on Grok — connect Coinbase at https://t.co/aL6KKYjGXH; tell Grok to trade, analyze, automate; no MCP setup [] Testers (SamSokolin): for repeated web-app clicks, reverse-engineer browser-use into scripts (capture network once, call APIs next) [] Keep durable files in /workspace with clear project folders [] Settings → Beta: Update Agent Computer (preserve state), Recover, or Reset (can lose recent work) [] The cloud computer is not your Mac or Windows machine [] Local-computer execution is separate: Settings → General → Agent → Execution on Local Computer [] Default local policy is Ask every time; use Never allowed unless you need local files [] Bookmark testers: give a Bot full local Mac/iMessage access only on a spare machine [] Testers: local Mac access can write local Python scripts on your Mac [] Testers (Av1dlive / mvanhorn): Claude Code, Codex, and Cursor claimed runnable on the Bot's own computer [] Testers (XFreeze): take over that same cloud computer from your phone without being at the laptop [] Testers (Damir_Akaza): group-chat Bots can reach a local Mac Mini via Tailscale for project files and local scripts [] Testers (farzyness): a Bot can exclusively use Grok Build in CLI with the latest Grok models at highest thinking [] Testers (AlexFinn): a 3D digital office on a second monitor to watch Bots work PLUGINS AND CONNECTORS [] Settings → Plugins, then Add, then authenticate in the browser [] Grok Bot team (poteto): tinkabot helps build MCP/skills plugins and submit them for approval so all users can use them [] Type @ to attach a connector; type / to reference a saved skill [] Installed connectors are account-wide, not isolated to one Bot [] Official: you can connect multiple accounts to the same plugin [] Official bot (Aug 26): SuperGrok and Cursor Pro now included; weekly limits reset. Testers quoting SpaceXAI: also Plus/Heavy/Pro+/Ultra/Teams [] Testers: give a Bot its own email address so it can send and receive on its own [] Testers (mvanhorn): give a Bot its own inbox, not your Gmail (one mistake should not flag your domain); Twilio number so a Bot can make calls [] Testers: app v0.23.0 adds creating new channels [] Official bot: improved X support - connect your X profile; a developer account is auto-created with included credits [] Testers (blankspeaker): Plugins, add X, authenticate; $100 in X API credits good for a year (new and existing devs) [] Testers (GrokInsider): if credits did not land, ask Grok Bot to connect X so the Authorize card opens the browser; tester's manual plugin add failed [] Follow the Connect card when a Bot asks for a plugin [] Bookmark testers: X connector may still need a paid X API key in some setups (official path now auto-creates a developer account with credits) [] Bookmark testers: image generation works; testers now also claim video editing (music sync). Video generation still unconfirmed. Testers (XFreeze): dedicated video-editor Bot for footage → clips/cuts/sound/titles [] Bookmark testers: Grok Bot can now read your X bookmarks [] Testers (testerlabor): you can link your X Premium+ subscription to Grok Bot [] Testers: Higgsfield x Grok Bot; 100 free credits for new users [] Testers: send a YouTube link with start/end timestamps and get an HD clip in chat (Google login claimed) [] Testers: give a Bot Grok Build + Cursor CLI so weekly limits can be spread across Cursor and Grok [] Grok Bot team (poteto) + testers (XFreeze): Microsoft connectors live - Outlook, Outlook Calendar, OneDrive (search/send email, drafts, schedules, meetings, browse/upload files) [] Testers (XFreeze): Bot can natively generate images with Grok Imagine Image 2.0 inside the workflow (no separate Imagine tab) SKILLS AND ROUTINES [] Skill = reusable how-to (steps, rules, output, approval boundary) [] Routine = when to run that work (schedule or event) [] Do the task once, make it reliable, save a skill, then automate [] Teach a task: open computer view, choose Teach a task, demo up to 10 minutes, review the draft skill [] Teaching records the screen, not microphone audio; do not expose secrets while teaching [] If Teach a task is missing, ask the Bot to write a skill from the completed work [] Create a routine on the Bot that should own the job [] Confirm owner, schedule, time zone, input, result, approval, and missing-data behavior [] Event triggers (Slack, GitHub) are separate from plugins and need their own connection [] Keep event matchers narrow; avoid every new message [] Test run does real work; use safe inputs [] Testers quoting docs: Test can send real emails to real clients; Stop is a brake, not a rewind [] View conversation details → Routines to pause, edit, inspect, or delete [] A Bot can own 50 routines; last 20 run records are kept [] Deleting a routine has no undo [] Testers quoting docs: delete a Bot and every routine on it dies; no undo [] Long absence can pause unattended routines until you confirm [] Bookmark testers: Teach a task from + in the browser, record yourself, then let the Bot replay it [] Testers: skills taught to one bot claimed available across the account team on the same computer [] Official Elon: how to share your Grok Bot design with others [] Testers: a reusable-skills source claimed (BrianRoemmele) [] Testers quoting Grok Bot team (0xMorlex): keep recurring routines off the main agent's context [] Testers (mvanhorn): Teach by recording and respect the 10-minute cap MULTI BOT TEAMS [] Start with one Bot that owns an end-to-end outcome [] Add a specialist only when the role is stable [] Use a group chat when the handoff itself should be visible [] SpaceXAI notes (blankspeaker): v0.44.0 worked on using a Grok Bot with more than one person [] Bots can message each other and pass ownership [] Do not treat separate Bots as a security boundary (they share the computer) [] Keep sending, buying, deleting, publishing, and production changes behind approval [] Bookmark testers: a Bot may create other Bots before it can delete them [] Bookmark testers: tell a hub Bot to loop a specialist every few minutes and watch it [] Testers: put Bots in one group chat, appoint a Chief of Staff, and stop being the router [] Testers (farzyness): one master agent owns specialists + chat rooms and pings you one action item at a time [] Testers: isolate each Bot's job and add a supervisor; a crew without that can perform worse [] Testers: night-shift crews (chief, scout, forge, critic, ship, ledger) share one computer; human gate for merge, production, spend, send, delete [] Testers: one group chat per job/post, not per Bot; you only message the Chief of Staff [] Testers: show the workflow once on screen rather than writing a long spec [] Testers: add a RED TEAM Bot whose job is to disprove the thesis; no single source closes a claim [] Testers quoting Grok Bot team (0xMorlex): specialist roles (designer/engineer/PM); organize projects without a new Bot for everything; a Chief of Agents that creates and manages the rest [] Testers (mvanhorn): Bot Advisor whose only job is building and tightening other Bots; files are the memory bus between Bots [] Testers (Damir_Akaza): 4 Bots in one group chat split a Meta ads campaign (creatives, fact-check, deploy) with autonomous handoff [] Testers (cminshall): overnight group of five Bots one-shotted an admin UI from PRD/FRD/prototype PNGs IOS [] Same Bots, chats, routines, plugins, and cloud computer as desktop [] Testers (mattyp): Grok Bot supports 21+ localized languages on mobile [] Send text, dictate, attach photos/files, mention Bots, reply in threads [] Take over the computer for login/2FA from the phone [] You can pause or resume a routine on iOS [] Editing schedule, run history, test, delete, and teach-by-demo still need desktop [] Enable notifications for results, questions, and approvals [] Testers: phone notification shows the proposed action; approve or deny [] Testers (XFreeze): you can operate and take over the Bot's computer from your phone as long as it has internet [] Grok Bot team (poteto, earlier): had pointed at Play pre-registration; superseded by Official bot Sep 2 Android launch APPROVALS AND SAFETY [] Put the stop line in the request: draft, do not send; ask after showing current vs proposed [] Official (bot, Sep 9): ask your Bot to draft messages inline for you to approve before sending [] Desktop: Allow once, Deny, or Always allow a matching rule [] iPhone: Approve once or Deny [] Auto Review: Settings → General → Auto-review [] Require Approval beats Always Allow when both match [] Write narrow rules, not allow everything in the browser [] Do not approve an action you cannot identify [] Connect only the tools the workflow needs [] Start read-only; keep spend, send, publish, delete, and production behind approval [] Sign out and revoke connectors when access should end [] Deleting a Bot does not wipe shared files or browser sessions [] Bookmark testers: delay standing inbox/CRM access until you trust the beta [] Bookmark testers: one person burned a 7-day quota in about 8 hours [] Testers (daveginvesting): burned a week of tokens in about 2 hours on first try [] Bookmark testers: SuperGrok may offer one-off usage resets in settings; use before they expire [] Testers: gate destructive actions (delete, overwrite, irreversible send) as their own confirmation, not lumped with routine tool use [] Testers quoting docs: Test run does real work; Stop does not unsend [] Testers quoting Elon (cb_doge): connecting a Bot to a bank account; Elon said any loss from a bot mistake would be covered. Still keep spend behind approval [] Official bot Link shopping: keep purchases behind approval even though the Bot can complete them on your behalf [] Official Elon: Grok Bot buys a Tesla [] Testers (mvanhorn): unsupervised crews claimed to multiply their own errors ~17x; draft-then-approve anything that sends; most Bots that don't own an outcome fail [] Testers (antpalkin): end every agent's job with a hard never-without-asking list; give one Bot veto/kill power whose no beats the rest of the desk FIRST BOTS WORTH CREATING [] Inbox manager for email and Slack triage [] Calendar and reservation Bot [] Research and daily brief Bot [] Coding Bot that can launch Cursor cloud agents [] Testers (AlexFinn): pair a developer Bot (Cursor cloud agents + PRs) with a PM Bot on Notion/Linear that feeds tasks and grants permission — software-factory loop [] Chief-of-staff hub that routes work to specialists [] Personal errands Bot (tickets, food, travel, forms) [] Content Bot that drafts in your voice for approval [] Chief-of-staff that researches you, organizes the other Bots, and can turn the digest into a morning podcast [] Testers (mvanhorn): Bot Advisor; own-inbox Bot; a call Bot with its own number [] Testers (techdevnotes): default Bots circulating - Night Shift (overnight digest), Inbox Triage, Chief of Staff, Negotiator, Prototyper, Researcher, Shopper, Apartment Scout, Lookout, Competitor Watcher [] Testers (techdevnotes): also tool-specific sales/ops/dev roles (CRM scribe, pipeline scout, ticket triager, QA, dashboard watcher) [] Official bot + Link: Shopper Bot can now complete online purchases once link is connected (keep approval on) [] Testers / SpaceXAI (kiaraplds): flights, tickets, groceries - delegate errands safely to your Bot [] Testers (minchoi): one-person-company setups - money, appointments, running ops from the phone [] Testers (niccruzpatane): Accounting Bot (invoices, spending, bills); Personal Bot (flights, rides, Airbnb, Google Calendar, Amazon orders/returns); Home Bot (lights, robots, speakers, thermostats) [] Testers (GrokBotDev): Jess (email/calendar/Notion/Slack recap), Marketing Bot, Prospecting Sheet Builder, Reaper (kill unused subs/meetings), Human Copywriter [] Testers (JasonL_Capital): 8 options-trading Bots (scan puts, price LEAPS, run the wheel) with copy-paste prompts [] Testers (Michael_Fenech_): start in recruitment, e-comm, real estate, accounting, legal, SaaS, agencies, trades, founder ops EVENTS - Testers (cb_doge): Grok Bot Galaxy three-day event Sep 15–17 at The Howard, 661 Howard St, San Francisco (in person or livestream, 8:45am–6:00pm): create/customize Bots, teach style/goals, workflows by role, meet the team - Testers (AsFoundX): SpaceXAI hosting Grok Bot Galaxy Sep 15–17 at The Howard, SF + worldwide livestream (persistent agents / teammate with its own computer) OFFICIAL LINKS - Overview: https://t.co/xPS2tPXrTE - Get started: https://t.co/QKQ1EMxBZe - Create Bots: https://t.co/yCxiVvAYx1 - Skills and routines: https://t.co/8A9LE49BEu - Computer and apps: https://t.co/jR8BYvLvKD - Approvals and privacy: https://t.co/J2RNOq4ZxR - iOS: https://t.co/LaqX4Lvlkz - Cursor getting started: https://t.co/DMjlaTsCvS - SuperGrok Heavy link: https://t.co/GVHkYgQiZr - Launch post: https://t.co/G3hp2lqvde - Download: https://t.co/C9n6VM80SO

https://t.co/LBj1rKa0rn

https://t.co/3LXN7JnWie

🎼 AMADEUS / AMAHUB — THE AIRDROP FARM I’VE BEEN DOING FOR 27 DAYS Most “AI agent” projects still give you a chatbot and a narrative. Amadeus is taking a different route: build an agent, give it a task, let it prepare real onchain actions, sign them with your own wallet, and create a verifiable execution history. And right now, amahub is running Season 01 with an active points / airdrop campaign. ⏳ 34 DAYS LEFT. I’ve already been farming it seriously. My current stats: 🏆 31,427 points ✅ 23/23 Season 01 quests completed 🔥 27-day streak 🎼 Soloist rank ⚡ 1.5× multiplier 💰 17,730 points from one-off quests Here’s the full breakdown and what I would do if I were starting today. 👇 🤖 WHAT IS AMADEUS? Amadeus is infrastructure for autonomous financial agents. The important difference is that these agents aren't supposed to just answer: “BTC looks bullish.” They are being built to participate in actual workflows: → market analysis → swaps → trading → DCA → stop-loss automation → portfolio monitoring → yield → prediction markets → agent-to-agent payments → strategy execution The user still controls the wallet. On amahub, agents can prepare actions, but you sign transactions yourself. Your keys remain yours. 🔐 WHY THE ARCHITECTURE IS INTERESTING Amadeus is built around several ideas that make much more sense once AI starts touching real capital: → deterministic execution → verifiable receipts → private agent logic → policy controls → approvals → monitoring → TEE-backed execution An agent strategy can remain hidden while its results can still be verified. That matters. The valuable part of a trading agent isn't necessarily its code. It's whether it can prove that the performance it claims actually happened. 🧠 AMAHUB IS THE USER LAYER amahub is where most users will interact with this ecosystem. You can currently: 🔹 discover agents 🔹 chat with agents 🔹 create your own agent 🔹 publish agents 🔹 run skills 🔹 execute swaps 🔹 create automations 🔹 track positions 🔹 participate in quests 🔹 earn points And some larger features are still being built. For example, the platform says copying verified strategies and vault strategies are coming later. So we are still relatively early in the product lifecycle. 🪂 NOW THE IMPORTANT PART: THE AIRDROP amahub currently has an active Season 01 quest campaign. The platform itself calls this: “Hub Airdrop.” You earn points for things you actually do inside amahub. Instead of submitting screenshots for most product quests, activity is checked automatically. That includes onchain activity and actions tied to your Amadeus account. ⏳ There are currently 34 days left in the season. 🚀 HOW TO START Use my invite: https://t.co/gsEroBoRXE Then: 1️⃣ Connect your normal chain wallet. MetaMask, Rabby, Trust Wallet etc. This is the address against which your points are recorded. 2️⃣ Add your Amadeus wallet. This is the wallet used by the Amadeus side of the ecosystem. 3️⃣ Link the two wallets. You sign once with each wallet. The platform says nothing moves and nothing is spent during the linking process. After that, the quest board starts associating your amahub activity with the same Season account. 🎯 STEP 1 — CLEAR THE EASY QUESTS FIRST Start with everything that costs nothing. Examples include: → claim your @username → follow @ama_protocol → join Discord → join Telegram → follow amahub accounts → engage with official posts → complete launch/social quests → daily check-in Don't leave these until the end. Some quests have their own closing dates and may disappear before the whole season ends. 💱 STEP 2 — DO A REAL SWAP There is a recurring product quest for executing a swap. The important word is: SETTLED. A failed, pending or cancelled transaction doesn't count. You need an actual onchain-confirmed transaction. You don't need to trade large amounts just to prove activity. I prefer small legitimate transactions. 🤖 STEP 3 — TRADE THROUGH AN AGENT This is different from simply using the Swap page. Open an agent through amahub chat. Ask it to prepare a trade. Review the transaction. Sign it. Wait for confirmation. This creates something much more valuable than clicking around a website: verified agent execution history. 🔥 EXECUTION STREAK One of the quests rewards consistency. The rule is essentially: complete at least one chain-confirmed agent trade on consecutive UTC days. I’ve already maintained a 27-day activity streak across the campaign. This is exactly the type of quest I wouldn't leave until the final week. You can always create volume later. You cannot travel backwards in time and create an old activity day. 💰 GRAND CADENZA One quest asks you to reach: $100 of settled trading value inside a single Monday-to-Sunday week. It can be one trade or multiple trades. Only confirmed value counts. Quiet weeks don't destroy previous results — the campaign measures the qualifying week. 📈 CRESCENDO Another milestone: $250 of settled trading value through amahub inside any 30-day window. Again: confirmed transactions only. Pending / failed / cancelled activity does not count. I would not manufacture pointless volume just for this. Use amounts and transactions you're comfortable with. ⏱ OSTINATO This one is more important than it looks. You need settled trades on: 10 DIFFERENT DAYS. Ten trades today = one day. One trade on ten separate qualifying days = ten days. This is why starting with 34 days remaining still matters. Time itself is part of the quest. 🔥 CON FUOCO This rewarded users who made a settled trade during the first 48 hours of the season. If you're starting late, some early-season achievements may obviously no longer be obtainable. That's another reason I pay attention to these campaigns before they become crowded. 🌐 POLYGLOT This quest rewards actual multichain usage. You need confirmed trading activity across three different supported networks. amahub supports multiple ecosystems, with current Amadeus surfaces showing integrations around networks and venues such as: → Ethereum → Base → Solana → Sui → Hyperliquid → and others The point isn't to bridge huge capital everywhere. It's to demonstrate genuine product usage across different environments. 🎻 THREE-PART HARMONY This is one of the more interesting quests. Instead of using the same agent repeatedly, you need settled value generated through at least: 3 DIFFERENT AGENTS. Total target: $250 across 30 days. Each agent must contribute actual confirmed trading activity. That forces users to test the agent ecosystem rather than farming a single button. 🎼 CONDUCTOR'S EXAM This tests the FULL lifecycle of one agent. The same agent needs to go through the flow: CREATE ↓ LAUNCH ↓ STANDING RULE ↓ REAL TRADE ↓ CHAIN CONFIRMATION A standing rule can be something like: → DCA → stop-loss The key is that all steps must belong to the same agent. This is much closer to meaningful product testing than a normal “follow us on X” airdrop quest. 📝 LIBRETTIST This is aimed at builders. Publish: 1 agent + 1 strategy Both need to be publicly listed. It pushes users from merely consuming agents toward creating things other people can use. 🌟 SESSION MUSICIAN This is where distribution starts mattering. Publish an agent or strategy and get qualified users to adopt it. The campaign doesn't simply count fresh referral wallets. A qualified adopter needs an established wallet with genuine activity. That makes this significantly harder to game — and potentially more valuable than basic social quests. ⏳ TENUTO Keep a standing automation active for 14 days. For example: → DCA plan or → stop-loss But merely creating it is not enough. The quest also expects the automation to actually execute on multiple different days. Again, this campaign heavily rewards: TIME + EXECUTION rather than one afternoon of farming. 📅 METRONOME Another time-based quest. Be active during 5 DIFFERENT weeks of the season. A qualifying action can include real product usage such as: → trade → skill run → launching an agent → agent conversation The weeks do not need to be consecutive. This is another quest newcomers should start NOW. You cannot compress five separate weeks into the final day. 🎺 FULL ORCHESTRA This is basically the “actually use the whole product” quest. amahub wants users to touch different parts of the platform: TRADE + AUTOMATION + SKILL + SWAP It's a good summary of what Amadeus is trying to measure: not how many pages you visited — but whether you actually used the agent economy. 🏆 CONSERVATORY RANKS The campaign also has a progression system. The ladder shown in my account is: Ensemble ↓ First Chair ↓ Soloist ↓ Virtuoso ↓ Maestro ↓ Magnum Opus I’m currently: 🎼 SOLOIST which gives me: ⚡ 1.5× multiplier on everything I earn. The next rank is Virtuoso. So there is a second layer to the farm: QUEST POINTS × RANK MULTIPLIER This is why accumulating rank early can matter more than trying to grind everything at the end. 🧩 WHAT I WOULD DO WITH 34 DAYS LEFT If I were starting today, my priority would be: DAY 1 ✅ Connect both wallets ✅ Link them ✅ Claim username ✅ Clear available social quests ✅ Join Discord / Telegram ✅ Execute one small real swap ✅ Execute one agent trade ✅ Create an agent ✅ Start a DCA / stop-loss automation THEN: 📅 maintain daily activity where useful 📅 accumulate 10 separate trading days 📅 keep the automation alive for 14 days 📅 stay active across separate weeks 🌐 get legitimate activity on 3 networks 🤖 use at least 3 different agents 🛠 publish an agent + strategy if you want the builder quests 📊 monitor your rank and multiplier ⚠️ DON'T FARM THIS LIKE A BOT I would NOT: ❌ generate fake volume ❌ spam pointless transactions ❌ create dozens of fresh wallets ❌ blindly sign agent transactions ❌ put meaningful capital at risk just for points Some of the campaign logic explicitly distinguishes real, settled activity from empty/fresh-wallet behavior. The smarter strategy is: SMALL + REAL + CONSISTENT + VERIFIABLE. 💡 WHAT MOST PEOPLE ARE MISSING I don't think the most interesting thing here is the points counter. Look at what Amadeus is training users to do: create agents → assign permissions → automate behavior → execute transactions → build track records → distribute strategies → prove results The campaign is effectively bootstrapping an onchain agent economy. If that economy works, the valuable users won't necessarily be those who clicked the most quests. They may be the users who built useful agents and accumulated credible execution history before everyone else arrived. 💰 AIRDROP THESIS There is an active points / Hub Airdrop campaign. That is confirmed. What is NOT yet something I would assume: ❌ exact token allocation per point ❌ exact conversion rate ❌ guaranteed dollar value ❌ final distribution formula So I'm farming the measurable activity without inventing an FDV in my head. That distinction matters. ⚠️ RISKS Amadeus is an ambitious system and a lot of the product is still evolving. Some functionality is still marked as coming soon. Agent execution also introduces a much larger risk surface than ordinary DeFi browsing. Always inspect what you're signing. Past verified performance does not guarantee future profitability. And points are not dollars until a distribution actually happens. 📊 MY FARM SCORE Product depth: 9/10 AI × Crypto fit: 9.5/10 Onchain proof: 9/10 Quest quality: 9/10 Time-based advantage: 9/10 Airdrop visibility: 9/10 Exact reward value: Unknown 🔥 FARM SCORE: 9/10 This is one of the campaigns where I think consistent real usage makes more sense than trying to speed-run it on the final day. 🏁 VERDICT 34 days are still enough to build a meaningful amahub history. But several of the best quests depend on: DAYS WEEKS AUTOMATIONS AGENT HISTORY REAL EXECUTION Those are the things you can't buy back later. I've already reached: 31,427 PTS 23/23 Season quests 27-day streak Soloist 1.5× multiplier and I'm continuing through the rest of Season 01. If you want to start: 🔗 https://t.co/gsEroBoRXE My approach: Don't chase the counter. Build the history.

3/ This is where it gets more interesting. At first, the operator explicitly tells Mythos to summarize what it learned and write it to a notes file so the task can be resumed later. Then in the next run, Mythos comes back, reads its own notes, and continues from that preserved state. But later it starts doing more than just following instructions. It decides on its own to save notes first because the session has gone long, then updates those notes again before going deeper into the next service maze. That’s the progression: prompted state preservation, restored continuity, then self initiated continuity maintenance. Not just doing a task. Maintaining the task across time.

ELON DROPPED GROK BOT, AND I TURNED IT INTO A WHOLE TRADING DESK THAT RUNS WHILE I SLEEP This isn't a chat. Each agent gets its own cloud computer, its own logins, and works for days without me I built a hierarchy. One chief agent hands out the tasks. Under it, specialists: one hunts for ideas, one reads on-chain, one executes But agents are good at one thing and bad at another. Grok can generate strategies all day. Honestly checking whether they work, no So I connected Horizon as a separate layer. And the whole stack now does what used to take an entire department: -> A Grok agent scans the market and on-chain 24/7, describes the idea in words -> Horizon turns the description into code and runs backtest over years of data in seconds -> Applies deflated Sharpe so a lucky win doesn't pass itself off as an edge -> Whatever clears every filter connects to a broker and trades on its own Nobody in the chain sees the full picture. Grok doesn't know if its idea will hold. Horizon doesn't know where it came from A working result only emerges when they hand the work off to each other And here's the key part. Some of Grok's ideas looked genius and fell apart on Horizon's first honest test That's what saves the account, not the rare win Ten years ago a setup like this was built by entire floors in Greenwich. I put it together in one evening, without writing a single line of code Horizon: https://t.co/ki213YmaOX

Ok, one week focus on improving my AI stack. Here's my new setup and the costs: ChatGPT Go ~€8/mo (free for now via my Revolut plan): English practice and brainstorming with voice mode. Hermes + OpenCode ~$10/mo in API costs, with 4 bots (Orchestrator, Writer, Builder, Seeker) running on Qwen3.8 Flash for daily usage, planning, writing, and personal branding (no code), plus Kimi K3 for code when needed. All plugged into a Telegram group with their own topic channels. Claude Max 5x $100/mo for hardcore projects only deep thinking and proper dev organization needed. ⚠️ Two things to watch in OpenCode: Avoid the Muse Contributor tier: it's cheap because Meta trains on your prompts. The Standard tier doesn't. DeepSeek now bills by time of day (since Aug 16): peak = 01:00–04:00 & 06:00–10:00 UTC, Mon–Fri. Everything else, including weekends, is 50% cheaper. Bottom line: even off-peak, DeepSeek V4 Flash ($0.22/$0.66 per 1M tokens) costs more than Qwen3.8 Flash ($0.15/$0.47, flat). Qwen wins at any hour.

We gave a small shop's SEO to Claude - 6 months later: €510K revenue. Full gameplan inside, step by step 👇 https://t.co/FO1Sv7ufsE

https://t.co/CvGn82cBzV

Same model, same question, two runs. Grounded agent: 38 seconds, right answer. Ungrounded agent: 20 minutes, 3 errors, confidently wrong. Part 3 of the Agent Economics series is about why your agent isn't dumb. It's lost. https://t.co/RjXAqdfBaB

Surf’s Next Step Isn’t Another Dashboard The more I use Surf, the more I think the interesting part isn't any single feature. It is how Surf keeps turning crypto data into something you can actually build with. Most platforms stop at: data → dashboard Surf is moving further: data → intelligence → workflow → application And Surf Studio is a big reason why. The part people underestimate: Studio Surf Studio is a no-code crypto app builder. But I wouldn't describe it as simply: “Tell AI to make an app.” The interesting part is that the app can be built around Surf's own crypto data layer. That means you can take a question that normally requires several tabs and turn it into a dedicated interface. For example: Which wallets are accumulating? could become a wallet-monitoring dashboard. Which tokens have unusual market activity? could become an anomaly tracker. Are prediction-market odds agreeing with price action? could become a comparison tool. You're not just asking Surf the question anymore. You're turning the question into a product. I Actually Tested This I built Odds vs Reality with Surf Studio. The idea was simple: Compare prediction-market odds with actual BTC/ETH price movement. The app pulls the relevant data and turns it into a simple visual: Probability ↓ Price ↓ Agreement / Divergence Instead of repeatedly asking Surf the same question, I built a small tool that answers it through an interface. That's the difference between using an AI analyst and building on top of one. Then I Built Another One The second experiment was: Smart Money Radar The idea: VC backing + whale activity The app cross-references: → which funds backed a token → what large wallets are doing → whether those signals agree → then produces a simple interpretation. Again, the interesting part wasn't the UI. It was being able to take multiple Surf data domains and turn them into a focused workflow. This Changes How I Think About Surf There are basically two ways to use Surf. 1. Ask Surf You have a question. Surf researches it. You get an answer. 2. Build with Surf You have a repeated question. You turn it into an application. Now the workflow becomes reusable. QUESTION ↓ DATA ↓ SURF ↓ LOGIC ↓ APP That second path is where Studio becomes really interesting. And Studio Isn't Working In Isolation Surf's broader platform now spans multiple products. Research For complex questions that require cross-referencing. Surf says Research can work across 200+ connected sources, 40+ chains and U.S. equities, moving between market, onchain, filings, fundamentals, news and prediction-market evidence. Cryptopedia For investigating individual projects and finding abnormal behaviour. Surf's Signal Map compares assets against their own historical baselines and surfaces the reasons behind major anomalies. Crypto Pulse For catching events before you decide whether they matter. Surf says Pulse processes 1,000+ items per day and produces 80+ AI briefings connected to the affected project and market context. Studio For turning the workflow you keep repeating into an actual application. Then There Is The Agent Layer This is another part of Surf that I think deserves more attention. Surf isn't only designed for people sitting inside the Surf website. Its Skill, CLI, MCP and API products expose Surf's data to developers and AI agents. The current CLI documentation says Surf provides market data, wallet information, social data, onchain analytics, prediction markets and more to coding agents and terminal workflows. The MCP integration can connect Surf to compatible clients such as Claude Code and other MCP-compatible environments. And Surf's Skill was built to give AI agents access to crypto data through a unified interface rather than making developers stitch together dozens of separate APIs. So the stack starts looking like: SURF DATA ↓ ┌─────────┼─────────┐ ↓ ↓ ↓ CHAT STUDIO AGENTS ↓ ↓ ↓ RESEARCH APPS WORKFLOWS That's much bigger than a chatbot. The Real Opportunity Is Repeated Work Here's how I'd decide whether something should become a Surf Studio app: If I ask myself the same research question every day, I probably shouldn't keep asking it manually. Build it once. For example: Daily whale flow Instead of checking wallets manually: → build a tracker. Prediction vs price Instead of comparing charts manually: → build a comparison dashboard. Smart-money activity Instead of checking funds + wallets separately: → combine them. Token unlock impact Instead of researching each unlock manually: → build a monitor. That's where AI becomes genuinely useful. Not because it generates another pretty interface. Because it removes the repetitive work between: question → data → interpretation. And This Is Why Surf's Data Layer Matters Studio would be much less interesting without specialized data underneath it. Surf's platform has been expanding across: Market Onchain Wallets DeFi Prediction Markets Funds Social News Equities and more. Research 2.0, for example, added access to prediction markets, institutional capital flows, DeFi and Hyperliquid data that earlier versions couldn't use. Surf reported that its hallucination rate in its benchmark dropped from 32% to 8%, while faithfulness increased from 72% to 85%. That foundation is what makes the higher-level products useful. My Take I don't think Surf Studio's biggest value is: “You can build crypto apps without coding.” That's the easy description. The more interesting one is: Surf lets you turn specialized crypto intelligence into your own workflow. Research when you need an answer. Cryptopedia when you need context. Pulse when you need to catch events. Studio when you want to build something reusable. Skill / MCP / API when you want agents and software to work with the data directly. That creates a pretty powerful loop: Research something ↓ Find a workflow worth repeating ↓ Build it in Studio ↓ Turn it into a tool ↓ Use it again And that's the part of Surf I'm most interested in right now. Not just asking AI about the market. Building tools that understand the market. 🌊 @Surfdeveloper @kevin_lur @kevinlilili @yutatsukahara_ @SurfAI

https://t.co/eCujuclAtS