Runwork (@runworkai) header
Runwork (@runworkai) profile picture

Your team cloud behind your ChatGPT, Claude, Cursor, 60 more agents and whatever comes next. Compound your skills, integrations, automations, vibe-apps and more

New York, NY
Joined January 2026
Photo by Runwork (@runworkai)Photo by Runwork (@runworkai)Photo by Runwork (@runworkai)Photo by Runwork (@runworkai)Photo by Runwork (@runworkai)Photo by Runwork (@runworkai)Photo by Runwork (@runworkai)Photo by Runwork (@runworkai)Photo by Runwork (@runworkai)Photo by Runwork (@runworkai)
Runwork retweeted
I will host a demo table for @runworkai at the closing party in #TechCrunchDisrupt2026. Come visit me today, Thursday Oct 15, at 6pm! You can also catch me doing a pitch on the stage later on 🗣️
1
3
11
169
Runwork retweeted
#SFTechWeek starts Monday and the calendar has 1,599 events on it. And then October keeps going: Disrupt, Cloudflare Connect, One Way Summit, and about 1,100 more on Luma. SF Tech Week and October Calendar for B2B AI: We went through all of them and kept 76 that are worth it if you're building B2B AI software. Rooms with investors, rooms with operators (COOs, chiefs of staff, ops leads running AI in their teams) and GTM leaders. You can see who's in the room and how to get in. Many are approval-only, so there's an "apply first" list at the top. Hosts approve in order! I'll be at a lot of these. If you see me, say hi or text me to meet! See the B2B AI calendar here: runwork.ai/sf-october-2026/
3
4
6
321
Runwork retweeted
My first video for @runworkai! Took me 24 hours, but I think my discourse has settled down better. Runwork is your team cloud behind your ChatGPT, Claude, Cursor, 60 other agents and whatever comes next. It's vendor-agnostic against models, harnesses, chat tools and compounds your skills, automations, vibe-apps, integrations. If you're still locking yourself to a specific lab or tool, sorry but that's very anti-AI-native in this market. Would you like to really miss the Opus 5 release from yesterday? I don't think so. What about open-weight models or open source Cowork tools? Let your team loose, give them a shared team cloud and see them flourish. If you're tad bit technical, then Runwork is "your team's AI capability layer". Centralizes all team configurations, gives you capability monitoring (not just token monitoring) so you can actually see who's producing what in their daily AI work. With Runwork's vendor-agnostic capability layer, you get to carry your AI work life into the future, everywhere your company goes. Take a look, start a trial, get in a call with me. Watching all kinds of teams (even medical companies!) instantly becoming more AI-native with Runwork is such a satisfaction for me.
3
4
222
Runwork retweeted
I love this latest update. I think the whole thing is becoming more and more clear. It's a 9-post thread with screenshots, take a look and let me know of any feedback! 😎 Next: really really simplify two things: - the team manager setting up their team and monitoring/maintenance - the teammate experience end to end the journeys already work and are used, but we're going to make sure a teammate who has no idea about AI can feel more comfortable today and get their hands dirty next week.
okay okay, we reorganized the dashboard. your agents, workflows, schedules, data, files, webhooks, now much easier to find and manage. quick tour of every new infrastructure page 👇
1
2
789
Runwork retweeted
designing a CLI for agents is interesting indeed. i am bringing interesting agent guidance to @runworkai's CLI. every response by CLI is an opportunity to teach the agent about Runwork and how to make things there and most importantly next steps for the command that was just run.
1
1
1
142
Runwork retweeted
I’m so excited about this, @runworkai desktop client is coming because of this question! Along with of course CLI, automatic MCPs for everything you make, API etc…
does your team do anything around sharing /skills either on a project level or a company level? if so, how do you do the sharing (git repo, dropbox, etc etc)?
1
2
168
Runwork retweeted
Replying to @Shpigford
We’re brining @runworkai a desktop client (alongside CLI, MCP, API etc) so everyone from all technical levels in a team can now sync their AI ecosystem from skills to vibe-apps/automations/MCP servers etc…
2
97
Runwork retweeted
This is not so easy, upgrading your existing teammates to be kinda AI-native… two barriers: some have no enthusiasm to improve their work life, and others lack a consistent experience between novice/curious/technical people. That’s we’re bringing an onboarding DESKTOP app for @runworkai. With our CLI, MCP, Web and Desktop apps, this completes the ability discrepancies.
A CEO from one of our portfolio companies shared this with their team. I’m re-sharing it with their permission, because it resonated and reflects what all founders and CEOs should be communicating. -- We are living through a period of compounding change. And in moments like this, the biggest risk is no longer making the wrong decision. It is moving too slowly while the world moves around you. There are two paths. We can play defense: - Protect what we have - Optimize what works - Wait for clarity It feels safe. It isn’t. Or we can play offense: - Learn faster than the environment changes - Use new tools to solve old problems in better ways - And create entirely new strategies and businesses That’s where the opportunity is. Challenge yourself to do things faster and better than you have ever attempted. Stay uncomfortable. Stay on the front foot.
2
3
139
Runwork retweeted
i love this especially: @runworkai agent wants to solve things in isolated ways so you can re-use your apps, re-purpose them among each other
Replying to @oytuntez @runworkai
honestly runwork came up with the two-app approach on its own, I just described what I needed 😄
1
2
4
178
Wow - this is definitely a game changer!
finally i can show what i've been working on! 🚀 introducing: ◼️Runwork: AI work infrastructure for humans and agents. access via web, CLI, MCP, API or code agents. anyone on your team can create apps, agents, workflows, schedules, APIs, MCP servers, skills... with 3,000+ integrations. talk to your data and apps with your teammates. get started from your terminal or the web dashboard.
1
2
6
77
Runwork retweeted
marketing wanted real-time DTP demand ~20min later, live dashboard is up and running 👇 @runworkai
finally i can show what i've been working on! 🚀 introducing: ◼️Runwork: AI work infrastructure for humans and agents. access via web, CLI, MCP, API or code agents. anyone on your team can create apps, agents, workflows, schedules, APIs, MCP servers, skills... with 3,000+ integrations. talk to your data and apps with your teammates. get started from your terminal or the web dashboard.
1
2
3
106
Runwork retweeted
follow @runworkai ! we'll be sharing deep dives into every feature today, we're excited to show all of it.
3
15
167
Runwork retweeted
both paths lead to the same workspace. your team gets chat channels to communicate among apps/AI/humans/agents, 3,200+ integrations, AI agents, schedules, workflows, apps... full handover between web and terminal.
1
3
13
176
Runwork retweeted
from your terminal, power users get local dev with Claude Code/Cowork, Cursor, or Codex. Managed infra comes with your own MCP servers, SKILL.md, AGENTS.md specific to each app.
1
3
15
194
Runwork retweeted
on the web, anyone on your team can talk to AI and get what they need. apps, dashboards, trackers, automations. no code. just a conversation.
2
4
16
162
Runwork retweeted
Replying to @MBoyrazX
your "OCR designer" app was craaaazy :D i can't believe you tried to make a Figma of your own.
2
1
3
61
Replying to @oytuntez
This is how AI work should feel, can’t wait to try this!
2
2
4
87
Runwork retweeted
Replying to @salihaksu
thank you Sali!!! i was so shocked when i first tested the "automatic MCP" for your vibe-apps, it enabled so much for me personally.
1
5
88
Replying to @oytuntez
Huge congrats on the launch, Oytun! 🔥 The fact that it supports MCP and 3,000+ integrations right out of the gate is massive. The seamless jump between the CLI and web is exactly what the ecosystem needs right now.
1
2
5
104