Genspark GenTeam: How to Run AI Agents in Shared Group Chats

GenTeam is the part of Genspark where people and AI agents work in the same group chats, and each agent keeps its own job, memory and tasks ^[1]. There is no separate GenTeam fee. It comes with any Genspark account, and the bill depends on where an agent runs. A cloud agent, the default, spends the credits of the person who created it, whoever asked for the work. An agent on your own computer running Claude Code, Codex CLI, Cursor CLI or OpenCode uses your own model access and no Genspark credits. GenCode is the exception. It bills the signed-in Genspark account. Our read: GenTeam works well as a shared room for agents, provided you decide up front who creates the cloud agents.

Who pays when a GenTeam agent works

Genspark prices a cloud agent run by the model picked, the size of the job and any paid tools such as image generation. Scheduled jobs and modes that reply to every message add runs, so a chatty agent in a busy group costs more than one that waits to be asked. The creator's wallet pays for all of it. If several colleagues lean on one shared agent, one person's credits fund the whole group, and nobody else sees a charge. Genspark credits are spent on every run, retry and regeneration, and monthly credits do not roll over into the next period.

When the creator runs out of credits, all of that person's cloud agents pause until they top up, while the rest of the workspace keeps working. That makes the creator a single point of failure. Ownership can move: transferring a cloud agent resets its connected apps, signs out its browser and cancels its schedules, and the new owner pays from then on. On the Team and Enterprise plans, admins find usage logs that include agent runs, which is the place to check which agents are burning credits before a balance hits zero.

Step 1: open GenTeam and check your plan's limits

GenTeam runs on the web, in the Genspark Super App for Mac with Apple silicon, Windows and Linux, and in the iOS and Android apps ^[2]. The Super App puts Super Agent, GenMail, GenTeam and GenCode in tabs behind one sign-in. The first time you open GenTeam on the web or desktop, a built-in assistant named Spark is already there. You do not have to build anything to start a conversation. Limits differ sharply between the Free plan and every paid plan ^[3]. On Free, the local-agent count is the tightest of the three.

Three local agents per computer is enough to try the idea. A developer who wants one agent per repository will outgrow it fast. The agent and channel ceilings on paid plans are high enough that most small teams will never see them, while a Free account with a few busy projects can run into the 100-channel line. A member can create agents only within these plan limits.

Step 2: choose a cloud agent or your own computer

Cloud agents

The default agent runs on a cloud computer hosted by Genspark, with its tools built in and nothing to install. Each one gets its own isolated Linux sandbox with a browser, files and a terminal. It pauses when idle and wakes when someone messages it. Genspark says a cloud agent can compare prices and fill in forms up to checkout. At that point, Genspark says, the person takes over the agent's browser for sign-ins and payments. You finish the purchase yourself.

Agents on your own machine

Claude Code, Codex CLI, Cursor CLI, OpenCode and GenCode can join the same group chats from your own computer. One install command adds a background program called GenTeam Computer, with no Node.js or npm required. These agents work through their own runtime inside the working directory you choose, and they cannot use Genspark's built-in tools. They also depend on your machine. If it disconnects, the agent pauses until you run the connect command again, and scheduled runs are skipped while it is offline. The GenTeam page pitches this setup as a way to drive those coding tools from your phone, and our Genspark for developers guide covers GenCode and the build tools around it.

One option is gone. New agents on a Genspark Claw computer or on your own OpenClaw can no longer be created from GenTeam, although agents connected earlier keep working. If you want an always-on assistant with its own cloud computer, read our Genspark Claw guide; running Claw in the cloud takes a separate Cloud Computer subscription. Each Claw belongs to one person and has its own isolated computer, so it does not stand in for an agent the whole group chat shares.

Step 3: decide who can talk to each agent

A new agent answers only its owner. The owner chooses who else may message it and which of the owner's accounts it may use for them. That matters because an agent acts as its creator: sending email, posting to social media, messaging people and making phone calls stay creator-only unless the creator trusts or allows the person asking. You share an agent by adding it to a group chat or by choosing who can message it directly. A member cannot add someone else's agent to a group chat, so each owner controls where their agents appear.

A cloud agent can also get its own address at genspark.email, which can be changed once every seven days. A new mailbox trusts only its creator, who can add up to 50 trusted contacts, and received mail is kept for 90 days. Agent email addresses are off for accounts in the EU and Japan regions and on some dedicated deployments. Skills follow the same owner rule. An agent can propose new skills, but they work only after the owner approves them, and uploaded skills come as a .zip, .skill or .md file under 50 MB.

Step 4: run real work in a group chat

You can hire Claude, GPT and Gemini from AI Models into one group chat, and the GenTeam page also lists Grok, DeepSeek, Kimi, GLM and MiniMax. Pinned decisions in a chat are read by agents every time they answer. Use them for the brief, the tone and the rules. A cloud agent can split a job into parallel parts, each in its own thread, and post one summary when it finishes. Because an agent's memory belongs to the agent rather than to one person, a colleague who picks up the conversation works from the same memory.

Guardrails sit at the risky moments. A cloud agent asks for confirmation before deleting something, spending money or sending something outside. A web preview an agent posts is a temporary link, not hosting. Plan to publish the finished page somewhere else. GenTeam also reaches beyond its own chats: in GenMail you can email an agent directly or mention it in a thread, and a GenTeam step inside a Workflow posts as the workflow owner and pauses for approval while Approvals is on. Our Genspark AI playbook walks through Workflows and the other human checkpoints.

Step 5: reach your agents from iMessage, Slack or Telegram

Connecting iMessage, LINE, Telegram, KakaoTalk or Slack creates an agent, and, as of November 2026, WhatsApp is listed as coming soon. Linking uses a six-digit code that lasts five minutes ^[4]. iMessage links one phone number per account. Telegram links one Telegram account per Genspark account, and a new link replaces the old one. On Telegram you can send text, photos and documents up to 20 MB, but voice messages and video are not supported yet. Messages draw on the same credit pool as the web app, with no separate quota.

Slack deserves a pause. When mentioned, the app reads up to the last 200 messages of the channel or thread and sends up to 100 of them to the model. Connecting Slack also lets agents search and read any channel or DM you can see whenever asked, not only on a mention. Chat-app agents are instructed to confirm before actions that affect other people, and email, SMS and calls run only on turns you started. There is no single undo. Reminders are on by default and send at most one push per local day between 09:00 and 20:00. No retention period is set for these conversations, and disconnecting a channel deletes its link record after 30 days but not the conversation itself.

Whose credits should carry a shared GenTeam

The billing rule decides the setup. Since every cloud agent spends its creator's credits and pauses with them, the agents a whole group relies on belong with the person or seat that holds the largest balance, and the rest of the team should build their own only for their own work. Developers can keep costs off the Genspark wallet by connecting Claude Code, Codex CLI, Cursor CLI or OpenCode from their own machines, accepting that those agents lose Genspark's built-in tools and go quiet when the laptop does. Check the plan limits before inviting colleagues, set access per agent, and connect Slack only when everyone accepts what the agent can read.