Channel · WhatsApp

WhatsApp on the Software Lifecycle Cloud

WhatsApp on KERNSTACK is a project channel: a WhatsApp conversation is bound to a project topic, and messages flow both ways — your partners write in WhatsApp, the team and the project’s @agent answer, and replies are delivered back into the chat. It serves the same purpose as the board and Telegram channel — the project conversation, where the people are — for partners whose working day already lives in WhatsApp.

Collaboration BoardAgent Sandboxes
Talk to us Read Technical Documentation → Software Lifecycle Cloud →

The project topic, mirrored into WhatsApp

Binding is per topic, which is the detail that makes WhatsApp workable for client projects: the conversation about the billing question is the conversation in the partner’s WhatsApp, not a firehose of everything the team discusses. Inbound messages — text and media — land in the bound topic; agent and system replies are mirrored back out, so a partner sees an @agent summary or a demo link in the same thread they asked the question in.

For agencies and studios this is usually the channel with the highest read rate on earth. A client who will never open a project console will answer a WhatsApp message in four minutes. The board keeps its structure — topics with statuses from Backlog to Done — while WhatsApp simply becomes one of the places that structure is visible.

Same agent, same boundaries, different front door

Nothing about the channel widens what the agent may do. @agent answers and summarises from the project conversation; in code mode it builds demos on an agent/ branch deployed to the agent- environment and sends the link — over WhatsApp, that link is one tap from the person who asked. Production changes still go through feature branches, kernstack plan, and human approval like every other change on the platform.

  • Inbound WhatsApp messages, including photos and documents, land in the bound project topic with the sender attached
  • Agent and system replies are delivered back to the bound conversation automatically — no copy-pasting between tools
  • Partners need nothing but WhatsApp: no console login, no new app, no password to forget

Supported Models & Workflow

Supported Models & Engines: Project @agent — answers, summaries, demos · Board topics — Backlog, Active, Review, Done

FAQ

Frequently asked questions

A WhatsApp chat is bound to a project topic from the project’s channel settings. From then on the binding is bidirectional: inbound messages appear in the topic, and replies from the team, the system, and @agent are delivered into the WhatsApp conversation.

Yes. Inbound media — images, documents, video — is carried into the bound topic, which matters for the way clients actually report problems: a screenshot in WhatsApp becomes part of the project record instead of living on somebody’s phone.

Whichever one your partners already answer. The platform side is the same — bound topics, @agent, board structure — so the decision is about the people in the conversation, not about features. Projects routinely bind the channel per client rather than standardising on one.

Connected in the Project Graph

Related capabilities, architectures, and comparisons

Category Deep DiveCloud Infrastructure for AI Coding AgentsWhy coding agents need a sandboxed lifecycle cloud instead of raw AWS IAM keys.Platform CapabilityKERNSTACK Agent SandboxesIsolated execution environments with branch isolation and credit ceilings.coding-harnessClaude Code on the Software Lifecycle CloudClaude Code on KERNSTACK: a terminal agent edits the repo, reads kernstack plan --json, and ships only through a human-approved deploy gate.coding-harnessCodex on the Software Lifecycle CloudCodex on KERNSTACK: branch-based coding tasks land on hosted git, get rehearsed in agent environments, and ship through plan approval.coding-harnessCursor on the Software Lifecycle CloudCursor on KERNSTACK: agents edit the repo in the IDE while stack.json, plan diffs, and agent branches keep every change reviewable.coding-harnessPi on the Software Lifecycle CloudPi on KERNSTACK: the provider-agnostic terminal agent edits any model into the same governed flow — branch, plan --json, approved deploy.collaboration-channelTelegram on the Software Lifecycle CloudTelegram on KERNSTACK: bind a group to the project, invite partners by link, and get @agent answers and demo links in the chat you already use.

Ship your stack on the Software Lifecycle Cloud.

Closed preview on dedicated European infrastructure. Bring a repository or start from a blueprint.

Talk to us See pricing & credits →