The project conversation, in the chat your partners actually open
Every KERNSTACK project has built-in conversations organised as board topics — Backlog, Active, Review, Done. Binding Telegram puts that conversation into a group your partners will actually read, including people who will never hold a console login. A client can follow progress, answer questions, and see decisions in the thread where they happened instead of in a status meeting about the thread.
The @agent mention is the active ingredient. Ask for a summary and you get one in the chat. Enable code mode — which needs hosted git — and @agent builds a demo on a dedicated agent/
Built for outside eyes, bounded by design
Channels exist because real projects include people outside the engineering team: clients, partners, stakeholders. The binding is per project, so a group sees its own project’s conversation — not your other clients, not your internal monologue in other topics. What the agent may do is bounded the same way it is everywhere on the platform: demos live on agent branches and agent environments, and keeping the work is a deliberate step onto a feature branch.
- Bind under Settings → Channels; invite partners to the group by link — no console accounts needed for them
- Board topics give the chat structure: a question lands in a topic with a status, not in an endless scroll
- @agent in code mode replies with a live demo URL from the agent-
environment; your main branch is never touched
Supported Models & Workflow
Supported Models & Engines: Project @agent — answers, summaries, demos · Board topics — Backlog, Active, Review, Done
Frequently asked questions
Open Settings → Channels in the project, bind a Telegram group, and share the invite link with the partners who belong in it. The group then carries the project conversation — messages, board topics, and @agent — for everyone in it.
Answer questions about the project, summarise conversation and board state, and — with Agents enabled in Settings and hosted git available — build demo changes. Demos are built on an agent/<id> branch and deployed to the matching agent-<id> environment; the reply contains the live link.
No. The agent’s code mode is sandboxed by construction: its own branch, its own environment, main untouched. Turning a demo into real work is a separate, human step — moving it onto a feature branch and putting it through plan review like any other change.
Related capabilities, architectures, and comparisons
Ship your stack on the Software Lifecycle Cloud.
Closed preview on dedicated European infrastructure. Bring a repository or start from a blueprint.