The B2B Podcast Index
Index
All categories
MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
MethodologySubmit
Best of:MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
An independent project byFame
SearchBest episodesGuestsInsightsMethodologySubmit a podcast
Index/AI & Data/Let's Talk AI
Let's Talk AI artwork

#100 - Tmux Tutorial: Boost Developer Productivity Like a Pro | Thomas Bustos

Let's Talk AI · 2026-02-25 · 13 min

0:00--:--

Key moments - from our scoring

Substance score

25 / 100

Five dimensions, 20 points each

Insight Density6 / 20
Originality7 / 20
Guest Caliber4 / 20
Specificity & Evidence5 / 20
Conversational Craft3 / 20

Thomas Bustos walks through his approach to achieving high developer productivity, explicitly pushing back against the notion that cloud bots alone make you 10x - instead emphasizing a deliberate tech stack combining Tmux, Cloud Code, NeoVim or Cursor, and Yoko OS (a custom operating system he built). He demonstrates real workflows using his Reader application (a PDF paper management tool synced with Obsidian) to show how Tmux sessions let you spawn parallel Claude AI contexts, each with isolated project scope. A key practice he highlights is using MCPs (Model Context Protocols) like Excalibur to generate design variations, wireframes in Scapple Draw, and competitive analysis tables in seconds. Bustos shows how to manage context window bloat by saving generated outputs as Markdown files and using a "restore prompt" technique to reclaim 20% of context midway through work. His daily/weekly/monthly skill automation in Yoko fights entropy by cascading through calendar checks, vault reviews, and structured planning. The episode targets engineers building their own development environments and those using Claude AI for feature iteration and UX design.

Key takeaways

  • →Tmux paired with Cloud Code lets you spin up isolated AI sessions per feature, each with its own repo context and persistent .md files for inter-session communication.
  • →Use MCPs like Excalibur to generate design tables, wireframes, and competitive positioning matrices in seconds rather than manually creating them.
  • →Save all Claude-generated outputs to Markdown files in Obsidian and use "restore prompt" mid-conversation to reclaim consumed context window tokens.
  • →Yoko OS with cascading daily/weekly/monthly skills automates entropy management by checking calendars, vault files, and goals before each work session.
  • →Cloud bots are useful for experimentation but aren't the 10x productivity lever - straightforward tools like Tmux, SSH, and a solid CLI are more directly correlated to engineering goals.

Topics in this episode

Cloud CodeCursor IDEObsidianTmuxYoko OSReader appClaude AI MCPsExcaliburNeoVimScapple Draw

Questions this episode answers

How do you prevent Claude AI context window from filling up during long design iterations?

Thomas saves all Claude-generated content (wireframes, tables, screenshots) to Markdown files in Obsidian, then uses a 'restore prompt' command to clear the conversation and reclaim ~20% of the context window while maintaining access to previous outputs.

How does Tmux help manage multiple Claude AI sessions?

Tmux lets you spawn new sessions from an existing one using a 'spawn' skill that automatically CDs into the target repo, creates a temporary .md file for instructions, and gives each Claude session its own isolated context window while keeping them linked through shared files.

What is the Reader app and how does it integrate with Obsidian?

Reader is Thomas's open-source PDF paper management tool running locally on port 4100 that lets users upload papers, create study cards from notes, and automatically sync all content with Obsidian as a searchable second brain.

How do you use MCPs like Excalibur for UX design?

Excalibur (an MCP) generates design tables of UI ideas, proposes wireframe variations, pulls color palettes from your codebase, and creates competitive positioning matrices - all in seconds and exportable to Scapple Draw for visual iteration.

What is Yoko OS and what problem does it solve?

Yoko is Thomas's custom operating system that automates daily/weekly/monthly review scripts to fight entropy by cascading through calendar checks, vault file reviews, and goal alignment before each work session.

What our scoring noted

Our reviewer’s read on each dimension, with quotes from the episode.

Insight Density

6 / 20

The episode contains a few genuinely interesting developer workflow ideas - like spawning sub-Claude Code sessions to isolate context windows and using a 'restore prompt' trick to recover 20% of a context window - but these are buried under disorganised, stream-of-consciousness narration. Most of the runtime is spent describing what is happening on screen rather than delivering transferable insight, and the relevance to B2B operators is marginal at best.

here I used a skill that I call spawn, where it's basically taking a current to max session and going into another one with all the context, which is similar to compacting or clearing, saving everything in .md before
I can just get all this context back because all of this is already generated and we don't need it earlier. So I can just go like here and go back there, restore prompt and voila. Now I'm like at 60 so I just got back 20% of the context window

