A
AIOS Wiki
read-only · public mirror
Open AIOS
Wikitobyxtoby/x/content-pipeline.md

Toby on X — Content Pipeline

Hand-authored·11 min read·16 sections·Last edited May 12 by initial import·View history
TL;DR

_Last updated: 2026-05-10 · auto-regenerated by `toby-x-strategist`. Drafts only — nothing here is published. The agent does not post; the operator does._

How to read this

13 proposed posts, ordered by priority. Mix is ~55% evergreen / 45% reactive. Each post is tagged with the content pillar it serves (see toby/x/strategy.md):

  • P1 = Tab anxiety, named (sub-frame this run: tab-loss grief)
  • P2 = The save-session ritual
  • P3 = Power-user shortcuts & collections (🔒 rel-gated until blank-page hotfix ships)
  • P4 = Better-than-bookmarks
  • P5 = Public collection of the week

Hold-until-clear gates (operator must clear before publishing):

  • 🔒 acct — verify Axiom Zen controls @TobyForTabs creds before any post.
  • 🔒 rel — wait until the new-tab blank-page hotfix ships before posting feature/screenshot content (rationale: posting into a sea of 1-star CWS reviews accelerates the bleed). Tracks toby/strategy/playbook.md O1 KR1, due 2026-05-24.
  • 🔒 price — no post containing a price until $4.50 vs $6/$10 reconciliation is closed (see toby/00-state-of-the-project.md, toby/strategy/playbook.md O3 KR1, due 2026-05-13).

Char counts include the link previewed at length 23 (the way X tokens it). All drafts are tested at ≤ 280 chars.

