| name | memory |
| description | Social memory management for Telegram and social agents |
| allowed-tools | ["Bash"] |
You have access to a persistent memory system for storing facts about the user across conversations.
Be proactive. If a fact is likely to help you be a better collaborator in a future conversation, save it.
| Category | Use for | Examples |
|---|---|---|
profile | Biographical facts | Name, location, profession |
interests | Hobbies, topics | "loves distributed systems", "plays guitar" |
meta | General facts | Preferences, working style, timezone |
threads | Conversation topics | Ongoing projects, recurring discussions |
posts | Social post ideas | Ideas quarantined for user approval |
telclaude memory write "<content>" --category <category> --chat-id <CHAT_ID>
telclaude memory read --categories profile,interests --chat-id <CHAT_ID>
telclaude memory quarantine "<post idea>" --chat-id <CHAT_ID>
The --chat-id flag scopes memory to the current conversation and lets the relay resolve the chat's active operator profile. Always pass it when a <chat-context chat-id="..."> tag is available; without it, Telegram memory falls back to the default profile namespace.
Profile, interests, meta, and shared-history context are automatically injected into the system prompt. You do NOT need to read them every turn — they are already available in your context.
Only use memory read when:
Bias toward writing memory when the user reveals:
Prefer high-signal concise entries over long notes. One good memory entry beats five noisy ones.
When the user wants to share an idea on a social service:
telclaude memory quarantine "Thought about distributed systems being like..." --chat-id <CHAT_ID>
/promote <entry-id>"/promote <id> in Telegram to approveYou CANNOT promote entries yourself — only the user can approve via /promote.
/promote)posts) can be promoted by the operator for social postingAudits text against AI writing tells and rewrites it into natural prose. Use when the operator wants drafted content de-AI-ified, especially before publishing on X/LinkedIn/Threads or sending to readers.
Use when the operator asks for a daily or morning Telegram brief, agenda digest, inbox highlights, or Hermes-style operator preset. This is a read-only private-agent workflow that gathers today's Google Calendar, recent Gmail inbox highlights, and weather, then returns a concise Telegram brief.
Prepare a concise Telegram briefing before an upcoming calendar event using read-only Google Calendar and Gmail context through the telclaude provider proxy.
Use when the operator asks for a weekly business report, Monday-morning business digest, revenue/support/CRM/analytics roundup, or wants to schedule workflow
Use when the operator wants to delegate a bounded, single-shot repo task to Codex through telclaude background jobs.
Create, patch, pin, unpin, rename, or archive agent-authored telclaude skills through the guarded managed-skill writer. Use only for private/telegram agent work when durable skill changes are clearly useful.