<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Wave Terminal Blog]]></title><description><![CDATA[An open-source, cross-platform terminal for seamless workflows]]></description><link>https://blog.waveterm.dev</link><generator>RSS for Node</generator><lastBuildDate>Thu, 10 Sep 2026 04:56:34 GMT</lastBuildDate><atom:link href="https://blog.waveterm.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[No Compromises: Why Your Terminal Should Be Open Source]]></title><description><![CDATA[Terminals are the backbone of developer workflows, yet some modern options have decided to stay closed, limiting your control and flexibility. You shouldn't have to choose between cutting-edge features and the freedom of open source. We believe that ...]]></description><link>https://blog.waveterm.dev/no-compromises-why-your-terminal-should-be-open-source</link><guid isPermaLink="true">https://blog.waveterm.dev/no-compromises-why-your-terminal-should-be-open-source</guid><category><![CDATA[devtools]]></category><category><![CDATA[command line]]></category><category><![CDATA[Open Source]]></category><category><![CDATA[privacy]]></category><category><![CDATA[Security]]></category><dc:creator><![CDATA[Mike Sawka]]></dc:creator><pubDate>Fri, 04 Oct 2024 15:00:27 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1728003845150/e12e86ba-0de5-49c2-a5c3-13b5a1ddd7bf.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Terminals are the backbone of developer workflows, yet some modern options have decided to stay closed, limiting your control and flexibility. You shouldn't have to choose between cutting-edge features and the freedom of open source. We believe that your terminal should offer both innovation and openness, and here's why.</p>
<p><strong>Privacy You Can Trust</strong></p>
<p>Knowing what information your tools collect is crucial. Open-source terminals make it easy to verify exactly what data is being gathered and how it's used. There's no need to take a company's word for it; the proof is in the code. Without access to the source code, “unintended” bugs or features could lead to data being collected without your knowledge or consent, leaving little room for accountability. This level of assurance is especially important for terminals, which handle sensitive information and have extensive system permissions.</p>
<p><strong>Security Through Transparency</strong></p>
<p>When it comes to tools that have deep access to your system, security is paramount. Open-source terminals offer transparency that closed-source alternatives simply can't match. By allowing anyone to inspect the code, open-source projects enable the community to identify and fix vulnerabilities swiftly. This collective vigilance ensures that security isn't just a feature—it's a fundamental aspect of the software's DNA.</p>
<p><strong>A Community-Driven Future</strong></p>
<p>One of the most significant advantages of open source is the power of community contributions. Developers worldwide can fix bugs, add features, and optimize performance. This collective effort accelerates innovation and leads to a more robust, versatile tool. When the community drives development, software can evolve more quickly to meet the needs of its users, not just the goals of a single company.</p>
<p><strong>Project Continuity and Ownership</strong></p>
<p>With open-source software, you're not at the mercy of a company's shifting priorities or business decisions. Even with a company's assurances, they could change the terms, introduce fees, or discontinue the product altogether. Open source ensures that the code remains accessible to everyone, allowing the project to live on regardless of what happens to its original creators. This gives you the confidence to invest time and resources into customizing your terminal without worrying about unexpected changes or limitations down the line.</p>
<p><strong>Supporting the Open Source Movement</strong></p>
<p>Choosing open-source tools contributes to a larger movement that values collaboration, transparency, and shared growth. It's about more than just software; it's about fostering a culture that prioritizes collective advancement over proprietary gains. By supporting open-source projects, you're investing in a future where technology is accessible and adaptable for everyone.</p>
<p><strong>Experience the Difference with Wave</strong></p>
<p>We've built <a target="_blank" href="https://waveterm.dev">Wave Terminal</a> with these principles in mind. Wave is a modern, open-source, cross-platform terminal designed to enhance your productivity without compromising on security or privacy.</p>
<p>Join us in shaping the future of terminal applications. Try Wave today, contribute to the project, or simply explore what a modern open-source terminal can offer. Together, we can create tools that not only meet our needs but also embody the values we believe in.</p>
<p>If you’re interested, please give us a star on <a target="_blank" href="https://github.com/wavetermdev/waveterm">Github</a>. You can download Wave for macOS, Linux, and Windows at <a target="_blank" href="https://waveterm.dev">waveterm.dev</a>.</p>
<hr />
<p><em>Stay focused. Stay productive. Choose open source.</em></p>
]]></content:encoded></item><item><title><![CDATA[Introducing the New Wave Terminal v0.8]]></title><description><![CDATA[We built Wave to make you holistically more productive. With an all-new layout engine and integrated widgets, Wave seamlessly blends the command line with file browsing, editing, web integration, and AI into one powerful environment. By eliminating d...]]></description><link>https://blog.waveterm.dev/introducing-the-new-wave-terminal-v08</link><guid isPermaLink="true">https://blog.waveterm.dev/introducing-the-new-wave-terminal-v08</guid><category><![CDATA[command line]]></category><category><![CDATA[cli]]></category><category><![CDATA[Open Source]]></category><category><![CDATA[Developer Tools]]></category><category><![CDATA[Productivity]]></category><dc:creator><![CDATA[Mike Sawka]]></dc:creator><pubDate>Wed, 25 Sep 2024 19:28:50 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1727220027506/1a3a73a0-525f-48f3-aa55-334b4689babd.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>We built Wave to make you holistically more productive. With an all-new layout engine and integrated widgets, Wave seamlessly blends the command line with file browsing, editing, web integration, and AI into one powerful environment. By eliminating distractions and keeping everything at your fingertips, Wave helps you maintain a smooth, uninterrupted workflow. Whether you're previewing files, automating tasks, or leveraging AI, it's designed to streamline your process, allowing you to stay focused and reduce the need for constant context switching.</p>
<h3 id="heading-a-command-line-reimagined">A Command Line Reimagined</h3>
<p>Traditional command-line interfaces (CLIs) are powerful, but they often require switching between different applications for tasks like previewing files, browsing the web, or using AI tools. Wave brings all these functions together in one place with a flexible layout and keyboard shortcuts. You can preview remote files, pull up documentation, or browse the web without ever leaving your terminal. With integrated widgets and seamless navigation, Wave keeps you in the flow so you can get more done.</p>
<h3 id="heading-faster-more-compatible-and-windows-native">Faster, More Compatible, and Windows Native</h3>
<p>Wave v0.8 is faster and more flexible than ever. It supports your standard terminal prompts and command completions while working smoothly with all shells (not just bash/zsh), removing the friction some users experienced with ohmyzsh packages. For the first time, Wave also runs <strong>natively on Windows</strong>, giving you a consistent experience across all major operating systems.</p>
<h3 id="heading-this-is-just-the-beginning">This is Just the Beginning</h3>
<p>Wave is open source and built with the community in mind. We're expanding its capabilities, adding support for creating your own widgets, and rolling out even more productivity features. Expect deeper AI integrations, better connections with external systems, and more ways to streamline your workflow. We're excited to continue evolving Wave, with your input helping to shape its future.</p>
<p>If you’re interested, please give us a star at https://github.com/wavetermdev/waveterm . You can download Wave at https://waveterm.dev (available for MacOS, Linux, and Windows).</p>
]]></content:encoded></item><item><title><![CDATA[Introducing BYOLLM!]]></title><description><![CDATA[What is BYOLLM?
At Wave, we wanted to ensure that users have a choice around whatever AI tools they bring to Wave, not just bolt on the latest AI trend. That's why we’re excited to announce the introduction of BYOLLM, or "Bring Your Own Large Languag...]]></description><link>https://blog.waveterm.dev/introducing-byollm</link><guid isPermaLink="true">https://blog.waveterm.dev/introducing-byollm</guid><category><![CDATA[WaveTerm]]></category><category><![CDATA[AI]]></category><category><![CDATA[llm]]></category><category><![CDATA[chatgpt]]></category><category><![CDATA[#ai-tools]]></category><category><![CDATA[terminal]]></category><category><![CDATA[openai]]></category><category><![CDATA[GPT 4]]></category><category><![CDATA[GPT-4o]]></category><dc:creator><![CDATA[Knox Lively]]></dc:creator><pubDate>Fri, 17 May 2024 21:12:10 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1715792711252/e2da2970-0c49-4185-aad1-198fdb564a66.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<h3 id="heading-what-is-byollm">What is BYOLLM?</h3>
<p>At Wave, we wanted to ensure that users have a choice around whatever AI tools they bring to Wave, not just bolt on the latest AI trend. That's why we’re excited to announce the introduction of <a target="_blank" href="https://docs.waveterm.dev/features/waveAI#third-party-llm-support-byollm">BYOLLM</a>, or "Bring Your Own Large Language Model." Whether it be for security, privacy, or even ethical reasons, this new feature enables users to use whatever LLM provider they like, right inside of Wave.</p>
<p>At the moment, Wave supports four local LLM providers — <a target="_blank" href="https://docs.waveterm.dev/features/supportedLLMs/ollama">Ollama</a>, <a target="_blank" href="https://docs.waveterm.dev/features/supportedLLMs/lmstudio">LM Studio</a>, <a target="_blank" href="https://docs.waveterm.dev/features/supportedLLMs/llamacpp">llama.cpp</a>, and <a target="_blank" href="https://docs.waveterm.dev/features/supportedLLMs/localai">LocalAI</a> — with the ability to <a target="_blank" href="https://docs.waveterm.dev/features/supportedLLMs/generic">bring your own</a>, OpenAI API-compatible (local or cloud-based) LLM provider if it's not officially supported. Each of these providers supports a wide range of models, essentially allowing users to bring hundreds of LLMs to their computers through this integration.</p>
<h3 id="heading-getting-started-with-local-llms">Getting Started with Local LLMs</h3>
<p>Setting up your own LLM in Wave is a simple process. Start by checking out our <a target="_blank" href="https://docs.waveterm.dev/features/waveAI#supported-llm-providers">supported LLM providers</a>, and from there select your LLM provider and follow the instructions. Configuration usually consists of setting just two parameters for local models: <em>aibaseurl</em> and <em>aimodel</em>. These parameters can be set either through the UI or from the <a target="_blank" href="https://docs.waveterm.dev/reference/slashcommands#client-set">command line</a>, making it easy for users to get started with their preferred LLM.</p>
<p>For example, to configure <a target="_blank" href="https://docs.waveterm.dev/features/supportedLLMs/ollama">Ollama</a>, simply navigate to the "Settings" menu and set the <em>AI Base UR</em>L to <code>http://localhost:11434/v1</code> and the <em>AI Model</em> to any model you've downloaded using Ollama. In this example, we're using <code>mistral</code>.</p>
<p><img src="https://lh7-us.googleusercontent.com/Rl_65EeLeuPVhqpPM2vrE6ZPT9XUh5N_wEsM2SUs4ziIz6r7oYA8HbTjSbbb82RJh6LGdunW0Lj1BiwUITGCEOX4CEIMBYSN0wj8HAOrxmhtEA4cWqwt4UWCoVg2a-ojyCWtI-NTB0w3I2dx6vyn3Uk" alt /></p>
<p>Once configured, you can start using your LLM in Wave. Simply ask a question using the command box (or use the <a target="_blank" href="https://docs.waveterm.dev/reference/slashcommands#chat">/chat</a> command), such as "<em>How do I build a container from a dockerfile?</em>", and Wave AI will provide an answer using your selected LLM.</p>
<p>The configuration process is similar for all <a target="_blank" href="https://docs.waveterm.dev/features/waveAI#third-party-llm-support-byollm">supported LLM providers</a> but varies slightly. Be sure to check out the detailed documentation for each provider to learn about their specific options and requirements.</p>
<h3 id="heading-getting-started-with-cloud-based-llms">Getting Started with Cloud-based LLM's</h3>
<p>At current, Wave only supports OpenAI API-compatible LLMs. However, if you or your team has an account with OpenAI you can easily <a target="_blank" href="https://docs.waveterm.dev/features/supportedLLMs/openai">configure Wave</a> to use <em>GPT-4</em> (or the newly released <a target="_blank" href="https://openai.com/index/hello-gpt-4o/"><em>GPT-4o</em></a>) and other fine-tuned models for added flexibility, privacy, and to circumnavigate our current rate limit of 200 requests per day.</p>
<p>We’re also currently testing <a target="_blank" href="https://www.perplexity.ai/">Perplexity</a>, as it's an OpenAI-compatible cloud-based model that many users have requested. Make sure you follow our social media (<a target="_blank" href="https://twitter.com/wavetermdev">X</a> and <a target="_blank" href="https://www.linkedin.com/company/wavetermdev">LinkedIn</a>) pages to be notified when we announce its support.</p>
<h3 id="heading-the-future-of-byollm">The Future of BYOLLM</h3>
<p>In the coming weeks and months, we hope to expand our BYOLLM offerings to include support for more commercial cloud-based models like Google's <a target="_blank" href="https://gemini.google.com/?hl=en">Gemini</a>, Anthropic's <a target="_blank" href="https://www.anthropic.com/claude">Claude</a>, and more to ensure that you have access to the latest trends in LLMs, and can tailor your AI experience to your specific needs and concerns.</p>
<p>Lastly, we’re committed to expanding how WaveAI is surfaced in the product to make it more useful. At the moment, Wave AI is limited to the command box and <a target="_blank" href="https://docs.waveterm.dev/reference/slashcommands#chat">/chat</a> command, but we are currently developing more ways to use AI for various tasks like troubleshooting, autocomplete, and much more. We think the terminal has a lot to gain from the latest trends in AI, and are excited to see how it can transform the terminal experience.</p>
<h3 id="heading-wrapping-up">Wrapping Up</h3>
<p>We couldn't be more excited about BYOLLM, and the future of our AI integrations to come. <a target="_blank" href="https://www.waveterm.dev/download">Download Wave</a> today to try our latest integrations and experience the power of BYOLLM firsthand — we can't wait to see what you'll create!</p>
<p>Also, feel free to join the Wave community on <a target="_blank" href="https://discord.gg/XfvZ334gwU">Discord</a> if you need assistance setting up one of these integrations, want to suggest additional LLMs for future inclusion, or simply wish to connect with other Wave users.</p>
]]></content:encoded></item><item><title><![CDATA[Announcing Wave Terminal v0.7.0!]]></title><description><![CDATA[The Wave Terminal team is excited to release Wave Terminal v0.7.0, a significant update designed to enhance your development workflow through comprehensive UI improvements, backend refinements, and a suite of new features. This major release merges o...]]></description><link>https://blog.waveterm.dev/announcing-wave-terminal-v070</link><guid isPermaLink="true">https://blog.waveterm.dev/announcing-wave-terminal-v070</guid><category><![CDATA[terminal]]></category><category><![CDATA[React]]></category><category><![CDATA[Go Language]]></category><category><![CDATA[tools]]></category><category><![CDATA[Linux]]></category><category><![CDATA[macOS]]></category><category><![CDATA[AI]]></category><category><![CDATA[devtools]]></category><category><![CDATA[command line]]></category><category><![CDATA[development]]></category><dc:creator><![CDATA[Knox Lively]]></dc:creator><pubDate>Wed, 13 Mar 2024 21:45:00 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1710548022398/447c6310-0ee8-437b-9713-98c560c6753c.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The Wave Terminal team is excited to release Wave Terminal v0.7.0, a significant update designed to enhance your development workflow through comprehensive UI improvements, backend refinements, and a suite of new features. This major release merges over 100 pull requests and sets the stage for advanced customization options and a more intuitive user experience.</p>
<h3 id="heading-ui-a-fresh-look-and-feel"><strong>UI: A Fresh Look and Feel</strong></h3>
<p>Wave Terminal now sports a new, cleaner, and flatter design, reducing visual clutter and updating colors to enhance focus on your work. With the introduction of a fully collapsible left sidebar and a command input that spans the full width of the terminal, your workspace is now more flexible and distraction-free. We've also added more customizability around your choice of editor settings — namely with the ability to switch between "JetBrains Mono" and "Hack" fonts for the terminal text.</p>
<p><img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1710306633400/e5e56974-7032-4ebb-a01c-1bf0f9b9478f.gif" alt class="image--center mx-auto" /></p>
<p>Lastly, the introduction of a light mode theme offers an alternative to the classic dark mode, catering to different user preferences. Please note that this feature is currently in beta, and our team is diligently working to enhance its stability and performance. We warmly welcome your <a target="_blank" href="https://github.com/wavetermdev/waveterm/issues/new/choose">feedback and suggestions</a> on this and any other themes you'd like to see in future updates.</p>
<h3 id="heading-backend-innovations-smoother-connections-and-updates"><strong>Backend Innovations: Smoother Connections and Updates</strong></h3>
<p>The connections backend has been entirely reworked using Go's standard crypto/ssh library, providing more predictable behavior across systems and resolving numerous connection-related issues. This overhaul simplifies interactions with interactive logins through the use of popups for password entry, OTPs, and other server inputs.</p>
<p>Additionally, Wave now supports optional auto-updates for MacOS and Linux, ensuring you're always working with the latest features and fixes. Linux users will also appreciate the new packages available, including .<em>deb</em>, .<em>rpm</em>, <em>AppImage</em>, and Pacman, making installation and updates smoother than ever. Note that we are also working on packages for <em>yum</em>, <em>aur</em>, and <em>dpkg</em>, so keep your eye out for those soon.</p>
<h3 id="heading-ai-and-code-editing-enhancements"><strong>AI and Code Editing Enhancements</strong></h3>
<p>Additionally, the "Wave AI" panel has received significant updates to improve your interaction with AI-assisted coding. Simply click the "Wave AI" button — (Shortcut: <code>Control + Space</code>) in the command input box to start an interactive session.</p>
<p><img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1710306054238/ca5d1eb6-b254-41cd-9669-f3625ec8fc07.gif" alt class="image--center mx-auto" /></p>
<p>Moreover, recognizing the diverse needs and preferences of our users and adhering to our "open-source first" ethos, we are actively working on integrations for other Large Language Models (LLMs). Whatever your needs are—whether for cutting-edge models, privacy considerations, or ethical reasons—our upcoming integrations will enable you to bring your preferred LLM (BYOLLM) directly to Wave Terminal.</p>
<p>Possible integrations on the horizon include <a target="_blank" href="https://gemini.google.com/?hl=en">Gemini</a>, <a target="_blank" href="https://www.anthropic.com/claude">Claude</a>, and even local LLMs like <a target="_blank" href="https://github.com/openlm-research/open_llama">OpenLLaMA</a> — promising a future where Wave Terminal is your central hub for cutting-edge AI-assisted coding, tailored precisely to your needs and preferences.</p>
<h3 id="heading-noteworthy-bug-fixes"><strong>Noteworthy Bug Fixes</strong></h3>
<p>This release addresses several key issues, improving overall stability and performance. Notable fixes include the resolution of MacOS path reordering (<a target="_blank" href="https://github.com/wavetermdev/waveterm/issues/368">GitHub #368</a>), enhancements to the display of Conda environments (<a target="_blank" href="https://github.com/wavetermdev/waveterm/issues/304">GitHub #304</a>), and a new slash command (<a target="_blank" href="https://github.com/wavetermdev/waveterm/issues/278">GitHub #278</a>) (<code>/reset: CWD</code>) to help when your current working directory is deleted.</p>
<p>Additionally, improvements in command history dropdowns and clearer indications of commands exiting with non-zero exit codes significantly enhance usability.</p>
<div data-node-type="callout">
<div data-node-type="callout-emoji">💡</div>
<div data-node-type="callout-text">For a detailed list of all changes and enhancements, please check out the full release notes <a target="_blank" href="https://docs.waveterm.dev/releasenotes">here</a>.</div>
</div>

<h3 id="heading-looking-ahead"><strong>Looking Ahead</strong></h3>
<p>As we celebrate the release of v0.7.0, we're already looking forward to bringing you customizable themes, full terminal font customization, custom keybindings, and much more in the upcoming v0.7.x series. These forthcoming features, based on your feedback and suggestions, promise to make Wave Terminal even more adaptable to your coding style and preferences.</p>
<h3 id="heading-join-the-wave"><strong>Join the Wave</strong></h3>
<p>We're immensely grateful for the community's feedback and support with this release. Stay tuned for further updates and don't hesitate to share your thoughts with us on <a target="_blank" href="https://discord.gg/XfvZ334gwU">Discord</a> or <a target="_blank" href="https://docs.waveterm.dev/">GitHub</a> and give us a star to show your support for Open Source!</p>
<p><strong>Download Wave:</strong><a target="_blank" href="https://www.waveterm.dev/"><strong>https://www.waveterm.dev</strong></a></p>
]]></content:encoded></item><item><title><![CDATA[Why It’s Time for a Renaissance of The Terminal]]></title><description><![CDATA[Creator of Wave Terminal, Mike Sawka recently chatted about Wave with Rachel Chalmers on Heavybit's Generationship Podcast. The talk focuses on the terminal, how easily it's overlooked, and what's missing from the terminals we use today. Mike also sh...]]></description><link>https://blog.waveterm.dev/terminal-renaissance</link><guid isPermaLink="true">https://blog.waveterm.dev/terminal-renaissance</guid><category><![CDATA[command line]]></category><category><![CDATA[Startups]]></category><category><![CDATA[devtools]]></category><category><![CDATA[AI]]></category><category><![CDATA[#ai-tools]]></category><category><![CDATA[Devops]]></category><dc:creator><![CDATA[Wave Terminal Team]]></dc:creator><pubDate>Tue, 30 Jan 2024 19:19:30 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1706640745124/235e10c5-7732-4ec3-87ff-7cb6c5c6e8a0.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Creator of Wave Terminal, Mike Sawka recently chatted about Wave with Rachel Chalmers on <a target="_blank" href="https://www.heavybit.com/library/podcasts/generationship">Heavybit's Generationship Podcast</a>. The talk focuses on the terminal, how easily it's overlooked, and what's missing from the terminals we use today. Mike also shares insights into the origin story behind Wave, lessons learned from building a company and being persistent with your vision.</p>
<h2 id="heading-the-problems-with-the-terminal">The problems with the Terminal</h2>
<p>When Mike would ask terminal users if they have any problems at first they would say everything was great. But once they stopped to think about it they’d start listing the issues: copy and paste, lots of context switching, command history, disconnections, etc.</p>
<p>There has been little innovation in terminals and Mike puts this down to a "chicken and egg" situation. It comes down to the fact that there is a terminal and a shell and traditionally the terminal was a hardware terminal so all the "smarts" went into the shell. As Mike points out:</p>
<p>"<em>Now if the shell wants to do something new, all the terminals have to support it and if the terminal wants to do something new the shells would need to support it so no one ever made any progress</em>." With Wave, Mike is looking to break that 50 year old "chicken and egg" problem, allowing the terminal to be smart, independent of the shell. He approached it by thinking how a terminal would be designed from scratch with today’s technology.</p>
<h2 id="heading-the-right-ways-ai-can-help-developers-be-productive">The right ways AI can help developers be productive</h2>
<p>If you were to set out to develop a terminal from scratch using today’s technology, AI and specifically the new GenAI technology available today would be powerful additions. "<em>AI is going to be a big enhancement to developers"</em> Mike says and then goes on to elaborate on 2 key aspects of programming where AI can help the most immediately:</p>
<ol>
<li><p>The Mechanical Aspect - help turning thoughts into code quickly or the mechanical transformation of what’s in developers’ heads into code</p>
</li>
<li><p>The Recall Aspect - remembering functions, api functionality, etc. Traditionally senior engineers have been the guardrails for an organization’s best practices and AI can increasingly play a role here.</p>
</li>
</ol>
<p>Programming is alive and well and we need to focus on using AI in the most effective ways, namely:</p>
<ul>
<li><p>Reducing repetitive work</p>
</li>
<li><p>Helping people learn</p>
</li>
<li><p>Increasing institutional knowledge</p>
</li>
</ul>
<h2 id="heading-the-terminal-renaissance">The Terminal Renaissance</h2>
<p>Mike finishes off the podcast sharing his love for Terminals and his vision for the future:</p>
<p><em>“I really want to see a renaissance of the terminal. I really want to see a shift back to the CLI from the web. I think a lot of applications have moved to the web and it is very siloed. What was so great about the terminal was commands could be composed and they could be scripted. If we can bring some of that UI goodness, some of this AI, some of these more interesting concepts to the Terminal we can really see the Terminal take off and be a new remade application.”</em></p>
<p>And of course Mike is rooting for Wave to do this and leading the way with the open source project and community. You can listen to the full podcast here:</p>
<div class="embed-wrapper"><div class="embed-loading"><div class="loadingRow"></div><div class="loadingRow"></div></div><a class="embed-card" href="https://youtu.be/grjVQSoFrWI?feature=shared">https://youtu.be/grjVQSoFrWI?feature=shared</a></div>
<p> </p>
<p>Links:</p>
<ul>
<li><p>Wave Terminal: <a target="_blank" href="https://www.waveterm.dev/">https://www.waveterm.dev/</a></p>
</li>
<li><p>Github Repo: <a target="_blank" href="https://github.com/wavetermdev/waveterm">https://github.com/wavetermdev/waveterm</a></p>
</li>
<li><p>HeavyBit’s GenerationShip Podcast (includes transcript): <a target="_blank" href="https://www.heavybit.com/library/podcasts/generationship/ep-4-reimagining-the-terminal-with-michael-sawka-of-wave-terminal">Ep #4 Reimagining the Terminal</a></p>
</li>
</ul>
]]></content:encoded></item><item><title><![CDATA[Upgrading Command Line History]]></title><description><![CDATA[Command line history revolutionized the way we interact with shells ever since it was added to the original csh shell in 1978 by Bill Joy. History allows us to easily navigate, recall, and reuse previously entered commands. In fact, I can't imagine u...]]></description><link>https://blog.waveterm.dev/upgrading-command-line-history</link><guid isPermaLink="true">https://blog.waveterm.dev/upgrading-command-line-history</guid><category><![CDATA[command line]]></category><category><![CDATA[cli]]></category><category><![CDATA[Open Source]]></category><category><![CDATA[Developer Tools]]></category><dc:creator><![CDATA[Mike Sawka]]></dc:creator><pubDate>Wed, 17 Jan 2024 22:47:38 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/stock/unsplash/npxXWgQ33ZQ/upload/436cd254f3d0c68e9701b5034b083def.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Command line history revolutionized the way we interact with shells ever since it was added to the <a target="_blank" href="https://en.wikipedia.org/wiki/Command_history">original csh shell in 1978 by Bill Joy</a>. History allows us to easily navigate, recall, and reuse previously entered commands. In fact, I can't imagine using the terminal without "Up Arrow", Ctrl-R, and <code>history | grep</code>. Yet, for 45 years, the implementation of history has seen little change, with data still stored in a single flat file in each user's home directory.</p>
<h3 id="heading-the-problem">The Problem</h3>
<p>There are two problems with this approach. The first is that history is segregated by user and machine. The second, is that the current format doesn't allow commands to be associated with rich metadata. To me, it feels obvious that a comprehensive record of every command typed into our terminals — both local and remote — complete with metadata like working directory, user, host, timestamp, command duration, and exit code, should be readily searchable and available at all times.</p>
<h3 id="heading-how-wave-is-solving-it">How Wave is Solving It</h3>
<p>Unified history, with rich metadata, is one of the core features we've built into Wave Terminal. I've been using Wave as my primary terminal for the past year and have over 25k history items (5706 unique commands). I can easily search for commands that were run on my local Macbook, or on remote Linux boxes. I also have all of the history for VMs and Docker instances that have long since been terminated or re-imaged.</p>
<p>Over the past year, this history feature has been a lifesaver. It's helped me recall everything from the steps to create a Mac 'icns' file to the command sequence for manually notarizing a Mac application. It's also invaluable for tasks like identifying the specific packages needed to reinstall a remote Linux box, enabling seamless recreation after termination.</p>
<p>Wave's history feature also works hand-in-hand with another of Wave's core features: persistent tabs. Because each command is indexed to the specific tab in which it was executed, we get a command history for each tab that <em>persists</em>, even across disconnections, terminal restarts, and machine reboots. This means that my AWS deploy commands, executed in their own dedicated tab, are neatly separated from my git commits or local builds, which are run in separate tabs. This separation helps to keep my terminal more organized and efficient.</p>
<h3 id="heading-the-future">The Future</h3>
<p>But there's more to come! Wave's mission is to create a more accessible, batteries included, terminal experience, focused on improving developer experience. We're developing features like more advanced history search, tagging for history items, a straightforward editing function to clear unwanted entries, opt-in AI integration, and options to import and export command sets in an open universal format.</p>
<p>We'd love to hear your thoughts on Wave Terminal. Try it out by downloading the latest version at <a target="_blank" href="https://waveterm.dev/download">https://waveterm.dev/download</a> (available for MacOS and Linux) and share your feedback, report bugs, or suggest features in our <a target="_blank" href="https://discord.gg/XfvZ334gwU">Discord Channel</a> or on <a target="_blank" href="https://github.com/wavetermdev/waveterm">GitHub</a>.</p>
]]></content:encoded></item><item><title><![CDATA[Introducing Wave Terminal]]></title><description><![CDATA[What if your command line terminal could display more than just text? That’s crazy, right (I can hear the screams of thousands of graybeard sysadmins). Well not all the time, but maybe just when you want it to. Like displaying Markdown, Images, or CS...]]></description><link>https://blog.waveterm.dev/introducing-wave-terminal</link><guid isPermaLink="true">https://blog.waveterm.dev/introducing-wave-terminal</guid><category><![CDATA[Developer]]></category><category><![CDATA[command line]]></category><category><![CDATA[cli]]></category><category><![CDATA[Open Source]]></category><category><![CDATA[Developer Tools]]></category><dc:creator><![CDATA[Mike Sawka]]></dc:creator><pubDate>Thu, 11 Jan 2024 18:25:07 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1704997114508/1ad837bf-4442-4ed0-b96c-2435a83e0bea.webp" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>What if your command line terminal could display more than just text? That’s crazy, right (I can hear the screams of thousands of graybeard sysadmins). Well not all the time, but maybe just when you want it to. Like displaying Markdown, Images, or CSVs (that you can actually copy from and paste directly into Excel). Or being able to run an editor, natively, right inline in your terminal that has mouse support, copy/paste, indentation, and syntax highlighting right out of the box for when you need to copy a line or two into your remote .bashrc file?</p>
<p>That’s why we built Wave, to keep what’s best about the command line while adding the power of the open web.</p>
<h3 id="heading-what-is-wave"><strong>What is Wave?</strong></h3>
<p>Wave is a cross-platform open-source terminal that supports inline rendering, modern UI, and persistent sessions. Wave was built to keep what’s best about the command line while adding the power of the open web. Wave has inline renderers for terminal content and remote files to help keep you in flow and reduce context switches. We have 5 initial plugins: remote file editor, markdown viewer, image viewer, CSV viewer, and a ChatGPT interface, with more coming soon.</p>
<p>But Wave isn’t just a simple renderer trick. We’ve been working on Wave for over a year and have over 1200 commits. We’re on a mission to improve terminal DevEx across the board and fix all sorts of terminal micro-frustrations. Wave manages your remote SSH connections, seamlessly restoring sessions, persisting sessions, and giving you a searchable contextual history of all the commands you’ve run, across all of your sessions and remote machines.</p>
<h3 id="heading-what-is-wave-built-on"><strong>What is Wave built on?</strong></h3>
<p>We’re proudly built on Electron (just like VSCode, Slack, and Discord) with all of the network code and heavy lifting done in a local Go backend. This enables us to deliver a consistent cross-platform experience and the ability to leverage high-quality web components for our UI and plugins.What's next?</p>
<h3 id="heading-is-wave-open-source"><strong>Is Wave open-source?</strong></h3>
<p>Openness is a core part of our mission. Our code is open source (Apache 2.0), and our plugins are written in TypeScript/React. We don’t require an email, login, or payment to use our terminal (it is free as in speech and as in beer).</p>
<h3 id="heading-what-platforms-does-wave-work-on"><strong>What platforms does Wave work on?</strong></h3>
<p>Wave works on MacOS as well as Linux (preliminary support). We have a Windows WSL port coming soon.</p>
<h3 id="heading-how-will-wave-make-money"><strong>How will Wave make money?</strong></h3>
<p>We get asked this question a lot! Basic rule of thumb is if it runs on your own computer with your own resources it will be free, if it hits our servers using our resources it will be paid. Yes, we do plan on making money in the future, through opt-in team collaboration features.</p>
<h3 id="heading-what-features-do-you-have"><strong>What features do you have?</strong></h3>
<p>Check out our Wave Terminal demo video to get an overview of our initial features.</p>
<div class="embed-wrapper"><div class="embed-loading"><div class="loadingRow"></div><div class="loadingRow"></div></div><a class="embed-card" href="https://youtu.be/HLX3lwr-6io">https://youtu.be/HLX3lwr-6io</a></div>
<p> </p>
<h3 id="heading-whats-next"><strong>What's Next?</strong></h3>
<p>We're just getting started. If you’re interested, please give it a try and give us a Star on Github to show your support for Open Source! Feedback, bugs, feature requests, and contributions are all welcome. Happy Hacking!</p>
<p><a target="_blank" href="https://www.waveterm.dev/">https://www.waveterm.dev</a> | <a target="_blank" href="https://www.waveterm.dev/">https://github.com/wavetermdev/waveterm</a></p>
]]></content:encoded></item></channel></rss>