Post 1 — P1, evergreen, no gate

  • Draft (211 chars):

    47 tabs is not a personality flaw. It's a research pattern.

    You opened them on purpose. You'll close them on purpose. The browser is just bad at holding the in-between.

    That's the part we built Toby for.

  • Why: Names the feeling, pushes back gently on the self-shaming script, frames the product as the bridge — not the cure. Validates the @keegan_doesbite / @Galaxy42_ shape of person without quoting them.

  • Suggested timing: Tue 2026-05-12, 15:00 UTC (Toby Tuesday post #1 of the relaunch).

  • Variants:

    • "67 tabs is not a personality flaw. It's a research pattern…"
    • Replace "research pattern" with "context I'm not done with yet" for a less-corporate version.

  • Source: brand-soul anchor (product/strategy/soul.md); structured against the @humba1icious "professional tab hoarder" framing (tweet 2045396913185595760, 2026-04-18).

Post 2 — P1 sub-frame: tab-loss grief, evergreen, no gate (NEW this run)

  • Draft (242 chars):

    The worst feeling in a browser isn't 80 open tabs.

    It's the moment after the crash, when you realize the 80 are gone — and so is the half-finished thought attached to each one.

    Saving a window shouldn't be a chore. It should be an insurance policy you forget you have.

  • Why: Names the tab-loss grief — the specific pain @wayne_effect (2050774386022465549), @LeFauxLucifer (2053629402437820581), @AngledLuminary (2052412672159916349), @decomposed_dino (2022232335236858085) all articulated this fortnight. Counter-positions against new entrants whose reliability is unproven, without naming any of them. Lives the brand promise "It's okay, Toby has it now."

  • Suggested timing: Wed 2026-05-13, 15:00 UTC. Pair as a thematic 2-post week with Post 1.

  • Variants: Drop the third paragraph and let the second sentence land as the closer.

  • Source: tab-loss grief signal cluster; compass axiom 3 (Persistence-is-Activation) per toby/strategy/compass.md.

Post 3 — P4, evergreen, no gate

  • Draft (235 chars):

    Browser bookmarks are a folder you never open. Toby is the wall behind your desk: you can see everything you put there.

    Same data. Different relationship to it.

    That's the bet. Visual > hidden. Always.

    gettoby.com

  • Why: Lives the existing "Better Than Bookmarks" tagline (in @TobyForTabs's own bio) instead of just stating it. Frames the category fight where it actually lives — against bookmarks, not against Arc or the new entrants.

  • Suggested timing: Thu 2026-05-14, 15:00 UTC.

  • Source: existing brand position in @TobyForTabs bio (profile lookup, 2026-05-10); brand soul axiom 1 "Visual Tangibility" (toby/strategy/compass.md).

Post 4 — P1, reactive, no gate (use within 7 days)

  • Draft (245 chars) — reply to or quote of @nibzard's prompt (tweet 2050495728452034863, 2026-05-02, "are you a tab hoarder, how are you dealing with this?"):

    Honest answer: not closing them is the right instinct. They're context, not clutter.

    The fix isn't fewer tabs. It's somewhere safe to set them down so the browser stops pretending they need to live as windows.

  • Why: Direct, useful, on-brand reply to a 1.1k-follower micro-influencer who invited a response. Doesn't lead with the link. If @nibzard asks "where do you set them down", drop gettoby.com in the second touch. Note: thread is now 8 days old; usable until ~2026-05-12, after which we drop this post and replace with a fresher reactive hook.

  • Suggested timing: ASAP — within 48h of relaunch.

  • Variants: Strip the second sentence and just send the first if the conversation is moving fast.

  • Source: @nibzard's tweet 2050495728452034863.

Post 5 — P2, evergreen, no gate

  • Draft (193 chars):

    Closing a window full of tabs and feeling the small grief of losing 30 things you weren't done with —

    That's the moment Toby exists for.

    Save the whole window as a collection. Open tomorrow. It's all still there.

  • Why: Articulates the activation moment per the v3 research dossier ("the activation moment is persistence — 'I opened a new tab and my organized world was still there'") (see toby/00-state-of-the-project.md, toby/strategy/compass.md axiom 3).

  • Suggested timing: Tue 2026-05-19, 15:00 UTC.

  • Source: docs/ai-onboarding-ideas-analysis.md activation insight; @decomposed_dino's lost-tabs grief tweet 2022232335236858085.

Post 6 — P5, evergreen, no gate (requires permission)

  • Draft (176 chars):

    Public collection of the week 🪟

    [Curator handle]'s [N]-link [topic] reading list, all in one Toby tab.

    One link, one window's worth of context. The internet's bookmarklet, basically.

    [share-link]

  • Why: Activates the Free-Tier Archivist segment (1,848 users, avg 224 lists, 18.6% public-share rate per toby/01-personas.md) and proves the social-share use case. This pillar is the playbook's under-pulled growth lever per toby/strategy/playbook.md O3 KR3 — 4 features needed by 2026-06-30. Start the cadence this run.

  • Suggested timing: First Friday after relaunch — Fri 2026-05-22 — and weekly after that.

  • Variants: If permission is hard to get, run as a Toby-team-curated collection ("Toby's reading list this week") instead.

  • Source: requires the operator to pull a top-public-list from prod (shareable_links table per toby/01-personas.md) and DM the curator for permission. Do NOT post a public collection without explicit OK.

Post 7 — P1 + P2 hybrid, evergreen, no gate

  • Draft (224 chars):

    The tab you've kept open for 11 days is doing a job.

    It's saying: "I'm not done thinking about this."

    The job of a tab manager isn't to make you close it. It's to make sure that thought survives a browser crash.

  • Why: Reframes the "you have too many tabs, fix yourself" cultural script. Useful to both heavy-organisers and switchers. Doubles as a soft reliability-affirmation post.

  • Suggested timing: Wed 2026-05-20, 15:00 UTC.

  • Source: brand voice; reading of @oceansnavi's tweet 1988229387276480809 ("100+ tab groups left… no aggregate tab saving") for the pain shape.

Post 8 — P3, screenshots required, 🔒 rel-gated

  • Draft (188 chars):

    A small thing that costs nothing:

    Right-click any link → Save to Toby → pick the collection. Two seconds. No "open this thing later" tab to close.

    [30s loom]

  • Why: Power-user moment. Useful, screenshot-able, demonstrates a feature. DO NOT POST until the new-tab blank-page reliability hotfix lands (toby/strategy/playbook.md O1 KR1, due 2026-05-24), or we're recommending a workflow into a product that's actively breaking.

  • Suggested timing: Hold. Schedule for the Tuesday after the hotfix ships (earliest plausible: 2026-05-26).

  • Source: extension feature exists in production today (right-click → save flow). Verify in apps/extension/ before posting.

Post 9 — P5 quote-tweet, reactive, no gate

  • Draft (139 chars) — quote-tweet template, deploy when next "be honest, how many tabs" post lands from a major account (Chrome, etc.):

    And every single one of them is doing a job.

  • Why: Cultural moment. Chrome's 2024-05-29 "Be honest" tweet got 1.17M views and 5,911 replies (quoted by SigmaOS, tweet 1795862656546435263). We don't post a fresh meme; we wait for the next one and quote it cleanly.

  • Suggested timing: Reactive. Standby — operator should set a saved search for "googlechrome" + "tabs".

  • Source: existing pattern from @googlechrome and @SigmaOS.

Post 10 — P1, evergreen, no gate, AuDHD-shaped

  • Draft (232 chars):

    Two systems running at once:

    1. The brain that won't let you close the tab
    2. The brain that needs to know where the tab is

    These aren't conflict. They're a workflow. Toby just gives them the same surface.

  • Why: Speaks directly to the AuDHD organising voice surfaced in @Galaxy42_'s tweet pattern. Generous, not exploitative — never says "ADHD" explicitly, never makes mental-health claims. Note: a competitor (ThoughtFold) just launched explicitly for "neurodivergent brains" — keeping our framing implicit is the right move; we don't compete on health-claim positioning.

  • Suggested timing: Thu 2026-05-21, 15:00 UTC.

  • Source: @Galaxy42_ tweet 2048389981626937556, 2026-04-26.

  • Variants: Drop the numbered list and write it as one sentence if it reads as too tidy.

Post 11 — P4, reactive (Arc/Dia transition window), no gate

  • Draft (244 chars):

    If you came to Arc because you wanted tabs to feel like things you could see and move around, that instinct was correct.

    It still works. It just lives somewhere else now.

    Toby keeps tabs as visual collections, in the new tab page where you already are.

  • Why: Real switcher window — @TheDevDesign (2050329431395237912, 2026-05-01) and @DazzioDG (2049999535309570136, 2026-04-30) both publicly miss specific Arc features in Dia. Carefully — never punch down at Arc; their team is still respected and many of our prospects are former-fans, not former-haters.

  • Suggested timing: Thu 2026-05-28, 15:00 UTC. Reassess if Arc reverses course.

  • Source: @arcinternet profile pivot to diabrowser.com URL (profile lookup 2026-05-10); @constantout's "tab hoarder" Arc-loss reply 2046254370434560465; fresh switcher signals above.

Post 12 — P2, evergreen, no gate

  • Draft (212 chars):

    "I'll deal with it tomorrow" tabs are a real category.

    Browser bookmarks won't hold them — too abstract. A Notion doc is overkill.

    A named collection is the right size: light enough to make, persistent enough to trust.

  • Why: Articulates a JTBD shape no competitor is naming — the in-between of "discardable" and "archive-worthy". Differentiates from both bookmark managers and KM tools without naming either.

  • Suggested timing: Tue 2026-05-26, 15:00 UTC.

  • Source: brand-soul "trade-off" axiom (product/strategy/soul.md).

Post 13 — Pinned-post candidate, P1+P4, evergreen, 🔒 acct-gated only

  • Draft (267 chars):

    Toby is a Chrome extension that turns your open tabs into named, visual collections. Save a window in one click. Open tomorrow — it's still there.

    The brand promise we hold ourselves to: "It's okay, Toby has it now."

    That's the whole product. gettoby.com

  • Why: Once the account is verified (🔒 acct), this should replace whatever pinned tweet is up there now (currently the Google Cloud outage status from 2025-06-12). It's the canonical anchor any new visitor sees first. Reflects the actual brand soul language.

  • Suggested timing: Day 1 of relaunch, after acct cleared. Pin and leave.

  • Source: product/strategy/soul.md ("It's okay, Toby has it now.").

Posting calendar (proposed)

DateSlotPost #PillarGates
Day 1 (post acct)pinned13P1+P4🔒 acct
Tue 2026-05-1215:00 UTC1P1—
Wed 2026-05-1315:00 UTC2P1 (tab-loss)—
Thu 2026-05-1415:00 UTC3P4—
Tue 2026-05-1915:00 UTC5P2—
Wed 2026-05-2015:00 UTC7P1+P2—
Thu 2026-05-2115:00 UTC10P1 (AuDHD)—
Fri 2026-05-2215:00 UTC6P5needs curator OK
Tue 2026-05-2615:00 UTC12P2—
Wed 2026-05-2715:00 UTC8P3🔒 rel (post-hotfix)
Thu 2026-05-2815:00 UTC11P4 (Arc switcher)—
reactive—4P17-day window
reactive—9P5 (QT)wait for Chrome

That's 11 original posts + 2 reactive over a 3-week window — exactly the 3-posts/week cadence specified in strategy.

Drafts NOT proposed this run (and why)

For operator awareness, items the agent considered and explicitly did NOT include:

  • AI-organize / "let Toby name your collection" hype post. AI relaunch is deferred to Q4 2026; pre-announcing creates an expectation gap. Also: Uncluttr is now publicly building this lane — entering it would be choosing a fight on a worse footing. Will revisit when our feature ships.
  • "Toby Mini vs Full" comparison thread. Worth doing but only after the reliability hotfix ships and CWS reviews stabilise.
  • Direct shot at OneTab / Workona / Session Buddy / new entrants (Uncluttr, TabVault Pro, ThoughtFold, TabRack, tab-out, leap-tabs). Pointless punching — older ones are dormant; new ones have 0-300 followers. Comparison content is fine; trash-talk and subtweet-style content is brand-poison per toby/strategy/playbook.md anti-bets.
  • "Hot take: bookmarks are dead" thread. Too on-the-nose. The bookmarks position belongs in evergreen one-liners (post 3), not in shouty thread form.
  • Holiday filler (Mother's Day 2026-05-10 came and went; we didn't post and we shouldn't). See toby/x/strategy.md "Cadence — Hard rule".
  • "We're back!" relaunch announcement. Posting "we're back" while the account has been silent for 11 months and the product has a live blank-page reliability incident is the worst possible first move. Just post Post 1. Let the relaunch be evidenced by quality.