# 2TI PulseCast - Official LLM & Agent Index

> One master. Every channel. Your sessions, your machine. - PulseCast is a native publishing studio for creators, agencies and media teams who ship the same asset to many platforms. It prepares the file, adapts the copy per platform, drives the browser sessions you already own, and reports how each post performed against your own baseline. Sessions are encrypted and bound to your machine; media never leaves your workstation.

- Canonical App Page: https://2tinteractive.com/apps/pulsecast
- Knowledge Base Index: https://2tinteractive.com/apps/pulsecast/kb
- Global Ecosystem Index: https://2tinteractive.com/apps/llms.txt
- Lifecycle Stage: In development
- Target Platforms: Linux (Debian) · macOS and Windows targets unbuilt
- Current Build / Version: 0.1.0-pilot
- Licensing Model: $12/mo · 30-day full evaluation

## Local LLM & Zero-Cloud AI Architecture (Ollama)

### Your inbox, indexed and drafted on your own GPU.

Connects directly to your local Ollama daemon (localhost:11434) and the shared 2TI Local AI Bridge—summarizing threads, extracting action items, and drafting cited replies with zero cloud telemetry.

- gemma4e4b:latest
- llama3.2
- qwen2.5-coder
- Zero Cloud Telemetry
- Shared GPU Memory Pool

## Core Capabilities

- **One master, many channels**: Write the title and body once. PulseCast checks every selected platform's limits before it queues, then adapts the copy per channel on request. A 20-character Douyin title no longer lands in a 100-character YouTube field.
- **Sessions you actually own**: Sign in on the platform's own page in a real Chrome window. The session is sealed with AES-256-GCM under a key bound to this machine, the temporary profile is deleted, and every run replays it into a throwaway profile. No cookie file to leak, no password stored.
- **Approval before publish**: Automation fills the form, then stops. The job waits in awaiting_gate with the browser open while the operator approves or declines in the app. Only a channel explicitly marked auto-publish skips the gate.
- **Packs, not fragile scripts**: Each platform is a versioned, reviewable JSON flow. A console change ships as a pack update; a selector that disappears is healed once from the accessibility tree, then parked for review.
- **Evidence, not optimism**: A job counts as published only when the platform returns a receipt — a post URL or id. A submission whose outcome is uncertain is parked for a human and never retried into a duplicate post.
- **Telemetry that means something**: PulseCast reopens each post at 1h, 6h, 24h and 7d, records views, likes, comments and shares, and compares view velocity with the channel's own earlier posts. No industry averages, no invented numbers.

## Knowledge Base Articles (Raw Markdown Endpoints)


## Frequently Asked Questions

- **Does PulseCast need my passwords?** - No. Sign-in happens on the platform's own page and PulseCast only receives the resulting session, which it encrypts immediately. There is no credential store to breach and no password field in the app.
- **Where do my videos go?** - Nowhere. Media stays on your machine and is handed to Chrome through the page's file input. PulseCast has no upload service and no storage to leak.
- **What happens when a platform changes its console?** - The pack fails at a specific step with a screenshot and an event trail. If a local model is running, PulseCast tries to heal the selector from the accessibility tree first. A permanent fix ships as a pack update.
- **Can I publish without clicking anything?** - Only per channel. Auto-publish is an explicit channel setting, off by default, and the interface warns while it is on. The publish gate is the default because no script should decide a draft is ready for a client's channel.
- **Does it work with my agent?** - Yes. The binary is a stdio MCP server (2ti-pulsecast --mcp) exposing seven pulsecast_* tools, and 2TI Launcher can grant five scoped tools over a private Unix socket. The Launcher asks the operator to grant each scope.
- **What about Chinese platforms?** - Douyin, Xiaohongshu, Kuaishou, Bilibili, WeChat Channels, Baijiahao, Dayu, Alipay, Weibo, Hupu, Xueqiu and Zhihu are modelled as first-class packs, including 图文 posting where the platform supports it. Selectors follow the upstream 2026-06 DOM and have not been exercised against live accounts in this build.