TopFreeAlternative

- Free open source alternatives of paid software.

Paid software

Free open source alternatives for Linux

Browse free and open source software that runs on Linux. Find open-source alternatives, compare features, platforms and pricing, and pick the right Linux tool for you.

godot logo
godot is a free, open-source alternative to Unity . Godot Engine 2D and 3D cross-platform game engine Godot Engine is a feature-packed, cross-platform game engine to create 2D and 3D games from a unified interface. It provides a comprehensive set of common tools , so that users can focus on making games without having to reinvent the wheel. Games can be exported with one click to a number of platforms, including the major desktop platforms (Linux, macOS, Windows), mobile platforms (Android, iOS), as well as Web-based platforms and consoles . Free, open source and community-driven Godot is completely free and open source under the very permissive MIT license . No strings attached, no royalties, nothing. The users' games are theirs, down to the last line of engine code. Godot's development is fully independent and community-driven, empowering users to help shape their engine to match their expectations. It is supported by the Godot Foundation not-for-profit. Before being open sourced in February 2014 , Godot had been developed by Juan Linietsky and Ariel Manzur for several years as an in-house engine, used to publish several work-for-hire titles. Getting the engine Binary downloads Official binaries for the Godot editor and the export templates can be found on the Godot website . Compiling from source See the official docs for compilation instructions for every supported platform. Community and contributing Godot is not only an engine but an ever-growing community of users and engine developers. The main community channels are listed on the homepage . The best way to get in touch with the core engine developers is to join the Godot Contributors Chat . To get started contributing to the project, see the contributing guide . This document also includes guidelines for reporting bugs. Documentation and demos The official documentation is hosted on Read the Docs . It is maintained by the Godot community in its own GitHub repository . The class reference is also accessible from the Godot editor. We also maintain official demos in their own GitHub repository as well as a list of awesome Godot community resources . There are also a number of other learning resources provided by the community, such as text and video tutorials, demos, etc. Consult the community channels for more information.
FreeWindowsmacOSLinux
openscreen logo
openscreen is a free, open-source alternative to Screen Studio . Note OpenScreen is now archived and no longer maintained. For continued maintenance and development, a community-driven spin-off led by one of the core contributors is available here: https://github.com/EtienneLescot/openscreen Warning This started as a side project that blew up; not production grade and you'll hit bugs, but hopefully it covers what you need. This project will soon be archived. OpenScreen OpenScreen is your free, open-source alternative to Screen Studio. If you don't want to pay $29/month for Screen Studio but want a version that does what most people seem to need - quick, polished product demos and walkthroughs you'd post on X, Reddit or Youtube. OpenScreen does not offer every Screen Studio feature, but covers a lot of the core functionality. Screen Studio is an awesome product and this is definitely not a 1:1 clone. If you just want something fully free and open source, this project should cover most of your needs. 100% free for both personal and commercial use. Use it, modify it, distribute it. Please respect the License. Note Software should be accessible. OpenScreen has no paid tiers, premium features, upsells, or functionality locked behind a paywall. Core Features Record a specific window, or your whole screen. Record microphone and system audio. Webcam overlay with picture-in-picture, drag-to-position, mirroring, and shape options. Auto or manual zooms with adjustable depth, duration, easing, and pixel-precise position; auto-zoom follows your cursor as you work. Custom cursor size, smoothing, and click effects, with cursor themes and post-recording path smoothing. Automatic captions for voiceovers, generated on-device with no upload (works offline). Wallpapers, solid colors, gradients, or your own background image. Motion blur. Crop, trim, and per-segment speed control on the timeline. Text, arrow, and image annotations, with text animation presets. Timeline snapping guides and an audio waveform to make trimming easier. Customizable keyboard shortcuts. Export to MP4 or GIF in multiple aspect ratios and resolutions. Languages supported: Arabic, English, Spanish, French, Italian, Japanese, Korean, Portuguese (Brazil), Russian, Turkish, Vietnamese, Simplified Chinese, and Traditional Chinese. Installation Download the latest installer for your platform from the GitHub Releases page. macOS The easiest way to install on macOS is via Homebrew : brew install --cask siddharthvaddem/openscreen/openscreen Brew automatically picks the right build for Apple Silicon or Intel, and verifies the download against a notarized signature so Gatekeeper won't block it. To update later: brew upgrade --cask openscreen To uninstall: brew uninstall --cask openscreen (add --zap to also remove app data) Manual install (if you prefer) If you'd rather grab the .dmg directly from the Releases page and encounter Gatekeeper blocking the app, you can bypass it by running the following command in your terminal after installation: xattr -rd com.apple.quarantine /Applications/Openscreen.app Note: Give your terminal Full Disk Access in System Settings > Privacy & Security to grant you access and then run the above command. After running this command, proceed to System Preferences > Security & Privacy to grant the necessary permissions for "screen recording" and "accessibility". Once permissions are granted, you can launch the app. Note Upgrading from an older version and hitting permission issues? If you already had OpenScreen installed and the new version won't record (Screen Recording or Accessibility keep failing even after you grant them), uninstall the old version, remove OpenScreen's existing entries under System Settings > Privacy & Security (both Screen Recording and Accessibility), then do a fresh install and grant the permissions again when prompted. Windows Install via winget : winget install SiddharthVaddem.OpenScreen To update later: winget upgrade SiddharthVaddem.OpenScreen To uninstall: winget uninstall SiddharthVaddem.OpenScreen If you'd rather grab the .exe installer directly, download it from the Releases page . Linux Three packages are published to the Releases page for each version. Pick the one that matches your distro: Debian / Ubuntu / Pop!_OS ( .deb ) sudo apt install ./Openscreen-Linux-latest.deb Arch / Manjaro ( .pacman ) sudo pacman -U Openscreen-Linux-latest.pacman Any distro ( .AppImage ) chmod +x Openscreen-Linux- * .AppImage ./Openscreen-Linux- * .AppImage NixOS / Nix (flake) Try without installing: nix run github:siddharthvaddem/openscreen Install into your user profile: nix profile install github:siddharthvaddem/openscreen For a NixOS system config (flake): { inputs . openscreen . url = "github:siddharthvaddem/openscreen" ; outputs = { nixpkgs , openscreen , ... } : { nixosConfigurations . < host > = nixpkgs . lib . nixosSystem { modules = [ openscreen . nixosModules . default { programs . openscreen . enable = true ; } ] ; } ; } ; } For Home Manager, use openscreen.homeManagerModules.default with the same programs.openscreen.enable = true; . You may need to grant screen recording permissions depending on your desktop environment. Sandbox error: If the AppImage fails to launch with a "sandbox" error, run it with --no-sandbox : ./Openscreen-Linux- * .AppImage --no-sandbox Platform differences Everything in the editor and export is the same on macOS, Windows, and Linux: zooms, backgrounds, motion blur, crop/trim/speed, blur regions, annotations, auto-captions, projects, export, and all languages. The differences are in capture , where macOS and Windows use a native pipeline that Linux doesn't have: Native recording : macOS (ScreenCaptureKit) and Windows (Windows Graphics Capture) record through a native pipeline for higher quality and clean window-level capture. Linux records through the browser pipeline instead. Custom cursors : on macOS and Windows the real cursor is captured (shape, type, and clicks), which powers the cursor themes, click effects, and editable cursor overlay. On Linux only the cursor position is captured (used for auto-zoom), so those cursor options aren't available. Webcam : captured natively on macOS and Windows; on Linux it's recorded through the browser, but still works as a picture-in-picture overlay. System audio support varies by OS: macOS : requires macOS 13+. On macOS 14.2+ you'll be prompted to grant audio capture permission. macOS 12 and below can't capture system audio (mic still works). Windows : works out of the box. Linux : needs PipeWire (default on Ubuntu 22.04+, Fedora 34+). Older PulseAudio-only setups may not capture system audio (mic should still work). License This project is licensed under the MIT License . By using this software, you agree that the authors are not liable for any issues, damages, or claims arising from its use.
FreeWindowsmacOSLinux
Redis Insight logo
Redis Insight is a visual tool that provides capabilities to design, develop, and optimize your Redis application. Query, analyse and interact with your Redis data. Redis Insight is an intuitive and efficient GUI for Redis, allowing you to interact with your databases and manage your data—with built-in support for Redis modules. Redis Insight Highlights: Browse, filter, visualise your key-value Redis data structures and see key values in different formats (including JSON, Hex, ASCII, etc.) CRUD support for lists, hashes, strings, sets, sorted sets, and streams CRUD support for JSON data structure Interactive tutorials to learn easily, among other things, how to leverage the native JSON data structure supporting structured querying and full-text search, including vector similarity search for your AI use cases Contextualised recommendations to optimize performance and memory usage. The list of recommendations gets updated as you interact with your database Profiler - analyze every command sent to Redis in real-time SlowLog - analyze slow operations in Redis instances based on the Slowlog command Pub/Sub - support for Redis pub/sub , enabling subscription to channels and posting messages to channels Bulk actions - Delete the keys in bulk based on the filters set in Browser or Tree view Workbench - advanced command line interface with intelligent command auto-complete, complex data visualizations and support for the raw mode Command auto-complete support for search and query capability, JSON and time series data structures Visualizations of your search and query indexes and results. Ability to build your own data visualization plugins Officially supported for Redis OSS, Redis Cloud . Works with Microsoft Azure Cache for Redis
FreeWindowsmacOSLinux
CodeWhale logo
CodeWhale is a free, open-source alternative to Claude Code . Codewhale Codewhale is an open source coding agent for your terminal, built in Rust and improved in public with the people who use it. 简体中文 · 日本語 · Tiếng Việt · Bahasa Indonesia · 한국어 · Español · Português · Русский · Українська · Français · Deutsch · 繁體中文 · हिन्दी · Türkçe · Italiano · Polski · العربية · Català Install npm install -g codewhale codewhale The first run helps you connect a provider or stay offline. Codewhale also supports Cargo, Docker, Nix, Scoop, prebuilt archives, Android/Termux, and a CNB mirror. See the installation guide . Use Talk to Codewhale the same way you would talk to a teammate: Fix the failing tests and explain what changed. Or run a task without opening the TUI: codewhale exec " fix the failing tests and explain what changed " Codewhale can read your repository, edit files, run commands, inspect results, and keep working toward a goal. You decide how much access it has. Why Codewhale Use the model you want. Connect hosted providers or local models through Ollama, vLLM, or SGLang. Switch provider and model with /model . Stay in control. Plan is read-only. Ask, Auto-Review, and Full Access make approval behavior visible. /undo reverts the last turn and /restore returns the workspace to an earlier snapshot. Keep long work organized. Save sessions, set a durable /goal , review workflows before they run, and coordinate agents without turning their internal instructions into your transcript. Extend the agent you already have. Connect MCP servers and skills, configure hooks, and keep agent roles as readable files in your project or personal settings. Run /help in the TUI for commands and keyboard shortcuts. Safety Codewhale runs on your machine with the access you grant it. Approval modes and repository rules limit what the agent may do; optional OS sandboxing adds a stronger execution boundary where supported. Unknown model prices stay unknown instead of being reported as free. Read authorization order for the exact policy stack and configuration for local settings. Documentation Providers and local models Agent teams MCP , hooks , and configuration Local web client All documentation Join the community Codewhale gets better when people use it, report what feels wrong, and help fix it. If a provider is missing, a workflow is awkward, or the terminal UI gets in your way, open an issue . If you know how to improve it, open a pull request . First contributions are welcome, and contributors keep credit for the work that lands. Join the Discord , or add Hunter on WeChat ( hunterbown ) and ask to join the Whale Brothers group. Project history Codewhale began as deepseek-tui and still preserves that configuration and session compatibility. It is now provider-neutral and independently maintained; it is not affiliated with any model provider. Thanks to every contributor and to the open source communities that helped the project grow. See the contributor record . License MIT
FreeWindowsmacOSLinux
rtk logo
rtk is a free, open-source software / service you can self-host or use without paying. High-performance CLI proxy that cuts up to 90% of the bash output your agent reads Website • Install • Troubleshooting • Architecture • Discord English • Francais • 中文 • 日本語 • 한국어 • Espanol • Português rtk filters and compresses command outputs before they reach your LLM context. Single Rust binary, 100+ supported commands, <10ms overhead. What RTK Does RTK intercepts shell commands and compresses their output before your agent reads it. Operation What RTK does to the output ls / tree Tree format with file counts instead of one line per entry cat / read Smart file reading: signatures and structure over full bodies grep / rg Truncates long lines, groups matches by file git status Compact stat format, grouped by state git diff Reduced context, headers stripped git log Hash, author and subject only git add/commit/push Confirmation line instead of full progress output cargo test / npm test Failures only, passing tests collapsed to a count ruff check Grouped by rule and file pytest Failures only, traceback trimmed go test NDJSON parsed, failures only docker ps Essential fields only How Savings Work RTK cuts up to 90% of the bash output your agent reads. That is what RTK measures, and it is not the same as cutting your bill by 90%. Bash output is one contributor to input tokens , alongside your prompt, the system prompt and conversation history. Input tokens are in turn only part of the bill , which also counts output tokens. The reduction dilutes at every step. The token counts RTK reports are estimated as bytes / 4 — RTK ships no tokenizer, so the percentages are reliable but the absolute token numbers are approximate . Full explanation: How RTK Savings Work Installation Homebrew (recommended) brew install rtk Quick Install (Linux/macOS) curl -fsSL https://raw.githubusercontent.com/rtk-ai/rtk/refs/heads/master/install.sh | sh Installs to ~/.local/bin . Add to PATH if needed: echo ' export PATH="$HOME/.local/bin:$PATH" ' >> ~ /.bashrc # or ~/.zshrc Cargo cargo install --git https://github.com/rtk-ai/rtk Pre-built Binaries Download from releases : macOS: rtk-x86_64-apple-darwin.tar.gz / rtk-aarch64-apple-darwin.tar.gz Linux: rtk-x86_64-unknown-linux-musl.tar.gz / rtk-aarch64-unknown-linux-gnu.tar.gz Windows: rtk-x86_64-pc-windows-msvc.zip Windows users : Extract the zip and place rtk.exe somewhere in your PATH (e.g. C:\Users\<you>\.local\bin ). Run RTK from Command Prompt , PowerShell , or Windows Terminal — do not double-click the .exe (it will flash and close). The full hook system works natively on Windows (and in WSL ). See Windows setup below for details. Verify Installation rtk --version # Should show "rtk 0.28.2" rtk gain # Should show the savings dashboard Name collision warning : Another project named "rtk" (Rust Type Kit) exists on crates.io. If rtk gain fails, you have the wrong package. Use cargo install --git above instead. Quick Start # 1. Install for your AI tool rtk init -g # Claude Code / Copilot (default) rtk init -g --gemini # Gemini CLI rtk init -g --codex # Codex (OpenAI) rtk init -g --agent cursor # Cursor rtk init -g --agent windsurf # Windsurf rtk init --agent cline # Cline / Roo Code rtk init --agent kilocode # Kilo Code rtk init --agent antigravity # Google Antigravity rtk init --agent kimi # Kimi AI rtk init -g --agent pi # Pi rtk init --agent hermes # Hermes rtk init -g --agent droid # Factory Droid # 2. Restart your AI tool, then test git status # Automatically rewritten to rtk git status Hook-based agents rewrite Bash commands (e.g., git status -> rtk git status ) before execution. Plugin-based agents, including Hermes, use their plugin API to rewrite commands before execution. The agent receives compact output without needing to call rtk explicitly. Important: the hook only runs on Bash tool calls. Claude Code built-in tools like Read , Grep , and Glob do not pass through the Bash hook, so they are not auto-rewritten. To get RTK's compact output for those workflows, use shell commands ( cat / head / tail , rg / grep , find ) or call rtk read , rtk grep , or rtk find directly. How It Works Without rtk: With rtk: Claude --git status--> shell --> git Claude --git status--> RTK --> git ^ | ^ | | | full raw output | | compact output | filter | +-----------------------------------+ +------- (filtered) ---+----------+ Four strategies applied per command type: Smart Filtering - Removes noise (comments, whitespace, boilerplate) Grouping - Aggregates similar items (files by directory, errors by type) Truncation - Keeps relevant context, cuts redundancy Deduplication - Collapses repeated log lines with counts Commands Percentages below are reductions in bash output , not reductions in your bill. See How Savings Work . Files rtk ls . # Compact directory tree rtk read file.rs # Smart file reading rtk read file.rs -l aggressive # Signatures only (strips bodies) rtk smart file.rs # 2-line heuristic code summary rtk find " *.rs " . # Compact find results rtk grep " pattern " . # Grouped search results rtk diff file1 file2 # Condensed diff (exit 1 if files differ) Git rtk git status # Compact status rtk git log -n 10 # One-line commits rtk git diff # Condensed diff rtk git add # -> "ok" rtk git commit -m " msg " # -> "ok abc1234" rtk git push # -> "ok main" rtk git pull # -> "ok 3 files +10 -2" GitHub CLI rtk gh pr list # Compact PR listing rtk gh pr view 42 # PR details + checks rtk gh issue list # Compact issue listing rtk gh run list # Workflow run status Test Runners rtk jest # Jest compact (failures only) rtk vitest # Vitest compact (failures only) rtk playwright test # E2E results (failures only) rtk pytest # Python tests (-90%) rtk go test # Go tests (NDJSON, -90%) rtk cargo test # Cargo tests (-90%) rtk rake test # Ruby minitest (-90%) rtk rspec # RSpec tests (JSON, -60%+) rtk err < cmd > # Filter errors only from any command rtk test < cmd > # Generic test wrapper - failures only (-90%) Build & Lint rtk lint # ESLint grouped by rule/file rtk lint biome # Supports other linters rtk tsc # TypeScript errors grouped by file rtk next build # Next.js build compact rtk prettier --check . # Files needing formatting rtk cargo build # Cargo build (-80%) rtk cargo clippy # Cargo clippy (-80%) rtk ruff check # Python linting (JSON, -80%) rtk golangci-lint run # Go linting (JSON, -85%) rtk rubocop # Ruby linting (JSON, -60%+) rtk sbt test # ScalaTest output (-90%) rtk sbt compile # Compilation errors only (-75%) rtk sbt run # Strip SBT preamble noise Package Managers rtk pnpm list # Compact dependency tree rtk uv run pytest # Preserve uv env, keep program output rtk pip list # Python packages (auto-detect uv) rtk pip outdated # Outdated packages rtk bundle install # Ruby gems (strip Using lines) rtk prisma generate # Schema generation (no ASCII art) AWS rtk aws sts get-caller-identity # One-line identity rtk aws ec2 describe-instances # Compact instance list rtk aws lambda list-functions # Name/runtime/memory (strips secrets) rtk aws logs get-log-events # Timestamped messages only rtk aws cloudformation describe-stack-events # Failures first rtk aws dynamodb scan # Unwraps type annotations rtk aws iam list-roles # Strips policy documents rtk aws s3 ls # Truncated with tee recovery Containers rtk docker ps # Compact container list rtk docker images # Compact image list rtk docker logs < container > # Deduplicated logs rtk docker compose ps # Compose services rtk kubectl pods # Compact pod list rtk kubectl logs < pod > # Deduplicated logs rtk kubectl services # Compact service list rtk oc get pods # OpenShift pod summary rtk oc get services # OpenShift service list rtk oc logs < pod > # Deduplicated logs Infrastructure as Code rtk pulumi preview # Strip header/URL/duration noise rtk pulumi up # Compact apply output rtk pulumi destroy # Compact destroy output rtk pulumi refresh # Drift summary rtk pulumi stack # Stack metadata (strips owner/timestamps) Data & Analytics rtk json config.json # Structure without values rtk deps # Dependencies summary rtk env -f AWS # Filtered env vars rtk log app.log # Deduplicated logs rtk curl < url > # Truncate + save full output rtk wget < url > # Download, strip progress bars rtk summary < long command > # Heuristic summary rtk proxy < command > # Raw passthrough + tracking Token Savings Analytics rtk gain # Summary stats rtk gain --graph # ASCII graph (last 30 days) rtk gain --history # Recent command history rtk gain --daily # Day-by-day breakdown rtk gain --all --format json # JSON export for dashboards rtk discover # Find missed savings opportunities rtk discover --all --since 7 # All projects, last 7 days rtk session # Show RTK adoption across recent sessions Global Flags -u, --ultra-compact # ASCII icons, inline format (further output reduction) -v, --verbose # Increase verbosity (-v, -vv, -vvv) Examples Directory listing: # ls -la (45 lines) # rtk ls (12 lines) drwxr-xr-x 15 user staff 480 ... my-project/ -rw-r--r-- 1 user staff 1234 ... +-- src/ (8 files) ... | +-- main.rs +-- Cargo.toml Git operations: # git push (15 lines) # rtk git push (1 line) Enumerating objects: 5, done. ok main Counting objects: 100% (5/5), done. Delta compression using up to 8 threads ... Test output: # cargo test (200+ lines on failure) # rtk test cargo test (~20 lines) running 15 tests FAILED: 2/15 tests test utils::test_parse ... ok test_edge_case: assertion failed test utils::test_format ... ok test_overflow: panic at utils.rs:18 ... Auto-Rewrite Hook The most effective way to use rtk. The hook transparently intercepts Bash commands and rewrites them to rtk equivalents before execution. Result : 100% rtk adoption across all conversations and subagents, with no per-command context overhead. Scope note: this only applies to Bash tool calls. Claude Code built-in tools such as Read , Grep , and Glob bypass the hook, so use shell commands or explicit rtk commands when you want RTK filtering there. Setup rtk init -g # Install hook + RTK.md (recommended) rtk init -g --opencode # OpenCode plugin (instead of Claude Code) rtk init -g --auto-patch # Non-interactive (CI/CD) rtk init -g --hook-only # Hook only, no RTK.md rtk init --show # Verify installation After install, restart Claude Code . Windows RTK works fully on native Windows. Since v0.37.2 the auto-rewrite hook runs as a native binary command ( rtk hook claude ) — no Unix shell, bash, or jq required — so commands are rewritten transparently on Command Prompt, PowerShell, and Windows Terminal, just like on Linux and macOS. Native Windows # 1. Download and extract rtk-x86_64-pc-windows-msvc.zip from releases # 2. Add rtk.exe to your PATH (e.g. C:\Users\<you>\.local\bin) # 3. Initialize — installs the native binary hook rtk init - g Upgrading from an older install? If you set RTK up before v0.37.2 you may still have the legacy rtk-rewrite.sh shell hook (which does need a Unix shell). Re-run rtk init -g to migrate to the native binary hook. Prerequisites : some filters shell out to ripgrep ( rg ). Install it and keep it on your PATH (e.g. winget install BurntSushi.ripgrep.MSVC ) to avoid Binary 'rg' not found on PATH warnings. Important : Do not double-click rtk.exe — it is a CLI tool that prints usage and exits immediately. Always run it from a terminal (Command Prompt, PowerShell, or Windows Terminal). WSL WSL also works and behaves exactly like Linux: # Inside WSL curl -fsSL https://raw.githubusercontent.com/rtk-ai/rtk/refs/heads/master/install.sh | sh rtk init -g Feature Native Windows WSL Filters (cargo, git, etc.) Full Full Auto-rewrite hook Yes (native binary) Yes rtk init -g Hook mode Hook mode rtk gain / analytics Full Full Supported AI Tools RTK supports 16 AI coding tools. Each integration rewrites shell commands to rtk equivalents, reducing the bash output the agent reads where the agent supports command interception. Tool Install Method Claude Code rtk init -g PreToolUse hook (native binary) GitHub Copilot (VS Code) rtk init -g --copilot PreToolUse hook — transparent rewrite GitHub Copilot CLI rtk init -g --copilot PreToolUse deny-with-suggestion (CLI limitation) Cursor rtk init -g --agent cursor preToolUse hook (hooks.json) Gemini CLI rtk init -g --gemini BeforeTool hook Codex rtk init -g --codex AGENTS.md + RTK.md instructions Windsurf rtk init -g --agent windsurf .windsurfrules (project-scoped) Cline / Roo Code rtk init --agent cline .clinerules (project-scoped) OpenCode rtk init -g --opencode Plugin TS (tool.execute.before) OpenClaw openclaw plugins install ./openclaw Plugin TS (before_tool_call) Pi rtk init -g --agent pi (global) TypeScript extension (tool_call) Hermes rtk init --agent hermes Python plugin adapter (terminal command mutation via rtk rewrite ) Mistral Vibe rtk init -g --agent vibe pre_tool hook (hooks.toml) Kilo Code rtk init --agent kilocode .kilocode/rules/rtk-rules.md (project-scoped) Google Antigravity rtk init --agent antigravity .agents/rules/antigravity-rtk-rules.md (project-scoped) Kimi AI rtk init --agent kimi AGENTS.md (project-scoped) Factory Droid rtk init -g --agent droid (or per-project) PreToolUse hook in ~/.factory/hooks.json (matcher Execute ) For per-agent setup details, override controls, and graceful degradation, see the Supported Agents guide . The Hermes plugin source and tests live in hooks/hermes/ ; installed Hermes runtime files still live under ~/.hermes/plugins/rtk-rewrite/ . Configuration ~/.config/rtk/config.toml (macOS: ~/Library/Application Support/rtk/config.toml ): [ hooks ] exclude_commands = [ " curl " , " playwright " ] # skip rewrite for these [ tee ] enabled = true # save raw output on failure (default: true) mode = " failures " # "failures", "always", or "never" When a command fails, RTK saves the full unfiltered output so the LLM can read it without re-executing: FAILED: 2/15 tests [full output: ~/.local/share/rtk/tee/1707753600_cargo_test.log] For the full config reference (all sections, env vars, per-project filters), see the Configuration guide . Uninstall rtk init -g --uninstall # Remove hook, RTK.md, settings.json entry cargo uninstall rtk # Remove binary brew uninstall rtk # If installed via Homebrew Documentation rtk-ai.app/guide — full user guide (installation, supported agents, what gets optimized, analytics, configuration, troubleshooting) INSTALL.md — detailed installation reference ARCHITECTURE.md — system design and technical decisions CONTRIBUTING.md — contribution guide SECURITY.md — security policy Privacy & Telemetry RTK can collect anonymous, aggregate usage metrics once per day. Telemetry is disabled by default and requires explicit opt-in consent (GDPR Art. 6, 7) during rtk init or via rtk telemetry enable . This data helps us build a better product: identifying which commands need filters, which filters need improvement, and how much value RTK delivers. For the full list of fields, data handling, and contributor guidelines, see docs/TELEMETRY.md . What is collected and why: Category Data Why Identity Salted device hash (SHA-256, not reversible) Count unique installations without tracking individuals Environment RTK version, OS, architecture, install method Know which platforms to support and test Usage volume Command count (24h), total commands, estimated tokens saved (24h/30d/total) Measure adoption and value delivered Quality Top 5 passthrough commands (0% reduction), parse failure count, commands with <30% reduction Identify missing filters and weak ones to improve Ecosystem Command category distribution (e.g. git 45%, cargo 20%, js 15%) Prioritize filter development for popular ecosystems Retention Days since first use, active days in last 30 Understand engagement and detect churn Adoption AI agent hook type (claude/gemini/codex), custom TOML filter count Track integration coverage and DSL adoption Configuration Whether config.toml exists, number of excluded commands, project count Understand user maturity and customization patterns Features Usage counts for meta-commands (gain, discover, proxy, verify) Know which RTK features are valued vs unused Economics Estimated USD value, derived from the estimated tokens saved and a fixed internal constant Quantify the value RTK provides to users All data is aggregate counts or anonymized command names (first 3 words, no arguments). Top commands report only tool names (e.g. "git", "cargo"), never full command lines. What is NOT collected: source code, file paths, command arguments, secrets, environment variables, personal data, or repository contents. Manage telemetry: rtk telemetry status # Check current consent state rtk telemetry enable # Give consent (interactive prompt) rtk telemetry disable # Withdraw consent — stops all collection immediately rtk telemetry forget # Withdraw consent + delete all local data + request server-side erasure Override via environment: export RTK_TELEMETRY_DISABLED=1 # Blocks telemetry regardless of consent Star History StarMapper Core team Patrick Szymkowiak — Founder GitHub · LinkedIn Florian Bruniaux — Core contributor GitHub · LinkedIn Adrien Eppling — Core contributor GitHub · LinkedIn Nicolas Le Cam — Core contributor Github · LinkedIn Takayuki Maeda — Core contributor GitHub · LinkedIn Contributing Contributions welcome! Please open an issue or PR on GitHub . Join the community on Discord . License Apache License 2.0 - see LICENSE for details. Disclaimer See DISCLAIMER.md .
FreeWindowsmacOSLinux

Explore more categories: