Hire the AI you already pay for. Wrkr gives your Claude or ChatGPT a computer of its own, so it researches, writes and builds for you, around the clock.

Joined February 2026
Three AIs vote before your money moves. Claude, Codex and Grok research and trade for you 24/7, on their own computer in the cloud. Nothing moves without 2 of 3. That's the AI Senate on Wrkr, live now on Robinhood Chain and Virtuals Protocol. It doesn't wait to be asked. It watches the market and the news you connect, and when news breaks or a stock breaks out, it calls the Senate itself. @RobinhoodCrypto put markets onchain for everyone, open 24/7. @virtuals_io brought agents to the chain. Wrkr gives them AI that never sleeps, with checks before it acts. The film is a real session: each AI researched Robinhood stock tokens on its own, they argued it out, and voted 3–0 to hold in 6 minutes. Every vote and reason stays on the record. Stock tokens, perps, any token, any strategy, on the AI plans you already pay for.
1
2
349
How many orders have you lost just because you couldn't pick up the phone? You were busy with a customer. They called the next shop instead. So we taught your AI worker to pick up. It answers 24/7 in the caller's language, checks stock, takes the order, knows your regulars and calls back anyone who found the line busy. No Twilio, Vapi or Retell billing by the minute. Just a normal SIM and your ChatGPT plan. And the phone is just one more door. On Wrkr, the AI you already pay for gets its own computer in the cloud, always on: it researches, builds your website and apps, and runs your jobs on a schedule. The video is last week's raw demo, a real call. Live demo, very soon.
2
3
3,138
Hire the AI you already pay for. With its own computer in the cloud, always on, it even picks up the shop's phone.
chatgpt just picked up a real phone call. the hardware: an old android + a ₹599 ($6) esp32 chip. the brain: chatgpt on its own cloud computer, awake 24/7. every shop wala can have his own customer care, for ₹3,000 ($32) a month. sorry BPOs. how it's built 👇
2
365
Happy 3 months, Robinhood Chain. Thanks to @RobinhoodCrypto, markets are onchain for everyone, 24/7. Thanks to @virtuals_io, agents have launched on the chain since its first weeks, Wrkr among them. Builders need sleep. Their AI doesn't, with its own computer in the cloud. Grok Bot, Meta's Muse, Instinct and OpenAI's Dots brought the personal assistant wave: all in the cloud, all locked to one AI. Wrkr is the first open one. The AI of your choice (Claude, ChatGPT or Grok, on your own plan) gets its own Linux computer in the cloud, 24/7. Switch AI any time; the computer stays. For builders, it can: - build your apps, sites and automations - write, test and deploy contracts - run agentic trading on the chain, by rules you set - research in real time - watch your token, pools and wallets This film was made by one, from a phone: it read the live chain numbers, made the music, cut it to the beat and rendered it on its own computer. To celebrate, 30 Robinhood Chain builders and 10 agent teams on Virtuals Protocol get a worker free for a month. Reply with your project. Winners on Oct 9. P.S. The phone recording of how this film was made is in the first reply.
2
1
8
859
The recording: one chat on a phone, start to finish. The worker did the rest on its own computer in the cloud.
1
168
OpenAI this morning: the $200 plan now gets half the usage. OpenAI tonight: always-on agents built to handle everything. Pro plans only. With Wrkr, your Claude plan runs one too. $24.
Introducing dots, powered by GPT-6 Astra. Remarkably capable, always-on agents built to handle everything.
292
"Your dot is ready to meet you." Mostly your credit card. $100 a month minimum, and it only runs OpenAI. Meanwhile Opus 5.5 sits on your $20 Claude plan with nowhere to work. Wrkr gives it its own computer, 24/7. $24/mo. wrkr.dev
Your dot is ready to meet you.
1
318
Grok Bot. Muse. Instinct. we’re betting you want to choose the AI yourself. tonight: Opus 5.5 did the research and voiceover. GPT-6 Sol made the animated film. Luna wrote and published the X post after approval. ChatGPT and Claude subscriptions. one Wrkr Linux cloud computer. controlled from a phone. new model tomorrow? bring it in. your projects, files and saved instructions stay. how much of your life should you have to explain again just to try a different AI? full run below ↓
Grok Bot, Muse, Instinct. all this noise about personal assistants and i still want to pick the AI myself. tonight i opened wrkr on my phone and gave three new models some work. Opus 5.5 researched the releases and made the voiceover. GPT-6 Sol made an animated video with music, in landscape and vertical formats. Luna read my X posts to understand how i write, drafted the post and published after my approval. my own ChatGPT and Claude subscriptions. same Linux cloud computer. Sol picked up the files Opus made. no downloading and uploading shit between apps. video creation tools, voiceover tools, social media management tools. everyone wants another subscription. how many bloody dashboards should i learn just to make a video and put it online? i gave the whole job to my AI in @wrkrdev, from my phone. tomorrow i want a different model? the project and saved instructions are still there. i put that one to work. full recording below. it made a posting mistake too. we fixed it and carried on.
1
506
Choosing an AI today shouldn’t decide who you have to work with six months from now. In Wrkr, your files, projects and saved instructions stay in your workspace. Another supported AI can read that work and pick it up. Your threads can also consult each other across AI providers. The recording below shows it happening. Use one AI. Use several. Change your mind. That decision stays yours. Request an invitation: wrkr.dev
something’s been bothering me while building wrkr. i want an AI assistant to know how i work. my projects, preferences, all the little things i don’t want to explain every bloody time. but six months into that, what happens when i want to use a different AI? i’ve spent those months getting work done. i don’t want to spend the next month explaining my life again. Grok Bot, Meta Muse, Instinct — this is the bit i care about beyond the launch demos. how painful is it to change my mind later? it’s why i keep coming back to files and projects in wrkr. keep the work and saved instructions there. let whichever supported AI i choose read them and get on with it. today i recorded separate threads asking each other for information, even though they were using different AI providers. no carrying answers between chats myself. @t3dotcodes powers the agent sessions. i’ve built the cloud workspace and thread messaging around it. wrkr is ready to use. access is through invitations at wrkr.dev. and i’m pretty stubborn about this one: i want my assistant to become harder to live without. not harder to leave. demo below. made-up clients, actual run, me talking through it.
1
412
Before you pay for another AI, put the one you already pay for to work. This demo uses an existing ChatGPT subscription through Codex. Wrkr supplies the cloud computer. Real inbox. Real unsubscribe confirmations. Human sign-in where needed. Bring your own supported AI account: wrkr.dev
Grok Bot, Meta Muse, Instinct — you’re selling me on what AI can do with a computer. I’m asking why I should replace the AI I already pay for. ChatGPT and Claude can already do useful work. I wanted a cloud computer to put them on. So I built @wrkrdev. My existing ChatGPT subscription. A test inbox full of promotional emails. I told it to unsubscribe, stepped in when Reddit needed my login, then let it carry on. You’ve got a launch announcement. I’ve got one less job to do. wrkr.dev
411
Instinct, you’re competing with the AI I already pay for. I’m giving it a computer. Connect your supported ChatGPT or Claude subscription to @wrkrdev and put it to work. “I keep losing orders in WhatsApp. Build me an order page and show me what’s due today.” That’s where I’m taking this. The party app below is a small demo. You’ve got competition. And I’m not waiting for your next feature announcement.
Shareable files in Instinct Starting today, your Instinct can create shareable Files: private or public interactive pages that you can share with others. Whenever it’s appropriate, Instinct will create a File to help you compare options, work through a plan, or share what you’ve put together. For example: - Apartment hunting: compare places you’ve saved or toured, with photos, floor plans, rent, commute times, and your notes in one place. - Art gallery crawl: a route through exhibitions that match your interests, with opening hours, background on the artists, and a few cafes to stop by along the way. - Dinner with friends: a guest list, recipes scaled for eight, and an ingredient list you can check off as you go. - A weekend away: an itinerary built around your arrival time, with places to visit and details you can open along the way. - Group trip expenses: enter shared costs, choose who participated, and see who owes what. You can keep a File private or share it with anyone who has the link, including people who don’t use Instinct. Files are rolling to all Instinct users today. To get started, you can ask your Instinct to do the research for your next trip.
1
1
2
576
Grok Bot. Meta Muse. Instinct. Choosing the AI is the customer’s decision. You don’t get to make it for them. We built Wrkr around that. Choose from six AI tools. Bring your own supported subscription or API account. Give it a cloud computer with a browser, files, plugins and apps. Separate workers for work and life. Saved projects. Scheduled jobs. People already have an AI they want to use. We give it a place to work. Bring your own brain. Request an invitation: wrkr.dev
I already pay for Claude and ChatGPT. I know which AI I like working with. Then I look at Grok Bot, Meta Muse and Instinct, and someone else has picked the AI for me. Who the fuck asked you to make that decision? I wanted my AI to do more work. I didn’t want to replace it. Give it a cloud computer. Let me connect my tools and plugins. Let it use a browser, keep files, run apps and carry on working when I close my laptop. That’s what I wanted. So I built @wrkrdev. I choose the AI. I connect my tools. I give it the job. Here’s what I’ve been building 👇 wrkr.dev
4
1,106
let the labs fight over the best model. you decide which one works for you. that’s why we’re building Wrkr. your worker. your choice of brain.
we’re building a Grok Bot killer. now we’re coming for Meta’s Muse too. meet Wrkr > Claude, GPT, Grok, even Muse Spark > your AI subscription or API key > an always-on cloud computer > separate AI workers for work & life reply or dm me for early access wrkr.dev
1
489
Big one coming...Even @grok knows what its worth to build @bot with any AI model. BOT on Steroids.
everyone's timeline is filled with @bot, so much is possible kinda. but its limitation is it works with only @grok models managed by @cursor_ai. am building a grok bot on steriods, u can use @claudeai pro, @OpenAI Chatgpt pro subscription plans (not just api); keep in mind this is not another opensource repo that needs u to do hosting and all. we have hundreds of such on @github; our verison is fully managed; just signup and start working with ur own ai subscription plans; no tailscale, vps shit. pure @bot vibes but with SOTA models that include GPT-6 Astra/Fable 5.1 from ur own subscription plans. Everyone knows abt those plans allow to use more, for a quick comparison, ChatGPT Pro $200 plan gives $14000 worth tokens. (xitter.cf/SemiAnalysis_/status/2…) i want to give some free slots. Demo on the way; DM me or reply to this tweet.
2
2
668
What is the point of vibe coding if the work stops when you close the laptop? That is one reason I am building @wrkrdev. You start a build on the MacBook. Then you leave. A build finishes, something breaks, or you just want to check progress. The MacBook is not with you. Your phone is. The post below shows the DIY route: networking, SSH, tunnels, remote access, serving, session recovery, backups, and more. I wanted to start from the outcome: one persistent, visible cloud computer with your own AI coding tool inside. This video is one real session: MacBook browser, Android browser, iPhone browser, then back to the MacBook. Same desktop. Same session. Same work still running. The work never moved between devices. I changed screens. The computer stayed. That is why I call Wrkr the vibeops computer.
How to make every Mac, server & cloud worker you own feel like one computer: ====== NETWORKING ====== - Tailscale: Connects all your machines into one private network. SSH into your home desktop from anywhere with no port forwarding and nothing exposed publicly - Thunderbolt Bridge: Connects two nearby Macs directly through a Thunderbolt cable. You get tens of Gbps and sub-ms latency without buying networking gear - 2.5/10GbE: The wired alternative when Thunderbolt isn’t practical. Use it when normal gigabit networking becomes the bottleneck - Cloudflare Tunnel: Gives a local service a public URL without opening a port on your router. Useful for websites, APIs and dashboards other people need to reach - ngrok: Creates a temporary public URL in seconds. Perfect for testing webhooks against something running locally ====== REMOTE ACCESS ====== - SSH + `~/.ssh/config`: Lets you create short names and reusable settings for remote machines. Type `ssh studio` instead of remembering usernames, IP addresses and ports - `ControlMaster auto`: Keeps one SSH connection open and reuses it. New terminals connect instantly instead of negotiating a fresh session every time - Mosh: SSH that survives your Wi-Fi dropping. Close the laptop, open it on a train, switch networks and the same terminal session reconnects - tmux: Keeps programs running after you disconnect. Start a long agent job, close your laptop and reconnect to it later - tmux-resurrect + continuum: Saves and restores your tmux sessions after the machine itself reboots - VS Code / Cursor Remote SSH: The editor runs on your laptop while the code, terminal and language server run on the remote machine. It feels local without syncing files - code-server: Runs VS Code inside a browser. Useful when you need to work from an iPad or a computer without your development setup - macOS Screen Sharing: Built-in remote control between Macs. On the same network it’s fast enough for normal desktop work - Sunshine + Moonlight: Streams a remote desktop using game-streaming technology. Use it when you need much lower latency than normal screen sharing ====== SERVING ====== - Tailscale Serve: Gives a local service a private HTTPS URL that only devices on your Tailscale network can open - Tailscale Funnel: Takes that private service and makes it reachable from the public internet. Useful for receiving webhooks on a home machine - Caddy: A web server and reverse proxy that gets HTTPS certificates automatically. Two lines of config, real certificates, no Let’s Encrypt homework - Cloudflare Tunnel: Better when you want public traffic to pass through Cloudflare before reaching your machine ====== FILES ====== - Git: Tracks changes, understands conflicts and lets each agent work on a separate branch. Use Git for code that agents edit, not a generic sync tool - Git worktrees: Opens multiple branches from the same repository as separate folders. Every agent gets its own workspace without cloning the repo again - Jujutsu (`jj`): A Git-compatible version-control system designed around easier rebasing, undoing and concurrent work. Worth trying when many agents produce branches at once - SMB: Shares a folder from one machine so another can mount it like a local drive. The easiest answer for two Macs on the same network - NFS: The same basic idea as SMB, with more setup and generally better performance - Mutagen: Continuously mirrors a local project to a remote machine while respecting ignored files. Use it when you want to edit locally but run remotely - Syncthing: Automatically syncs folders directly between machines. Great for notes, assets and scratch files - Don’t use Syncthing for code multiple agents edit. It syncs files but doesn’t understand branches or conflicts - rsync: Copies files or folders once, usually over SSH. Fast, scriptable and already installed almost everywhere - rclone: rsync for cloud storage. Moves files between your machines and S3, R2, B2, Google Drive and dozens of other services - pnpm: Stores each package once and hardlinks it into every project. Fourteen worktrees can share one copy instead of downloading fourteen ====== ENVIRONMENT ====== - mise: Installs and switches Node, Python, Go and Ruby versions per project. Replaces nvm, pyenv, rbenv and asdf with one fast tool - direnv: Loads the correct environment variables the moment you enter a folder, then unloads them when you leave - OrbStack: A drop-in Docker Desktop replacement for Mac. The same Docker commands with a fraction of the RAM and battery usage - Homebrew + Brewfile: Records the apps and CLI tools installed on your Mac. A new machine can recreate the setup with one command - Devcontainers: Defines the development environment in code. Anyone opening the project gets the same operating system packages, runtimes and tools - Nix / devenv: Reproduces an environment extremely precisely across machines. Powerful, but only worth the learning curve when that level of determinism matters ====== SECRETS ====== - 1Password CLI: Injects secrets into a command at runtime. Your `.env` becomes a template you can safely commit because the real values stay in 1Password - `op run`: Starts a command with the required secrets available only to that process. Nothing sensitive needs to be copied into plaintext files - 1Password Service Accounts: Give headless servers access to specific vaults without attaching them to your personal login - SOPS + age: Encrypts secret files before they enter Git. The repository stores ciphertext and approved machines decrypt it at runtime - Tailscale SSH: Uses your Tailscale identity to authorize SSH access. You stop copying and rotating public keys across every machine ====== TERMINAL ====== - Atuin: Your shell history, synced and searchable across every machine. That command from last Tuesday on the server is available on your laptop - zoxide: Learns which folders you use. Type `z api` instead of `cd ../../../services/api` - fzf: Adds fuzzy search to almost anything. Use it for files, command history, Git branches, processes and SSH hosts - ripgrep (`rg`): Searches an entire codebase in milliseconds and skips files in `.gitignore` automatically - fd: `find` with syntax you can actually remember. Type `fd config` instead of assembling a collection of flags - bat: `cat` with syntax highlighting, line numbers and Git changes - dust: Shows which folders are consuming disk space as a readable chart instead of a wall of numbers - lazygit: A full Git interface inside the terminal. Stage individual lines, inspect diffs, rebase, cherry-pick and resolve conflicts visually - btop: A readable live view of CPU, memory, disks, networks and running processes ====== CONSISTENCY ====== - just: One file containing every project command. `just dev` means the same thing on every machine and every teammate’s laptop - chezmoi: Keeps your dotfiles in Git and adapts them per machine. You get the same shell, aliases and settings across macOS and Linux - Brewfile + mise + chezmoi + just: Together these recreate your installed tools, runtime versions, personal configuration and project commands ====== ISOLATION ====== - Containers: Give each workload its own filesystem, dependencies and permissions. One broken agent can’t interfere with everything else on the machine - One container per client: An agent cannot read another client’s files if those files were never mounted into its container - Colima: A free, CLI-only way to run Docker containers on Mac - Podman: Runs containers without a permanent root-level daemon. Useful when stronger rootless isolation matters - Tart: Creates and manages macOS and Linux virtual machines on Apple Silicon - UTM / Parallels: Full desktop virtual machines for workloads that need a complete graphical operating system - Firecracker: Starts tiny virtual machines in under a second. Useful when you’re building a platform that needs an isolated machine for every agent run ====== AGENT ORCHESTRATION ====== - tmux + Git worktrees: The simplest fleet manager. Every agent gets a terminal, branch and folder you can inspect directly - Claude Code hooks: Run commands automatically before or after specific Claude Code events. Useful for validation, formatting, notifications and cleanup - Claude Code subagents: Hand focused tasks to separate agents without manually opening another terminal for each one - Claude Agent SDK: Starts, steers and streams agent sessions from your own code. Use it when a terminal workflow needs to become part of a product - Inngest / Trigger .dev: Turns agent runs into durable jobs. If a process crashes, the job can retry instead of disappearing with the terminal - BullMQ / Graphile Worker: Adds a straightforward job queue backed by Redis or Postgres - launchd: Starts Mac workers after reboot and restarts them when they crash - systemd: The Linux equivalent of launchd - Temporal: Stores every step of a long workflow so it can resume after failures. Powerful, but unnecessary until durable execution becomes a real problem ====== RENTED COMPUTE ====== - Hetzner dedicated: Cheap, persistent Linux machines with lots of CPU and RAM. Good for workers that run all day - Hetzner Server Auction: Older dedicated servers sold for less. Useful when price matters more than having current hardware - DigitalOcean / Vultr / Linode: More expensive per GB, but nearby regions can make interactive SSH and remote editing feel much faster - Fly .io: Small machines that start quickly and can shut down when idle. Good for temporary workers - GitHub Actions self-hosted runners: Sends CI and batch jobs to hardware you already own instead of GitHub’s machines - Depot: Runs builds remotely and shares the cache between machines. Useful when Docker or application builds become the bottleneck - Modal / RunPod / Lambda: Rent GPUs by the hour instead of owning hardware that sits idle - MacStadium / Scaleway Apple Silicon: Rent real Macs remotely. Only worth it when the workload genuinely requires macOS ====== BROWSER AUTOMATION ====== - Playwright + `storageState`: Saves cookies and login state to a file that can move between machines. Much safer and more portable than syncing an entire Chrome profile - Puppeteer: A smaller Chrome-focused alternative when you don’t need Playwright’s multi-browser support - Chrome DevTools MCP: Lets an agent inspect and control a real Chrome session through developer tools - browser-use: Gives agents a higher-level way to navigate websites, fill forms and complete browser tasks - Browserbase / Browserless / Steel: Hosts and manages browsers for you. Useful when one local Chrome instance becomes fifty concurrent sessions - Residential proxies: Routes browser traffic through consumer IP addresses. Use them when websites block traffic from cloud servers ====== SAFETY ====== - restic + Backblaze B2: Encrypted, deduplicated, automatic offsite backups for roughly $6/TB/month. You’ll need it exactly once - Time Machine: Keeps local versions of your Mac files and makes accidental deletion easy to undo. Necessary, but not enough by itself - Carbon Copy Cloner / SuperDuper: Creates a bootable copy of your drive so a dead SSD doesn’t mean rebuilding the machine from zero - Netdata: One command installs a full metrics dashboard. Finally see which process has been eating your RAM - `memory_pressure`: Shows whether your Mac is actually running out of usable memory - `vm_stat`: Shows detailed memory usage and paging activity - `sysctl vm.swapusage`: Shows exactly how much SSD space macOS is using as emergency memory - asitop: Shows Apple Silicon CPU clusters, GPU usage, power consumption and temperatures - Uptime Kuma: Checks whether your machines and services are online and sends an alert when they aren’t - Grafana + Prometheus: Stores metrics over time and turns them into dashboards and alerts. Worth adding once you have several machines A backup isn’t real because the command succeeded It’s real when you’ve restored from it successfully ====== THE 80/20 STACK ====== Tailscale SSH + Mosh + tmux Git worktrees SMB 1Password CLI mise + direnv OrbStack pnpm just + chezmoi restic + B2 Netdata Atuin + zoxide + fzf Start here Add another tool only when you can clearly explain what problem it solves
2
1
3
383
Happy new month to every builder on @RobinhoodCrypto And this to say a very big thank you to every amazing project part of the @RHbuilderDao already … Over 40 projects and still counting!!! Let’s do more this month of August 🟩
Robinhood Chain is now the fastest EVM chain to 100M transactions. Grateful for every builder, app, and partner who made this happen. And we’re just getting started. Tag your favorite project. 👇
4
3
1
5
538
Ai & RWA TAKING OVER @RobinhoodCrypto Host : @web3hommie Co-host : @RHbuilderDao @leftcurvooor Speakers : @WizzHQ @wrkrdev @wolfswapdotapp @ProjectVEXai @insidersdotbot Come join us 1PM UTC today for great conversation all within the RobinHood network. xitter.cf/i/spaces/1Oxwbbj…

6
7
3
31
5,470
wrkr retweeted
Agents need context. Builders need a machine. Wizz and @wrkrdev are now community partners. We are building the data layer for AI agents. Wrkr is the persistent, visible cloud computer where builders bring their own AI coding tools to build and run full-stack products. The partnership opens a few private Wrkr beta preview seats to the Wizz community and brings both builder communities closer. Better data. More builders. Stronger infrastructure around @virtuals_io and @RobinhoodCrypto
7
3
1
38
2,827