Originality

7 / 20

The multi-agent Claude Code session architecture with a 'spawn' skill and a personal OS ('Yoko') connected to an Obsidian vault is a genuinely idiosyncratic workflow not commonly covered, but the overarching framing of 'path to 10x engineer' is one of the most recycled tropes in developer content. The contrarian note about Cloud Bot not being the 10x tool is a fleeting and underdeveloped point.

I wouldn't say that cloud, both are open cloud when you're doing deep engineering work, is the tool that is going to make you 10x
Yoko is my operating system, so it has lots of skills, and it connects to another repo, which I call my vault, and it's basically an obsidian, a second brain

Guest Caliber

4 / 20

This is a solo tutorial monologue by the host with no guest and no stated credentials, seniority, or demonstrated scale. There is no evidence of building or shipping at scale that would give the content authority beyond 'here is my personal setup.'

In this episode, we're going to cover a few cool things and we're going to comment the path to 10x engineer, which is a poster recently where you can see my stack, everything that I use
I hope that you enjoyed this brief video on getting your hands on using Tmux

Specificity & Evidence

5 / 20

Tool names are cited specifically (Tmux, Claude Code, NeoVim, Cursor, Excalidraw, Obsidian) and one port number is mentioned, but there are zero business outcomes, no team size, no revenue or time-saving metrics, and no benchmarks. Evidence is entirely limited to 'this is what I do on my machine.'

Right now it's running in the port 410
Now I'm like at 60 so I just got back 20% of the context window which is great

Conversational Craft

3 / 20

This is an unstructured solo screen-share monologue with no interviewer, no questions, no follow-ups, and no pushback. The narration frequently loses its thread mid-sentence and relies on the viewer watching a screen that is not accessible in audio form, making the content nearly incomprehensible as a standalone episode.

So this is Reader. And here you can see that it has the favicon updated, etc. This is a simple feature.
So a few notes while this is being generated. You can analyze repos, you can generate tables of options when analyzing repo to like map what you have in mind versus what already exists.

Conversation analysis

Computed from the transcript - who did the talking, and the words that came up most.

Most-used words

cloud12session9recommend8code8context8reader8repo7example7generate7cool6excalibur6generated6open5tmux5check5usually5

Episode notes

Every developer struggles with context-switching, managing multiple sessions, and maintaining focus. Enter Tmux. Tmux is a tool Thomas Bustos calls the backbone of his productivity. In this episode, he walks through his full tech stack, explains how deep work sessions are structured, and shows how Tmux integrates with NeoVim and Cloud Code for maximum efficiency. Learn how to track metrics, iterate on user experience, and keep your workflow aligned with your goals. If you want to move from “busy” to “productive,” this episode is a must-listen. Top Takeaways: Cloud tools can enhance productivity but aren't the sole solution. Tmux is a core tool for managing sessions effectively. Daily skills help manage entropy and keep goals aligned. Using a tech stack that includes NeoVim and Cloud Code is beneficial. Iterating on user experience is crucial for app development. Context management is key in software engineering. Open source tools can be integrated for better workflow. Security and setup considerations are important for cloud tools. Deep work sessions can lead to more productive outcomes. Feedback and iteration are essential in the design process. Chapters: 00:00 Welcome!

Full transcript

13 min

Transcribed and scored by The B2B Podcast Index.

I wouldn't say that cloud, both are open cloud when you're doing deep engineering work, is the tool that is going to make you 10x. I definitely think that you can be extremely productive and inefficient using it, but not necessarily what will make you the most productive. All right, let's do this. In this episode, we're going to cover a few cool things and we're going to comment the path to 10x engineer, which is a poster recently where you can see my stack, everything that I use, some interesting references that I would recommend in a specific use case, as well as spending some time in Tmux so that we can comment on cool processes and ways to use those tools based on your workload.

So starting from the setup, my favorite tech stack right now is this one, Cloud Code, Tmux. You can use NeoVim or whatever you prefer. I use both. Cursor, when I want to be more on an ID VS Code thing, and I'm picking up NeoVim.

The interesting thing here is Yoko, maybe. So Yoko is my operating system, so it has lots of skills, and it connects to another repo, which I call my vault, and it's basically an obsidian, a second brain. And so they interact very well together, and it helps me manage lots of things, including MCB setups, as well as lots of other things. All of this is open source, so you can check it out.

And the cool thing is that if you're thinking about your own setup, I would recommend that video from Miska. I hope I pronounced this name correctly. If you haven't set up T-Max yet, I would recommend this video for you to follow. It's a great reference.

