Troubleshooting

Installing

• Windows warns you before the installer runs. Before continuing, verify that you downloaded it from the official CodeNeter Download page.
• The codeneter command isn't found after installing the CLI. Open a new terminal and try again. If it's still missing, check the CLI requirements and make sure npm's global install folder is on your PATH.

Signing in

• The browser page says something went wrong. Return to the app and start signing in again.
• "Session expired. Sign in again to continue." Your sign-in has ended. Sign in again from the bottom of the sidebar.
• The CLI says it isn't authenticated. Run codeneter login. If the browser step isn't finished in time, the command stops waiting; run it again. codeneter whoami shows which account is signed in.
• Your browser doesn't open when you connect Codex. In the desktop app, use Open sign-in page in the Integrations settings.

Projects and permissions

• The CLI asks you to trust the workspace. The agent can read, edit, and run files in that folder. Choose Trust this workspace if it's a project you trust; prompts can't be sent until you do.
• The Changes tab is empty. It shows Git changes, so the project needs to be a Git repository.
• Commands ask for approval too often, or not at all. Check the Execution Permissions in Settings. In the CLI, also check /yolo and the autoApprove setting.

MCP servers

• A server isn't working. Check its status in the MCP settings, with CodeNeter: Check MCP Status in the extension, or with /mcp in the CLI.
• A local server fails to start. Make sure the server is installed and you've added any credentials it needs, such as an API key. The server's setup instructions list what it requires.
• A remote server won't connect. Check its URL and any access token the server requires.

Usage limits

When a request stops with a usage-limit notice, use the options in the notice. To change your plan, see Plans and usage.

Updates

• Desktop app. When an update is ready, Update appears next to your account at the bottom of the sidebar.
• CLI. Run codeneter update. If the CLI can't update itself, run npm install -g @codeneter/cli@latest.

Checking the CLI

Run codeneter doctor to check that the CLI can reach CodeNeter and that you're signed in.

Contact support

Email [email protected]. Include which part of CodeNeter you're using and its version, your operating system, and what you were doing when the problem happened.