Is OpenCode down? User reports show no current problems with OpenCode

Is OpenCode down right now?

No. OpenCode answers normally for most users right now. This page tracks OpenCode status through live checks and OpenCode down reports from the community. A green result means the website, the docs, and the hosted model gateway all respond.

Remember that OpenCode runs on your own machine. A dead session here often means a provider or a local config fault, not a server outage. The reports below show which side is failing today.

Is OpenCode down for me or everyone?

Run one prompt with a second provider, such as a local model or a different API key. If that works, your first provider or its key is at fault. If every provider fails inside one project, suspect the project config file. A true OpenCode outage shows up across many users at the same time.

How do agents change the way OpenCode works?

OpenCode ships with two main agents. Build holds full tool access and edits files freely. Plan works read-only, so it answers questions and drafts steps without touching your code. You swap between them with the Tab key mid-session.

Custom agents add their own rules on top. A config file sets each agent its model, prompt, and tool permissions. Subagents handle narrow jobs, like a review pass, while the main agent keeps the full picture.

What does the /connect command set up?

The /connect command links a model provider to your copy of OpenCode. You pick a provider from the list, then paste an API key or finish a browser sign-in. Zen, the hosted gateway from the OpenCode team, is one choice among many.

Why do free models refuse to run?

The free tier error usually points at your config, not your account. A leftover provider entry aimed at the old Zen address triggers it. Denying the read or shell tool in permissions triggers it too. Cleaning the config and signing in again clears the block for most users.

Can OpenCode run a model on my own machine?

Yes. Any provider with an OpenAI-style endpoint works, including local servers on your own hardware. Point the base URL at the local address in the config file. Local models skip the network fully, so a provider outage cannot stop your session.

Common OpenCode Problems and Fixes

Most OpenCode faults trace back to one config line, one dead key, or one stuck session. Try the five fixes below in order and rerun a tiny prompt after each step.

API key expired error on every prompt

That key died on the server side, and signing in again will not revive it. Create a fresh key in the OpenCode Console and replace the stored one.

Free tier error inside the official app

Open your config file and delete any leftover provider entry for the old Zen address. Then check your permissions block; free models need the read and shell tools allowed. Sign in once more with /connect and test a free model.

Provider connects but never answers

Test the same key in a plain terminal call to the provider. A hang there means the provider or your network is at fault. Inside OpenCode, a wrong base URL in the config gives the same silent wait.

Agent edits the wrong files

Stop the run and switch to the Plan agent for a read-only pass. Ask for a file list before any edit lands. Tight permission rules in the config can fence the agent out of folders it must never touch.

Sessions or history went missing

OpenCode stores sessions per project folder, so launching from another folder shows an empty list. Start it again from the real project root. The /sessions command lists what the current folder holds.

Having a problem with OpenCode?

Comments are public and help others understand the issue.

Subscribe

Login

Notify of

new follow-up comments new replies to my comments

Label

{} [+]

Name*

Email*

Label

{} [+]

Name*

Email*

0 Comments

Oldest

Newest Most Voted