All the rest resources, and at the end of this post, you will be able to see what you need to go deeper into these different subjects. My core goal right now is to show you a few examples and go to this T-Max session and give real examples of things that you can do. So the first thing is that I use a daily or a weekly skill or a monthly. And basically what this does is it's going to take me through a very specific set of steps to manage entropy around my vault and my goals and it connects to my life pillars, et cetera.

So if you take a daily, for example, DailySkill is going to take you through checking the prerequisites, checking which day are we, the states, checking your calendars. If you have multiple calendars, it will check those. And then you have like a cascade. It checks all the relevant files from your vault.

So this is to fight entropy. Then project updates, people network, task system. And then it processes the information, load extension, check current date, read context, gather information. And now it starts building a table, a draft of a plan with deep work and sessions that are in your calendars.

So this is just one example of all the things that I use in my OS. I usually CD into it and start a cloud code session and then I manage everything from that session. So this is a very specific example, designing a UX. I created here a use case where I have an open source repo that is called Reader This is Reader So here I did the simple analysis of the structure You can see that it an HGS app that has some UI components into it Then I use this to generate the best practices table.

And what's interesting about this is that here I asked it to do a simple change of the icon here. By the way, this is Reader. This is the app. You can see it's in localhost.

Right now it's running in the port 410. And what it does is that you upload papers and it's synced with MyObsidian. It has teams, it has settings, it has a comment palette to do all kinds of things. It has a guide, which is basically how to use it, a methodology to read papers that I picked from Latent Space and also somewhere else I can recommend the resources.

So this is Reader. And here you can see that it has the favicon updated, etc. This is a simple feature. But more importantly, when I used Spawn here, what it did was that it created a new session and a temporary .

md file to give instructions to that specific cloud card. But before doing this, it CD'd into the reader repo. So now this one created this session so that it has its own context window as well as directly being into the repo it's working on. this can write notes into .

md that this one can also read later. There are different ways to make them pair like that. And some will work in parallel, some like more as a master in like sub-cloud code sessions. There's like many things that you can do.

But here I used a skill that I call spawn, where it's basically taking a current to max session and going into another one with all the context, which is similar to compacting or clearing, saving everything in .md before. But the way I've set this up, I like to jump from cloudcast session to cloudcast sessions. A very interesting example here that I think is worth mentioning is that if I check my MCPs right now, you can see that I have all of those.

And here you can see that I have Excalibur. And so what I was doing earlier is that I have Excalibur running here. And all of those are questions of UI that I was thinking about. So for example, I asked, okay, we have our PDF reader app where I can ask things about a paper here.

That's great. But like, what other things could I do? Like recommend me. So basically what it did is that it generated a table with ideas and then I asked it, okay, cool.

I like those ideas. And for the flashcards slash conky kind of experience, proposed me a few UX examples. And so it used MCP, the MCP of Excalibur to generate those variations. and then I asked it to go and look at all the different colors that I know of in my code base, so in my system design, and show me the color palette as well as a brand and positioning and a competitive landscape and a matrix of where would you position it or to compare to existing solutions, etc.

And so all of this was generated in seconds. What I would usually do here is that I might just take a screenshot of this one just to iterate on that example Maybe what we can do is that we can clear this conva Also what I usually do is that I copy all the things that are generated on the locally running Excalibur and I put them into my Obsidian in an Excalibur plugin file so that I keep track of everything and I constantly clear so that context aware. So I will paste the screenshot with this direction, generate four new, more detailed wireframes to have a very clean experience from reading a paper to testing yourself.

Think about the user neuron. Create all visuals in ScalicDraw, Xenium, CP. So that would be an example. And so here I can maybe take a screenshot of this so that it has like an understanding of what this looks like and I can just run this.

And so what this will do is that it will help me iterate on the Scandero combat basically and generate IDs. The ideation process is something that I wrote here about, which is you can just use all your MCPs and granular MCPs to get all the transcripts, etc. And then you can do this kind of prompts to ideate on top of what everyone said so that you get directions and you kind of know the intuition of which direction makes more sense and thinking from first principle what's the best user experience based on all the information that I have so far.

Here it's going to generate and using this candy draw and it's going to be working right here. So a few notes while this is being generated. You can analyze repos, you can generate tables of options when analyzing repo to like map what you have in mind versus what already exists. And then you can ask to create schemas in a Scalidraw so that you can visually look at the table entities and all that.

There are so many things that are possible. You can see that this is very context-heavy, so I have some best practices around that. But you can spin up new Cloud Code to work on dedicated features as well as having one big scope with one big plan and having it one-shotted through one session, basically. That's possible.

