Startup failures report no logs because there is no viewLogs method

Before submitting your bug report

• I've tried finding an answer on the Continue docs site
• I'm not able to find an open issue that reports the same bug
• I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS:MacOS 15.7.7
- Continue version: 2.0.0
- IDE version: VSCode 1.127.0
- Model:ANY
- config:
  
{
  "models": [
    {
      "title": "Gemma4:e4b (Ollama)",
      "provider": "ollama",
	"model": "gemma4:e4b",
      "apiBase": "http://localhost:11434"
    }
  ]
}

  
  OR link to agent in Continue hub:

Description

The Troubleshooting guide says to open the console and look at the console window.
But start up failures offer the use a button "Show Logs". But it does nothing.
Looking at the console window we see why:

2026-07-05 20:45:34.005 [error] Error: command 'continue.viewLogs' not found
at Zrt._tryExecuteCommand (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1893:4832)
at Zrt.executeCommand (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/

If I understand the README, it seems like 2.0 is planned as the last version of Continue. I hope that's not true.

Suggestion: It would make things easier for users if a viewLogs method were added.

To reproduce

1. Configure any of the setups where activation fails.
2. Press "Show Logs" button.
3. Expected behavior, Logs show up; Actual behavior: the failure alert disappears, showing no logs.
4. Look in console log, filter on "continue"
5. See the error message like I logged above complaining continue.viewLogs not found.

Log output

2026-07-05 20:45:34.005 [error] Error: command 'continue.viewLogs' not found
    at Zrt._tryExecuteCommand (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1893:4832)
    at Zrt.executeCommand (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/

Start by tracing the startup failure alert's "Show Logs" action and the continue.viewLogs command reference. Check how commands are registered and verify that the completed flow opens the relevant logs when startup activation fails.