Status and maintenance
Indexing progress, CPU usage, three log types and rebuilding indexes.
Read the status
Hover over Hornet C/C++: idle to see the version, mode and CPU Usage. During scans, the current stage's percentage and file count appear. Source / header counts and clangd compilation-database task counts measure different things and need not match.
Click the status bar to open the action menu. VS Code manages the status bar's context menu; Hornet offers its own actions through hover links and a left-click menu.
Maintenance actions
| Action | Purpose |
|---|---|
| Open Extension Logs | Extension startup and general runtime information. |
| Open Clangd Logs | clangd startup, compile arguments and semantic parsing logs. |
| Open Hornet-DB Logs | Tag / Flyweight lightweight indexing logs. |
| Open Settings | Open Hornet settings. |
| Update Index | Update the existing index. |
| Rebuild Index | Restart the parser, clear the workspace's standard clangd index cache and rescan. |
| Reload window | Reload the VS Code window. |
| Clear Errors | Clear current diagnostics; the next parse may report issues again. |
Adjust CPU usage
Maximum is the default; High, Medium and Low are also available. This changes clangd thread counts and the lightweight parser's work share, not an OS-level hard cap on CPU usage.