# Coding tools · OmniGet Docs - URL: https://getomniget.com/docs/cli-tools - Updated: 2026-10-02 - OmniGet 1.0.0 > Free, open-source yt-dlp GUI for Windows, macOS and Linux. Paste a link to save video, audio and files from 1,000+ sites, or run AI coding agents. --- AI agents # Coding tools The **Tools** tab of LLM knows 34 AI coding tools, from Claude Code, Codex, Gemini CLI and OpenCode to Cursor Agent, GitHub Copilot CLI and Aider. It finds the ones already installed, shows their version, and lets you install, update, sign in to and check each one, always showing the exact command before it runs. ## Where it is **LLM › Tools**. The first-run screen also scans for these tools ([First launch](https://getomniget.com/docs/onboarding)); if it finds none, it tells you to come back here. ## What it detects Most entries are command-line tools; a few are desktop apps or both. Each card shows a tag for the kind (**CLI**, **App** or **CLI + app**) and the project status (**Active**, **Maintenance** or **Discontinued**). The list includes, among others: Claude Code, Codex CLI, Gemini CLI, Qwen Code, OpenCode, Kilo Code CLI, Crush, Cursor Agent, GitHub Copilot CLI, Cline CLI, Continue CLI (cn), goose, Zed, Factory Droid, Kimi Code, Amp, Aider, Junie, Kiro CLI, Warp, Mistral Vibe, Letta Code and OpenHands CLI. For each tool, the card shows: - **Installed**: the version found, or **Not installed**. - **Latest**: the newest published version, tagged **update available** or **up to date**. - **Installed by**: how the copy on your computer was installed (for example npm, Homebrew, pip or the tool’s own installer), with its **Path** and **Real path**. ## How to use it ### Install or update a tool 1. Find the tool with **Search**, or narrow the list with **All**, **Installed**, **Available** or **Legacy**. 2. Click **Install** (or **Update** when a newer version exists). 3. Read the **Command plan**. It lists the install methods for your system, with one marked **recommended**. 4. Click **Run**. The output appears live in the **Log** below. Note Updates only run against a copy whose installer OmniGet could prove, so it does not overwrite a tool that another package manager owns. ### Sign in Click **Sign in**. OmniGet opens a terminal with the tool’s own login command (**Terminal opened: …**). If you have more than one account for that tool, it first asks **Sign in on which instance?**. You sign in with the tool’s provider, under that provider’s terms; OmniGet does not see your password. ### Diagnose a tool Click **Diagnose** to check the install, the latest version, the sign-in state, and the tool’s configuration and log folders. **Nothing to fix.** means the check passed. OmniGet only checks that credential files exist; it never opens them. ### Check a tool’s configuration Click **Configuration** on an installed tool to open **Config health**: - **Scan installed** reads what is set up for that tool (agents, commands, skills, hooks, MCP servers and settings) and checks it with the same validators as the [Catalog](https://getomniget.com/docs/catalog). - **Weight and structure** shows the files found and their size. - **Optimize with an agent** starts a [task](https://getomniget.com/docs/work) that reviews those files and proposes a leaner configuration. Nothing is changed without you. Choose **Global only** or **Choose folder…** to include a project’s own configuration. ### Check for updates **Check updates** at the top compares every installed tool with its latest release. Tools with a new version get **Update available** and a **What changed** summary with a link to the **Full release notes**. ## ACP agents The **ACP agents** section, at the bottom of the page, lists agents from the official Agent Client Protocol registry. Click **Add to roster** to make one available as an agent in OmniGet. Agents started through `npx` or `uvx` are registered as a command; binaries are downloaded into OmniGet’s folder and checked against the registry’s SHA-256. When the registry publishes no checksum for your system, OmniGet asks before installing without verification. ## What OmniGet does with these tools - [Threads](https://getomniget.com/docs/threads) run Claude Code, Codex, OpenCode or an ACP agent on a project, one thread per task. - [Usage, sessions and retrospective](https://getomniget.com/docs/usage) reads the session history these tools keep on your computer. - [Connections, models and limits](https://getomniget.com/docs/accounts-limits) shows the subscription limits of the accounts you sign in with. ## Common problems ### “No install method for this system.” The tool publishes no installer for your operating system. Use the **Docs** link on its card for other options. ### A tool is installed but shows **Not installed** Click **Refresh** to scan again. OmniGet looks in your `PATH` and in the usual install folders; a tool installed somewhere unusual may not be found. ### The update did not run If OmniGet cannot prove which installer owns the copy, the **Command plan** marks the update **copy only**: click **Copy** and run the command yourself. Desktop apps update themselves, and agents added from **ACP agents** are reinstalled from that section. [Previous**← Catalog and project setup**](https://getomniget.com/docs/catalog) [Next**Connections, models and limits →**](https://getomniget.com/docs/accounts-limits)