Inspect tasks and processes
2 minute read · Local Tasks
Resource Manager brings local tasks and processes into a single table. Use it to see what is still working, inspect a result and stop the particular supported task you intend.
Read the table
Open the Resource Manager control in the app chrome. Each row shows Process, Project, Workspace, Status / time, CPU and Memory, with its available actions. Search by the task, project or workspace and include finished entries when needed.
The table includes supported agent runs, background scripts, local processes and Vortex's own Electron processes. CPU and memory readings are observations for the available local processes. An absent measurement is not zero usage, and one high reading alone does not establish a memory leak.
On a narrow window, scroll the table horizontally to see the remaining columns. Use the information button for the row's details and available output, result or error.
Stop the intended task
Use × on a supported active local row. Check the task identity, project and device before confirming a stop when requested. Two scripts can share a name; stopping one must target its own run.
Stopping a task can interrupt its work. Read the result and inspect changes before starting it again. A stale entry, a foreign device or an unknown process is not permission to terminate an arbitrary system process. Vortex's built-in Electron process rows show measurements without an action to terminate the application.
Clear finished entries
Use the trash action on a completed row, or Clear finished for completed entries matching the current filter. This removes entries from the manager's visible history. It preserves their conversations, results and project files.
The dismissal is saved locally for the current account. It is different from deleting a conversation, removing a project or stopping a running task. Clear a search filter when you need to see the broader list again.
Return to the work
Inspect the detailed result or return to the related conversation. For an app-owned background script, Vortex keeps its completion with the owning chat and resumes that conversation when the job finishes. A process ending successfully still needs the checks appropriate to the task.
Related: background scripts, workspace activity, local schedules.