Chatbot

This article is the chatbot job. You want a bot session you start on this machine, talk to, and leave running for a small task. A one-prompt conversation sits on AI chat. The free-key walk sits on Free AI. People who wanted another company's website without an account sit on ChatGPT no login. The short pointer sits home.

This is OpenCode. MIT. The OpenCode project publishes it. We did not make it. Official files live on GitHub Releases. The repo is sst/opencode (anomalyco/opencode). Official site is opencode.ai. This site does not host a model or a chat app. Skip Softonic, CNET, and unofficial wrappers.

The button on this page goes to Install on the home page. Trust notes sit on Free chatgpt download safe.

Install the chatbot tool

Copy this command, then paste it into PowerShell if you use Scoop:

scoop install opencode

Official docs also list Chocolatey package opencode:

choco install opencode

Official docs also list a Node global package named opencode-ai:

npm install -g opencode-ai

On macOS or Linux, official docs list Homebrew:

brew install anomalyco/tap/opencode

On WSL, macOS, or Linux you can use the official install script at https://opencode.ai/install:

curl -fsSL https://opencode.ai/install | bash

Usual Windows zip is opencode-windows-x64.zip. An arm64 zip sits on the same tag. Open the list on GitHub Releases. Live tag observed: V1.18.25, 28 August 2026. File notes sit on Free chatgpt releases. LICENSE sits on Free chatgpt GitHub. Official docs recommend WSL on Windows if you prefer the script path.

How to use a chatbot tool OpenCode

1. Install OpenCode with scoop install opencode, or take opencode-windows-x64.zip from GitHub Releases.
2. Start OpenCode in the terminal so a chatbot session is running on this machine. You should get a local session, not a website we host.
3. Connect a provider with /connect and a free Groq or Google AI Studio key, or point at Ollama at http://localhost:11434/v1.
4. Pick a model with /models.
5. Talk in that session. Ask the bot to do a small local task. Confirm you got a reply in the same terminal. Close the session when you are done.

That list is the chatbot path. You are running a session you can leave open. You are not visiting a toy webpage bot. After the five steps, ask one small task and wait for the reply. Checking is part of the job.

What a chatbot is on this machine

Chatbot here means a session of OpenCode you start in a terminal, connect to a provider, and talk to as a bot. The bot is the agent in that window. It is not a cartoon bubble on a marketing site. It is not a page we host.

People type chatbot when they want something they can start, ask, and keep around for a few minutes of back and forth. A one-shot question can sit on the AI chat article. This page stays the session you keep open.

The bot does not appear until the program runs. If the terminal is closed, the session is gone for that hour. Start it again on this machine.

Start a session in the terminal

Open a terminal you control. Run OpenCode. Wait until the session is ready for a command. Then connect a provider. Then pick a model. Then talk. That order keeps the bot from sitting there with nothing to speak through.

A website that draws a fake bot and asks you to paste a key into a form is the wrong shape. Keep the key in /connect inside the local session. Keys sit in ~/.local/share/opencode/auth.json. Do not paste that file into a group thread.

If the session never starts, you may have the wrong binary. Uninstall a wrapper. Install from Scoop or GitHub Releases. Trust notes sit on Free chatgpt download safe.

Talk, then leave the session

Ask the bot to do a small local task you can judge: rewrite a sentence, list three file names in the folder you are in, or explain a function you just pasted. You want a reply in this terminal. Then ask a follow-up. That is a chatbot session, not a single search result.

Leave the session open while you work if you still need it. Close it when you are done. Closing the window is not uninstall. The program stays on this PC until you remove it.

We did not sit on your PC and watch every tool call. We will not write a guarantee we did not observe. If a task fails, read the error in the same window. Check the model, the key, or Ollama.

Agent work vs a toy webpage bot

OpenCode is a terminal agent. That is heavier than a webpage that only echoes a greeting. You can ask it to work with files you already have on this machine. You still decide what to send. Do not paste secrets you do not want a provider to see.

A toy webpage bot is easy to fake. This page stays the GitHub program. Official docs live on opencode.ai. The one-prompt walk sits on AI chat. The free-key walk sits on Free AI.

We will not clone another company's chat homepage. This site does not host a chat app.

Keys and local Ollama

Open the Groq console, create an account, click Create API Key, and copy the key. Google AI Studio is another free key path. Run /connect, search for Groq or the Google provider they list, paste the key. Official docs list Groq under Providers. This site does not issue keys.

For a local bot with no cloud key, install Ollama, pull a model, and point OpenCode at http://localhost:11434/v1. Official docs show that local provider. Start Ollama before you start the chatbot session. This site does not host Ollama.

Skipping Softonic

Skip Softonic. Skip CNET. Skip unofficial wrappers. A search for chatbot is noisy. Portals wrap installers. Fetch OpenCode from Scoop, from GitHub Releases, or from the official install page. Match opencode-windows-x64.zip or the arm64 zip on V1.18.25. Files stay on GitHub. This site does not host the installer.

Checking the bot answers

The job is not finished when the session opens. The job is finished when the bot answered a small task in this terminal. If it failed, the session may lack a model, a key, or a running local server.

A first task that rewrites one sentence is enough. A first task that edits a whole project is a bad first test. Learn the session, then grow the ask.

School PCs and uninstall

A lab image may block unknown programs. Then this chatbot job is closed for that hour. Do not fetch a wrapper. A borrowed laptop you return in twenty minutes is a bad place to leave a key. Use a PC you control.

If you installed with Scoop, Scoop can remove the package. If you took the zip, delete that folder. Closing the chatbot session is not uninstall. Fetch again from GitHub Releases or Scoop, not from a wrapper.

What this article will not do

It will not host the installer. It will not host a model. It will not be a star rating. The install pointer is Install on the home page.

It will not replace the AI chat walk. That sits on AI chat. It will not replace the free-key walk. That sits on Free AI. It will not invent a login bypass. That mix-up sits on ChatGPT no login.

First bot session

Install. Start. Connect. Pick a model. Ask one small task. That is a first chatbot. A request that rewrites every file you own is a terrible first test. You want to learn the session and one reply you can check.

If the bot stays silent, you may have skipped /connect, or Ollama is not running. Add a real key or start the local server. If the program never appears, uninstall a wrapper. Install from Scoop or GitHub Releases. Match V1.18.25 until the release page shows another tag.

Keep the session on a disk you keep. Do not drop the zip into a kiosk folder other people wipe at logout. Use a PC you control.

How do I use a chatbot on this machine?

Paste scoop install opencode, or take opencode-windows-x64.zip. Start OpenCode. Connect a provider. Pick a model. Talk in that session. The install pointer is Install on the home page.

Is this a website chatbot?

No. This page documents a local terminal agent. This site does not host a model or a chat app. You bring a free API key or Ollama.

Did you make this chatbot tool?

No. The OpenCode project publishes OpenCode under MIT. Official files live on GitHub Releases. This site only points at that page. We do not host the installer.