Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Introducing cmux history: cmux now has support for reopening closed terminals/browsers/workspaces via ⌘+Shift+T History also supports reopening closed Claude Code/Codex/OpenCode/etc sessions You can also jump back and forward through recently focused workspaces/terminals with the navigation buttons or ⌘+[ and ⌘+] (similar to a browser) Run `cmux hooks setup` once...

15,723 görüntüleme • 4 ay önce •via X (Twitter)

22 Yorum

Steven Torres profil fotoğrafı
Steven Torres4 ay önce

@manaflowai Love seeing the new features! cmux has been amazing to use

MikeZ93 profil fotoğrafı
MikeZ934 ay önce

Are you planning Support for @FactoryAI Droid 🤞

Austin Wang profil fotoğrafı
Austin Wang4 ay önce

Free & open source (GPL)

Harish profil fotoğrafı
Harish4 ay önce

Chad

Sebastian Kehle profil fotoğrafı
Sebastian Kehle4 ay önce

cmux filetree when?

Gregor profil fotoğrafı
Gregor4 ay önce

lost a 2hr codex session last tuesday

Alexander Malakhov profil fotoğrafı
Alexander Malakhov3 ay önce

Reopening closed agent sessions is the kind of boring workflow feature that matters. I built Agent Sessions for the browse/search side of local Claude/Codex/OpenCode history.

A Failure Atlas profil fotoğrafı
A Failure Atlas4 ay önce

This matters more than it looks. For AI agent workflows, recovery is part of reliability. Reopening the exact workspace helps preserve the trail when a run goes wrong.

Abhishek Kumar profil fotoğrafı
Abhishek Kumar4 ay önce

How do you make money ?

JMoon profil fotoğrafı
JMoon4 ay önce

Half the value of a working session lives in the context built up inside it. Cmd+Shift+T for session context is a real thing and most people miss it.

Valentin profil fotoğrafı
Valentin4 ay önce

Bless your heart

prateek profil fotoğrafı
prateek4 ay önce

this is so cool @lawrencecchen, I might steal some of your keybindings!

Matheus Pimenta profil fotoğrafı
Matheus Pimenta4 ay önce

When will they launch for Windows?

Nick Venturi profil fotoğrafı
Nick Venturi4 ay önce

finally i can rage quit my terminal and pretend it never happened

vivek bhardwaj profil fotoğrafı
vivek bhardwaj4 ay önce

> History also supports reopening closed Claude Code/Codex/OpenCode/etc sessions saved my life more than once, tysm

tanpachiro kamado profil fotoğrafı
tanpachiro kamado4 ay önce

Do we resolve the slow part of the PermissionRequest hook? I love cmux but that slow part ruined my workflow.

josh 🏔️ profil fotoğrafı
josh 🏔️4 ay önce

just wrangled a homespun version for 20 mins yesterday. very delighted to see this!!

买call一时爽 profil fotoğrafı
买call一时爽4 ay önce

man, cmux is getting better!

Nova profil fotoğrafı
Nova4 ay önce

This is the unglamorous agent feature I trust most: recovery state. Losing a terminal/browser/workspace should not mean losing the receipt trail. Are reopened sessions preserving enough context to audit what changed before the crash?

Marco D'Alia profil fotoğrafı
Marco D'Alia4 ay önce

nice! Would be nice to have groups in the sidebar too!

Solomon Omolabi profil fotoğrafı
Solomon Omolabi4 ay önce

This is the kind of feature non-coders will underestimate until they lose context once. Reopening the exact terminal, browser, and agent session makes AI coding feel less like a chat and more like a real workspace with memory.

Matthew Lam profil fotoğrafı
Matthew Lam4 ay önce

is cmd shift t only opening the last recently closed?

Benzer Videolar

Another insane Jev use case! Jev makes it incredibly cheap to evaluate and classify agent runs at scale. And finally, someone open-sourced a self-improving memory layer that can put that capability to work across agent harnesses. It turns your agent sessions into a compounding knowledge layer, where every successful run can make future agents smarter across: - Codex - Claude Code - Cursor - OpenCode and 20+ more Beacon by Asymptote Labs continuously builds a shared history across your agent harnesses and uses Jev to identify the runs worth learning from. It then turns the best workflows, corrections, and debugging patterns into reusable skills. GitHub repo: (don’t forget to star it ⭐) Most agent runs are messy. They contain exploration, failed commands, dead ends, and one-off fixes that should never become permanent memory. So Beacon preserves the full session history, while Jev helps decide what should be promoted, reviewed, or discarded. The recording below shows this in action. Beacon found 579 sessions across 5 coding-agent harnesses and normalized them into one consistent history. From there, Jev surfaces the lessons worth keeping and makes them available across your agent stack. - A pattern learned in Cursor can carry into OpenCode. - A lesson from Claude Code can improve the next Codex run. Every successful run adds to the shared knowledge layer, making future agents smarter. If you want to dive deeper into Jev, I also wrote a breakdown of how it works. The article is quoted below.

Akshay 🚀

119,118 görüntüleme • 10 gün önce

Another insane Jev use case! Jev is making it dramatically cheaper to evaluate what actually happened inside an agent run. And finally, someone open-sourced a self-improving memory layer that can put that signal to work across agent harnesses: - Claude Code - Codex - Cursor - OpenCode, and 20+ more Beacon by Asymptote Labs continuously captures your agent history across harnesses and uses Jev to identify which runs are actually worth learning from. It then turns the highest-signal workflows, corrections, and debugging patterns into reusable skills. GitHub repo: (don’t forget to star it ⭐ ) Beacon preserves the complete session history. But preserving a run and learning from it are two different things. Most coding-agent sessions contain routine exploration, failed commands, and fixes that only apply to one task. The trace can remain available for inspection without turning every detail into guidance for future agents. Jev scores each run for evidence, reuse potential, and human correction signals. An application policy then decides whether to promote, review, or discard it. The recording shows this in action. Claude receives a coding task, modifies the implementation, and runs the tests. I then provide an edge-case correction, so Claude updates the code and adds regression coverage. Beacon automatically captures the complete session. Jev evaluates whether the correction contains a reusable engineering lesson. Once approved, that lesson becomes available to other coding agents working on the project. Since it works across harnesses: - Claude Code sessions can teach Codex. - Cursor debugging can improve OpenCode. So a problem solved by one agent should not need to be learned from scratch by another. If you want to dive deeper into Jev, I also wrote a hands-on guide to building this Jev-style decision path with open models, entirely locally. Read it below.

Avi Chawla

290,485 görüntüleme • 12 gün önce