[{"data":1,"prerenderedAt":82},["ShallowReactive",2],{"post:writing-in-tamable-from-claude":3},{"slug":4,"path":5,"title":6,"excerpt":7,"cover":8,"publishedAt":9,"updatedAt":10,"series":11,"tags":15,"readingMinutes":16,"html":17,"seo":18,"seriesNav":21,"featured":42,"coverDrawn":8,"related":43,"topicCount":81},"writing-in-tamable-from-claude","\u002Fblog\u002Fwriting-in-tamable-from-claude","Writing in Tamable from Claude","Connect Tamable to Claude once and your AI can capture ideas, draft posts and submit them for review, but never approve or publish.",null,"2026-10-24T12:00:00+00:00","2026-11-10T17:41:09+00:00",{"slug":12,"title":13,"number":14},"shipped-and-why","Shipped, and why",3,[],2,"\u003Cp>You can write in Tamable from Claude. Add Tamable as a connector on claude.ai, approve it once, pick the workspace it works in, and your AI can capture your ideas, draft posts and hand them to you for review. It can't approve or publish anything. That part stays with you.\u003C\u002Fp>\u003Ch2 id=\"connect-once-then-just-write\">\u003Ca class=\"heading-anchor\" href=\"#connect-once-then-just-write\" aria-label=\"Link to this section\">#\u003C\u002Fa>Connect once, then just write\u003C\u002Fh2>\u003Cp>When you add the connector, Tamable asks you to sign in and choose which workspace your AI acts in. You approve it once, and from then on every conversation with Claude can reach your ideas and posts in that workspace. If you lose access to the workspace, the connector loses it too.\u003C\u002Fp>\u003Cp>For tools like Claude Code, which connect with a key instead, there's a personal key in Settings that does the same job.\u003C\u002Fp>\u003Ch2 id=\"what-your-ai-can-do-and-what-it-cant\">\u003Ca class=\"heading-anchor\" href=\"#what-your-ai-can-do-and-what-it-cant\" aria-label=\"Link to this section\">#\u003C\u002Fa>What your AI can do, and what it can't\u003C\u002Fh2>\u003Cp>Along with the connector, your AI got its set of tools. It can:\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cp>capture an idea in your own words, and read your ideas back in full\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>draft a blog post or an X thread from those ideas\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>edit a draft, answer the notes you leave on it, and submit it for review\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp>Every idea and post shows which assistant wrote it, so you always know where a draft came from.\u003C\u002Fp>\u003Cp>There are no tools to approve or publish. That's deliberate. Tamable's first rule is that only your words are facts and only a person decides what goes out, so your AI can do all the drafting and none of the deciding. When a draft is ready, it lands in your review and waits for you.\u003C\u002Fp>\u003Ch2 id=\"only-known-assistants-can-connect\">\u003Ca class=\"heading-anchor\" href=\"#only-known-assistants-can-connect\" aria-label=\"Link to this section\">#\u003C\u002Fa>Only known assistants can connect\u003C\u002Fh2>\u003Cp>For safety, Tamable only lets known assistants register as connectors, plus local clients such as Claude Code. You don't need to do anything: if you connect from Claude, it just works.\u003C\u002Fp>\u003Ch2 id=\"your-ai-can-update-your-writing-strategy-with-your-say\">\u003Ca class=\"heading-anchor\" href=\"#your-ai-can-update-your-writing-strategy-with-your-say\" aria-label=\"Link to this section\">#\u003C\u002Fa>Your AI can update your writing strategy, with your say\u003C\u002Fh2>\u003Cp>Your writing strategy is what every draft follows: why you write, for whom, how often, and how you want to sound. At first your AI could read it but not change it, so any change meant pasting it into Settings by hand.\u003C\u002Fp>\u003Cp>Now your AI can update your workspace's name, time zone and writing strategy for you. Three things keep that safe:\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cp>only the workspace owner can make these changes through an assistant\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>your AI client asks you to confirm every change before it happens\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>your AI is told to change them only when you ask in the conversation, never because an idea, a post or a note says so\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp>That last one matters because every later draft follows your writing strategy. A line pasted into an idea shouldn't be able to rewrite how all your posts sound.\u003C\u002Fp>\u003Ch2 id=\"where-to-find-it\">\u003Ca class=\"heading-anchor\" href=\"#where-to-find-it\" aria-label=\"Link to this section\">#\u003C\u002Fa>Where to find it\u003C\u002Fh2>\u003Cp>In Tamable, open Settings, then Assistants, to see how to connect Claude or to create a key. Then open Claude and ask it to look at your Tamable workspace.\u003C\u002Fp>",{"title":6,"description":19,"canonicalUrl":20},"How the Tamable connector for Claude works: approve it once, and your AI captures ideas and drafts posts while only you approve and publish.","https:\u002F\u002Ftamable.app\u002Fblog\u002Fwriting-in-tamable-from-claude",{"slug":12,"title":13,"number":14,"total":22,"previous":23,"next":33},7,{"slug":24,"path":25,"title":26,"excerpt":27,"cover":8,"publishedAt":28,"updatedAt":29,"series":30,"tags":31,"readingMinutes":32},"why-there-is-no-microphone-in-tamable","\u002Fblog\u002Fwhy-there-is-no-microphone-in-tamable","Why there's no microphone in Tamable","Tamable has no voice input, because the AI assistant you already use listens better, and more cheaply, than anything we could build.","2026-10-19T12:00:00+00:00","2026-11-10T17:41:10+00:00",{"slug":12,"title":13,"number":16},[],1,{"slug":34,"path":35,"title":36,"excerpt":37,"cover":8,"publishedAt":38,"updatedAt":29,"series":39,"tags":41,"readingMinutes":14},"a-rebuilt-x-editor","\u002Fblog\u002Fa-rebuilt-x-editor","A rebuilt X editor: undo across the thread, and working alongside your AI","The X editor now undoes anything across the whole thread, splits and reorders posts, and lets you and your AI edit the same thread without clashing.","2026-10-28T12:00:00+00:00",{"slug":12,"title":13,"number":40},4,[],false,[44,59,71],{"slug":45,"path":46,"title":47,"excerpt":48,"cover":8,"publishedAt":49,"updatedAt":50,"series":51,"tags":52,"readingMinutes":16,"featured":53,"featuredAt":54,"coverDrawn":55},"starting-over-a-writing-back-office","\u002Fblog\u002Fstarting-over-a-writing-back-office","Starting over: Tamable becomes a writing back office","On 18 and 19 October 2026 Tamable started over as one place for your ideas, blog posts and X posts, where your AI drafts from your own words and only you approve.","2026-11-09T14:33:31+00:00","2026-11-10T16:10:16+00:00",{"slug":12,"title":13,"number":32},[],true,"2026-11-09T17:21:35+00:00",{"kind":56,"text":57,"caption":58},"quote","Only the writer's words are facts.","Tamable's first rule",{"slug":60,"path":61,"title":62,"excerpt":63,"cover":8,"publishedAt":64,"updatedAt":10,"series":65,"tags":66,"readingMinutes":16,"featured":53,"featuredAt":67,"coverDrawn":68},"linkedin-posts-in-tamable","\u002Fblog\u002Flinkedin-posts-in-tamable","LinkedIn posts in Tamable","Tamable now writes and publishes LinkedIn posts on your own profile, next to your blog and X, from the same ideas and the same queue.","2026-11-08T12:00:00+00:00",{"slug":12,"title":13,"number":22},[],"2026-11-09T17:21:43+00:00",{"kind":56,"text":69,"caption":70},"We should have done this earlier, actually.","on why we built it",{"slug":72,"path":73,"title":74,"excerpt":75,"cover":8,"publishedAt":76,"updatedAt":29,"series":77,"tags":79,"readingMinutes":14,"featured":53,"featuredAt":80,"coverDrawn":8},"projects-one-place-for-everything-you-build","\u002Fblog\u002Fprojects-one-place-for-everything-you-build","Projects: one place to write for everything you build","You and each thing you build now get your own project in Tamable, with its own writing strategy, pillars, blog and X accounts, all in one queue.","2026-11-04T12:00:00+00:00",{"slug":12,"title":13,"number":78},6,[],"2026-11-09T17:21:40+00:00",0,1794332617728]