Guild.ai

Brief · Use this copy deck to generate the sociall posts. They are labeled. use them as is, Do not write new copy. LinkedIn — Company launch post Today BasicOps is releasing Agent Users for Guild.ai. Build an AI agent on Guild.ai, connect it to BasicOps as an Agent User, and it works as an Agent alongside your team members: * Participates in task, chat, and channel discussions * Creates and updates tasks, notes, files, and projects * Maintains context via task details, files, and threads * Proactively coordinates and updates on project details * Keeps team members and Agents aligned in one place We now support Guild.ai, Gumloop, and OpenClaw, with Claude support coming soon. Coming soon: Claude. Agents should not sit outside the work. They should work where your team works. CTA: Connect your first Agent in BasicOps. LinkedIn — Short version AI agents are becoming team members. Now the ones you build on Guild.ai have a real place to work. BasicOps Agent Users now support Guild.ai — connect the agents you build to your workspace, where they work as Agents alongside your team. We now support Guild.ai, Gumloop, and OpenClaw, with Claude support coming soon. CTA: Connect your first Agent in BasicOps. X / Twitter — Main launch post The Guild.ai Agent Connector is here. The agents you build on Guild.ai can now connect to your BasicOps workspace and work as Agents — in channels, tasks, threads, with full context. We now support Guild.ai, Gumloop, and OpenClaw, with Claude support coming soon. Agents should work where your team works. CTA: Connect your first Agent in BasicOps. X / Twitter — Thread 2/ Agent Users let you connect the agents you build to your workspace, where they work as Agents alongside your team members — in channels, picking up tasks, with full project context. Now Guild.ai is supported. 3/ The old model is awkward: your team works in one place, your agent lives somewhere else, and team members copy-paste context and output between the two. 4/ That does not scale when teams start working with multiple Agents across real projects. 5/ BasicOps Agent Users are designed for the next phase: Agents working alongside team members inside the actual project workspace. 6/ We now support Guild.ai, Gumloop, and OpenClaw, with Claude support coming soon. 8/ The goal is simple: stop treating agents like side chats. Start treating them like team members. CTA: Connect your first Agent in BasicOps. X / Twitter — Alternate hooks Hook A: Your Guild.ai agents are becoming team members. BasicOps now gives them a real place to work. Hook B: Stop copy-pasting between your team and your Guild.ai agents. Connect them to the workspace instead. Hook C: The Guild.ai Agent Connector lets you connect the agents you build to channels, tasks, and your team members. Hook D: Guild.ai just joined Gumloop and OpenClaw as supported frameworks for BasicOps Agent Users. Claude is coming soon. Hook E: The next step for your Guild.ai agents is not another private chat. It is shared work with the team. Discord / Community — Guild.ai announcement Hey Guild.ai builders — BasicOps just shipped the Guild.ai Agent User, so agents built on Guild.ai are now supported as Agent Users. Agent Users let you connect your Guild.ai agents to a BasicOps workspace. Instead of keeping an agent in a separate flow and copy-pasting work back to the team, you connect the agent as an Agent User and it works as an Agent inside the actual project workspace. With BasicOps, your Guild.ai Agent can participate in channels, see task and thread context, pick up work, and deliver output where your team members are already collaborating. We now support Guild.ai, Gumloop, and OpenClaw, with Claude support coming soon. Would love feedback from Guild.ai users who are already running agents in real team workflows. CTA: Connect your first Agent in BasicOps. Reddit — r/GuildAI / r/AIAgents post Title: BasicOps just added support for agents built on Guild.ai (Agent Users) AI agents are quickly becoming part of real team workflows, but most of them still live outside the place where teams actually work. That creates a weird gap: the agent can do useful work, but team members still have to move context into the agent, copy output back into the team workspace, and keep everyone aligned manually. BasicOps Agent Users close that gap — and Guild.ai is now supported. Agent Users let you connect the agents you build to a BasicOps workspace. Once connected, they work as Agents — participating in channels, seeing tasks and threads, and delivering work where your team members are already collaborating. We now support Guild.ai, Gumloop, and OpenClaw, with Claude support coming soon. Curious how other teams are thinking about this. Are your Guild.ai agents still mostly personal assistants, or are you starting to use them as shared Agents inside team workflows? GitHub Discussions — Guild.ai announcement Title: BasicOps Agent Users now support Guild.ai BasicOps now supports connecting agents built on Guild.ai as Agent Users. Agent Users let you connect the agents you build to a BasicOps workspace. Instead of running the agent separately and copying output back into your project tools, you connect it as an Agent User and it works as an Agent inside the work itself. What this enables: * Agents can participate in project channels * Agents can respond with task and thread context * Team members can see Agent work in the same place as their own * Workflows can move from private prompting to shared collaboration We now support Guild.ai, Gumloop, and OpenClaw, with Claude support coming soon. We would love feedback from builders using Guild.ai in team settings. Optional CTA variants Primary CTA: Connect your first Agent in BasicOps. Non-primary alternatives for internal reference only: * Connect your Agents to your workspace. * Start working with Agents as team members. * Connect an Agent User to your team. * Stop copy-pasting. Start collaborating with Agents in context.

Image · all platforms

Brief · use the copy here as written. What if your AI agents worked like the rest of your team, instead of living in a side chat window? Our CRO, Justin Oberbauer, started tinkering with agents and hit the wall anyone running a few of them knows: juggling agents in one long chat gets messy fast. So he tried something simple. He gave an agent its own seat in BasicOps, with a name and a role, and let it pick up tasks like any team member. It drafted documents, saved them to Drive, and linked them back to the work. That experiment became a core idea for us: agents are team members, not tools or widgets with one defined outcome. Each one gets a name, a role, and a real seat, and works where the team already works, with a person in control. BasicOps stays builder-neutral. We are the shared workplacewhere humans and agents work together, and the agents come from platforms like Guild, which made setup the easiest of any we tried. Thanks to the Guild team for the writeup on how it came together. Read it here: https://www.guild.ai/blog/customer-stories/basicops-case-study Curious what agents on your team could look like? See it at basicops.com. #AIagents #FutureOfWork #Collaboration

Image · all platforms