Generally, Scalidraw is what we commented. And here in a moment, I'm going to share with you how I save lots of context when I'm doing these kind of things. So if we go back into Excalibur, here you can start seeing a representation of your app currently. And so now it's telling, okay, cool, you're in reading mode and maybe now you also have cards.

Okay, so deep reading mode, this is one. Then card creation from notes, I can like generate study card based on the notes that I have in my app. What is the purpose of pre-training in GPT? That would be like a focused study mode where you go through your cards and then what happens during the fine tuning stage maybe that would be for quick review widget this is like a user journey that he proposed here you would have read paper technos create cards to the cards and quick review now from this i can like save that and ideate on yeah this makes sense i would prefer this here what about those considerations can you look at this transcript from conversation that i had with someone so that you can reflect So that gives you a very strong idea of how I usually iterate on those things Now what I wanted to show you is that see now that we at 56 because we generated all of that and in reality I can just get all this context back because all of this is already generated and we don't need it earlier.

So I can just go like here and go back there, restore prompt and voila. Now I'm like at 60 so I just got back 20% of the context window which is great because now instead of asking it to do that I can just remove all of this and I will be able to now take a screenshot like this and be, okay, so now this is what we want to do. This is what we have. I can go there and remove the previous screenshots and do something else.

Okay. So that's like the bonus point. Now, what I would share with you is that if you're building these days, I would recommend that you have an IT, either cursor or whatever is your favorite. Then I would have a CLI.

Highly recommend T-Mux here. I think it's the PowerPoint of this video. Then you can have agents that can run in the background, either you're open cloud or maybe more sculpt agents like Devin that directly works on a code base. And then like being able to connect remotely to your computer with SSH.

I'm not speaking about a cloud bot here and you can see that there is cloud bot here. The reason I added it is because it's a trend. So I think it's just cool to look at, but I wouldn't say that cloud bots are open cloud when you're doing deep engineering work is the tool that is going to make you 10x. I definitely think that you can be extremely productive and efficient using it, but not necessarily what will make you the most productive.

It feels to me more like something fun to play around and experiment with, and that you can definitely get value out of it. But you also want to think about the security and the setup, which is quite consuming and intensive in resources, whereas all of those are straightforward and directly correlate it to your goals. So we've covered everything that I wanted here, which is a pass to the next engineer. We've reviewed how I usually use my Yoko setup, design UX, building features.

Here you can see the creator of CloudBot talking about how he ships code. Here you have all the resources around NeoVim and Tmux if you want to set it up yourself. This is like a map that I would recommend that is useful, especially if you want to go into NeoVim, Vim kind of things, but that's optional, totally optional. And I hope that you enjoyed this brief video on getting your hands on using Tmux.

This is how I would connect to the Tmux session. So currently my sessions, I think that have Turing, have a work one and a live demo, which is where we were. If I just run my attached, this is like where we started creating all the demo things on top of the reader repo. And the reader repo is also accessible here.

So you can just check it out. It has everything into the doc. I hope that was helpful. If you have any questions, let me know.

If you have ideas of future episodes, I would love to know that. And I will see you in the next one. Ciao.

Related episodes across the Index

Other episodes covering the same guests and topics, from across The B2B Podcast Index.

  • How AI Is Rebuilding Every DTC Creative TeamScalability School · on Cloud Code86 / 100
  • The Generalist’s Revenge: How AI is Leveling the Professional Playing Field | Tim CakirUnlocked Professional: AI and Future of Work · on Cursor IDE77 / 100
  • Full-Stack Signals in Solid, AI Development, and the Future of Web Frameworksegghead.io developer chats · on Cursor IDE76 / 100
  • The context engineering playbook (Claire Gouze)The Analytics Engineering Podcast · on Cursor IDE75 / 100
  • 91. AI in The Future of WorkThe Operations Room: A Podcast for COO’s · on Cloud Code75 / 100
  • Developer-First DAST: Fix Security Issues Before They Reach Production with Gadi BashvitzTestGuild Devops Toolchain Podcast · on Cursor IDE70 / 100

More from Let's Talk AI

All episodes →
  • #99 - The 3 Pillars Every AI Leader Needs to Master | Thomas Bustos
  • #98 - The Rise of the AI Native Employee | Thomas Bustos
  • #97 - AI Native Companies Explained: How Startups Should Build With AI | Thomas Bustos
  • #96 - Why Every Early Stage Founder Needs a Learning Engine | Thomas Bustos
  • #95 - The First 5 Customers: A Framework for Early Stage Founders | Thomas Bustos
Explore the best B2B AI & Data podcasts →
All Let's Talk AI episodes →