Skip to case study

Athas code editor

Open-source contributor, 2025–2026

My role
Contributor, 9 merged pull requests
Stack
Rust, Tauri, React, TypeScript, LSP, SSH
Project
Open-source code editor

I have nine merged pull requests in Athas. They touch its React and TypeScript interface, its Tauri and Rust desktop core, the remote tooling, the language-server integration, and how the editor handles large files.

Scope

Features and reliability fixes

My changes are spread over several parts of the editor: language support, how the editor UI behaves, remote connections, resource cleanup, how language servers are started and stopped, large files, and input from untrusted sources. All of it runs in a desktop app that has to work on more than one platform.

Merged work

Features, fixes, and maintenance

  • Made the editor, the language servers, and the terminal stream large files instead of loading them whole, and sped up scrolling and tokenizing. This is my largest change: 63 files and about 4,400 added lines.
  • Hardened untrusted input: agent file and terminal access stays inside the workspace, language-server and debugger messages have size limits, and credentials stay out of connection strings and git errors.
  • Added C# language support, and image diffs with zoom for git.
  • Fixed how the menu bar behaves on Linux and made the interface more consistent across platforms.
  • Replaced a hard-coded proxy port with dynamic port selection.
  • Closed SSH and SFTP resource leaks and fixed memory leaks in React components.
  • Fixed a race condition that could start the same language server twice.

Engineering

Fixes that keep a session stable

  • Language server lifecycleThe LSP fix stops duplicate server processes from starting and fighting over editor state.
  • Resource ownershipSSH and SFTP handles get closed explicitly instead of leaking from one remote session into the next.
  • Cross-platform behaviorThe Linux-specific UI changes still match how the rest of the desktop app looks and behaves.
  • Large filesOpening a big file no longer pushes the whole file through the editor, the language server, and the terminal at once.

Open source

Working inside an existing project

In a project someone else maintains, a change has to fit the architecture that's already there and get through review and CI, and not every feature someone proposes belongs in the product. That's why I point to merged work: those are the changes that actually became part of the shared codebase.