A blazing fast, Rust-based CLI tool to organize temporary projects and experiments with a rich terminal interface.
try-rs is a command-line workspace manager built in Rust that helps developers organize their temporary coding projects and experiments. It solves the problem of cluttered directories by automatically creating date-prefixed folders and providing a fast, feature-rich terminal interface to manage them. The tool includes fuzzy search, Git integration, and a configurable TUI to streamline the workflow for experimental code.
Developers and engineers who frequently create temporary projects, prototypes, or experiments and want a structured, fast way to manage them from the terminal. It's especially useful for those using multiple shells and operating systems.
Developers choose try-rs for its exceptional speed due to Rust, its rich TUI with features like fuzzy search and previews, and its deep integration with Git and shell environments. It offers a more organized and efficient alternative to manual folder management in /tmp or Desktop.
A blazing fast, Rust-based workspace manager for your temporary experiments.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Built in Rust and compiled to a native binary, ensuring zero interpreter lag as emphasized in the README's feature list.
Offers a beautiful TUI with fuzzy search, content previews, and tabbed workspaces using Ratatui, making navigation intuitive and efficient.
Automatically clones repositories from URLs and marks them with icons, streamlining the setup for experimental code from Git.
Supports multiple themes, configurable panel layouts, and shell-specific integrations via a TOML config file, allowing extensive customization.
Works on Linux, macOS, and Windows with support for Fish, Zsh, Bash, PowerShell, and Nushell, as detailed in the installation section.
Requires a Nerd Font for icons to display correctly, which is an extra installation step and may not be available in all environments.
Setup involves running shell-specific commands and potentially editing config files, which can be complex for users unfamiliar with terminal customization.
Purely terminal-based, lacking a graphical interface, which might limit accessibility for users who prefer mouse-driven workflows.
Editor integration depends on external editors being properly set up via config or environment variables, and may not work out-of-the-box for all editors.