Read CodeSpace Problems and Output Panels
Interpret Monaco diagnostics, jump to file locations and inspect timestamped operation messages in CodeSpace without mistaking them for server tests or logs.
The bottom panel has Problems and Output tabs. Problems is initially selected. Use the tabs to switch views and Close Panel to hide the panel.
Problems
Problems are built from Monaco markers associated with files open in CodeSpace. Each entry can show severity, message and account-relative path:line:column. The badge reports the current number of collected diagnostics across those models, rather than only the active tab.
Click an entry to activate/open its file and move the cursor to the diagnostic position. Available language services decide which errors or warnings can be detected. A closed or unopened project file is not guaranteed to have been analyzed.
No problems detected has a limited scope
An empty list means no diagnostics were collected from the available editor models and language services. It does not prove the project builds, the server runtime accepts it, or the application is secure and functional.
Diagnostics can update while you edit unsaved text. They do not save the file or run server tests. Validate important changes using the application's actual runtime and test process.
Output
Output shows messages emitted by workspace actions, such as creation, save results and formatting errors. Messages are prepended with the browser's local time and success, warning, error or information styling. A new message opens the Output panel automatically.
Inspect messages together with modified-tab markers and file state. Save All can partially succeed; a success label is not a complete transaction report. Some detailed opening/saving failures are logged only to browser developer tools, so the panel is not an exhaustive error log.
Output is not a terminal, application stdout, web-server log viewer or persistent audit history. Reloading the workspace loses its in-memory messages.
Hidden panel
Close Panel hides the whole bottom panel, including its tabs. The current template has no separate dedicated reopen button; a later operation that emits Output can show it again. Do not reload merely to recover panel visibility while files are unsaved. Preserve and save work before any reload.