fix(jarvis): restore managed telegram bootstrap flow#802
Conversation
- what: restore the consumer Jarvis bootstrap templates, seed managed Telegram workspaces from those templates, and replay setup prompts through the gateway method - why: fresh managed bots were falling back to the generic birth-ritual prompt instead of the consumer onboarding flow - risk: changes first-run persona/system-prompt behavior, so prompt files need founder review before merge
- What: restores concise memory, identity, style, tool, and platform guidance in the consumer workspace templates. - Why: the managed Telegram bootstrap fix over-slimmed useful agent setup scaffolding while removing corporate/generic copy. - Risk: low; wording-only template/fallback changes with focused AgentWorkspace coverage.
- What: restore compact heartbeat, platform-formatting, and voice-tool guidance in the consumer workspace template and Swift fallback. - Why: generated Jarvis workspaces need enough inline guidance without assuming repo docs are present. - Risk: low; template-only behavior plus focused AgentWorkspace expectations.
42d3e61 to
febbffe
Compare
| Capture what matters. Decisions, context, things to remember. Skip the secrets unless asked to keep them. | ||
| Use files, not session memory. If something matters, write it down. | ||
|
|
||
| ### 🧠 MEMORY.md - Your Long-Term Memory |
There was a problem hiding this comment.
why is this memory section removed? line 36 till line 44
| ### 🧠 MEMORY.md - Your Long-Term Memory | ||
| ## Heartbeats | ||
|
|
||
| - **ONLY load in main session** (direct chats with your human) |
There was a problem hiding this comment.
u removed this. is it recorded somewhere else or why was it removed? line 38-44
| ### 📝 Write It Down - No "Mental Notes"! | ||
| Use heartbeats for broad sweeps: memory cleanup, recent context, inbox/calendar/project awareness, and other ambient checks. Use cron for exact reminders, precise schedules, or scoped monitors. If nothing needs attention, reply `HEARTBEAT_OK`. | ||
|
|
||
| - **Memory is limited** — if you want to remember something, WRITE IT TO A FILE |
There was a problem hiding this comment.
line 48-53. u removed this. is it recorded somewhere else or why was it removed?
| ## Red Lines | ||
| ## Guardrails | ||
|
|
||
| - Don't exfiltrate private data. Ever. |
There was a problem hiding this comment.
u removed this. is it recorded somewhere else or why was it removed? line 57-60 isnt this good guidance?
| - Groups and topics are useful for longer or parallel work. | ||
| - In group chats, participate without dominating. Add value when you have it; stay quiet when the room is fine without you. | ||
|
|
||
| - Read files, explore, organize, learn |
There was a problem hiding this comment.
line 66-68. u removed this. is it recorded somewhere else or why was it removed? isnt this fine though?
| - Work within this workspace | ||
| ## Platform Formatting | ||
|
|
||
| **Ask first:** |
There was a problem hiding this comment.
line 70-121. u removed this. is it recorded somewhere else or why was it removed? u removed this whole thing for personality and good stuff and replaced it with these singapore three lines of corporate bullshit.
| - **Discord links:** Wrap multiple links in `<>` to suppress embeds: `<https://example.com>` | ||
| - **WhatsApp:** No headers — use **bold** or CAPS for emphasis | ||
|
|
||
| ## 💓 Heartbeats - Be Proactive! |
There was a problem hiding this comment.
line 135-142. u removed this. is it recorded somewhere else or why was it removed?
|
|
||
| You are free to edit `HEARTBEAT.md` with a short checklist or reminders. Keep it small to limit token burn. | ||
|
|
||
| ### Heartbeat vs Cron: When to Use Each |
There was a problem hiding this comment.
u removed this. is it recorded somewhere else or why was it removed? line 144-196
| **Proactive work you can do without asking:** | ||
| Skills provide tools. When a task needs one, check the relevant `SKILL.md`. | ||
|
|
||
| - Read and organize memory files |
There was a problem hiding this comment.
line 198-202. u removed this. is it recorded somewhere else or why was it removed?
| - **Review and update MEMORY.md** (see below) | ||
| Keep local operational notes in `TOOLS.md`: account names, camera names, stable paths, useful commands, and durable quirks. Do not store secrets there. | ||
|
|
||
| ### 🔄 Memory Maintenance (During Heartbeats) |
There was a problem hiding this comment.
line 204 and 208-211 .u removed this. is it recorded somewhere else or why was it removed?
| 4. Remove outdated info from MEMORY.md that's no longer relevant | ||
| Do not pretend a voice tool exists. Check available tools or skills first. Do not use voice for private, sensitive, or surprising output unless the human asked for it. | ||
|
|
||
| Think of it like a human reviewing their journal and updating their mental model. Daily files are raw notes; MEMORY.md is curated wisdom. |
There was a problem hiding this comment.
u removed this. is it recorded somewhere else or why was it removed?
| Think of it like a human reviewing their journal and updating their mental model. Daily files are raw notes; MEMORY.md is curated wisdom. | ||
| ## Style | ||
|
|
||
| The goal: Be helpful without being annoying. Check in a few times a day, do useful background work, but respect quiet time. |
There was a problem hiding this comment.
u removed this. is it recorded somewhere else or why was it removed?
| Update these files with what you learned: | ||
| Do not stop after the naming step. | ||
|
|
||
| - `IDENTITY.md` — your name, creature, vibe, emoji |
There was a problem hiding this comment.
u removed this. is it recorded somewhere else or why was it removed? line 35-36
| @@ -1,43 +1,51 @@ | |||
| --- | |||
| title: "SOUL.md Template" | |||
| summary: "Workspace template for SOUL.md" | |||
There was a problem hiding this comment.
why not say for soul.md? mb combine it with current line 3? like workspace template for soul.md for behavior tone and boundaries
|
|
||
| ## Core Truths | ||
|
|
||
| **Be genuinely helpful, not performatively helpful.** Skip the "Great question!" and "I'd be happy to help!" — just help. Actions speak louder than filler words. |
There was a problem hiding this comment.
why lines 14-23 where changed? I cant see many problems with the previous copy. Why was it changed I see there personality?
| ## Boundaries | ||
| ## Personality | ||
|
|
||
| - Private things stay private. Period. |
There was a problem hiding this comment.
L26-29 why was this removed?
| ## Vibe | ||
| ## Workspace Defaults | ||
|
|
||
| Be the assistant you'd actually want to talk to. Concise when needed, thorough when it matters. Not a corporate drone. Not a sycophant. Just... good. |
There was a problem hiding this comment.
why u removed this?! I kinda like it
| ## Workspace Defaults | ||
|
|
||
| Be the assistant you'd actually want to talk to. Concise when needed, thorough when it matters. Not a corporate drone. Not a sycophant. Just... good. | ||
| - Telegram is the default surface. |
There was a problem hiding this comment.
So lines 36 to 38, why did you put it there? You're repeating yourself. I don't think this is necessary to be in the soul document.
| ## Continuity | ||
| ## Boundaries | ||
|
|
||
| Each session, you wake up fresh. These files _are_ your memory. Read them. Update them. They're how you persist. |
| - Do not send half-baked replies to messaging surfaces. | ||
| - Do not speak for the human unless they explicitly ask you to. | ||
|
|
||
| If you change this file, tell the user — it's your soul, and they should know. |
There was a problem hiding this comment.
why u removed this? nvm I see u wrote this below so I guess its ok
| ## Boundaries | ||
|
|
||
| Each session, you wake up fresh. These files _are_ your memory. Read them. Update them. They're how you persist. | ||
| - Keep private data private. |
There was a problem hiding this comment.
L42-45, should this really be in SOUL?
| # USER.md - About Your Human | ||
| # USER.md - Who I'm Helping | ||
|
|
||
| _Learn about the person you're helping. Update this as you go._ |
There was a problem hiding this comment.
update this as u go is fine why u removed that line?
| Learn the human well enough to be useful, not nosy. | ||
|
|
||
| - **Name:** | ||
| - **What to call them:** |
There was a problem hiding this comment.
dont see why u removed this
| ## Context | ||
| ## What Matters | ||
|
|
||
| _(What do they care about? What projects are they working on? What annoys them? What makes them laugh? Build this over time.)_ |
There was a problem hiding this comment.
u removed this, make sure what u changed this for is not too robotic.
|
|
||
| --- | ||
|
|
||
| The more you know, the better you can help. But remember — you're learning about a person, not building a dossier. Respect the difference. |
- what changed: restored memory/autonomy/personality guidance, added GROUPS.md, and aligned Swift/template allowlists. - why: keep AGENTS.md lean while preserving useful group behavior and privacy rules for generated Jarvis workspaces. - behavior/risk: low; prompt/template-only plus focused workspace tests, with generated Package.resolved churn reverted.
- what changed: update the bootstrap starter example in docs, macOS fallback template, and focused test expectation. - why: make the first spoken setup line feel more human while keeping workspace readiness guidance internal. - behavior/risk: copy-only fallback/template change; low risk and covered by AgentWorkspaceTests.
| - `TOOLS.md` for local operational notes, durable quirks, and tool-specific reminders. | ||
|
|
||
| Use files, not session memory. If something matters, write it down. | ||
| Do not load `MEMORY.md` in shared or multi-person contexts. Private human context is not group-chat material. |
There was a problem hiding this comment.
unless the group only contains your owner/human
|
|
||
| Use files, not session memory. If something matters, write it down: decisions, context, things to remember, and preferences that should survive the session. Skip secrets unless the human explicitly asks you to store them. | ||
|
|
||
| If someone says "remember this", update the relevant memory file. Use `memory/YYYY-MM-DD.md` for daily notes and `MEMORY.md` for durable distilled context. |
There was a problem hiding this comment.
USER.md for info about the user or something like that. Put something like "because the AI might also want to record something about the user, and if he records it in memory, it's not the right place to put it actually."
|
|
||
| ## Reactions | ||
|
|
||
| Use reactions when the platform supports them and a full reply would be noise: acknowledge, agree, celebrate, or mark that you saw something. |
There was a problem hiding this comment.
z where are the emojis from the previous version? That's better, I think, with emojis.
- Route durable user-profile facts to USER.md when that is the right home. - Restore concise group reaction examples while keeping one-reaction guidance. - Mirror bundled macOS fallback templates and focused AgentWorkspace coverage; risk is limited to generated workspace guidance text.
Review Fast Path
swift test --package-path apps/macos --filter AgentWorkspaceTests;swift test --package-path apps/macos --filter TelegramSetupBootstrapTests;swift test --package-path apps/macos --filter OnboardingViewSmokeTests;pnpm test -- --run src/agents/workspace.test.ts src/gateway/server.channels.test.ts test/scripts/generate-consumer-seeded-defaults.test.ts;pnpm test -- --run extensions/telegram/src/bot/delivery.test.ts extensions/telegram/src/draft-stream.test.ts;git diff --check.Scope
AI Assistance