---
name: ultron-app-claude-integration
description: "Ahmed wants to build a custom \"Ultron\" app with the same chat-integration pattern as the Telegram plugin — Channels vs Agent SDK options"
metadata: 
  node_type: memory
  type: project
  originSessionId: e76b8acc-b39e-441c-ad82-68c4ed982296
---

On 2026-07-04 Ahmed asked whether the Telegram↔Claude-Code integration logic could be copied to
a custom app he wants to build, branded "Ultron". Researched via claude-code-guide agent:

- **Channels** (Claude Code feature, v2.1.80+, research preview): build an MCP server declaring
  `claude/channel`, push messages into a running Claude Code session, optional `reply` tool back —
  literally the same mechanism the Telegram plugin uses. Docs: code.claude.com/docs/en/channels.md
  and channels-reference.md. Downside: only works while that Claude Code session is open, tied to
  this session.
- **Claude Agent SDK**: build Ultron as a fully standalone app/product with its own embedded agent,
  own infra, full UX control, independent of any running Claude Code session. More upfront work but
  the right call if Ultron is meant to be a real product (ties to [[personal-device-control-nodes]]
  and his broader agentic-app ambitions in [[ahmed-agentic-vision]]).

**Why:** He's simultaneously talking about productizing/selling Ultron — a real customer-facing app
would want the Agent SDK route, not a reskinned chat bridge to this one VPS session.

**How to apply:** Asked him to clarify which he actually wants (quick rebrand of this chat vs a real
standalone product) — answer pending as of this memory. Don't assume Channels is sufficient if he
says "product."