PC TidyUp for VS Code

Review Windows disk usage, scan folders, and use PC TidyUp's cleanup, compression, OneDrive archive and restore tools inside an editor tab. This optional developer interface uses the same local app as standalone PC TidyUp. No cloud processing or telemetry is added. Existing standalone launchers and scheduled scans remain usable.

Published by Agentics B.S..

Product branding

Publisher profile: Agentics B.S..

Agentics B.S. publishes this extension as AgenticsBS.pc-tidy-up. The compact tiger-and-broom icon identifies the extension and browser tab. The dashboard uses the full PC TidyUp logo supplied by the publisher.

Updating an existing installation

This package uses extension ID AgenticsBS.pc-tidy-up. If you installed an earlier package from a different publisher, uninstall only that VS Code extension, then install this package. Keep your standalone app, shared runtime, settings and reports.

Finish or cancel unfinished jobs before updating the shared app; paused jobs must also be completed or cancelled. Run PC TidyUp: Update Shared Runtime from the Command Palette, then PC TidyUp: Open Dashboard. Installing the new extension alone can reconnect to your existing runtime without upgrading it.

From installation to your first dashboard scan

Use VS Code on Windows 10/11. All commands below run in the VS Code Command Palette, opened with Ctrl+Shift+P. You do not need a terminal, a separate Python or Node.js installation, or administrator rights for normal use.

1. Finish installing the extension. Stay in the VS Code profile where you installed PC TidyUp. If VS Code offers Reload Window after installation, click it. The dashboard does not open automatically.
2. Open a folder you trust. Use File > Open Folder... and open your intended working folder. If VS Code shows Restricted Mode, press Ctrl+Shift+P, run Workspaces: Manage Workspace Trust, and trust the folder only if you know its contents. PC TidyUp operations require a trusted workspace.
3. Start PC TidyUp. Press Ctrl+Shift+P, type PC TidyUp: Start PC TidyUp, select that command, and press Enter. This prepares and starts the local shared app; it does not open the dashboard or start a scan.
4. Wait for setup to finish. Follow the PC TidyUp shared runtime progress notification. A new installation uses the runtime bundled with the extension. If an older standard installation is detected, finish its active work and close the older app, then choose Use existing installation in the prompt. Your settings, personal rules and reports stay in place. When connected, the VS Code status bar shows PC TidyUp: 0 running | 0 paused if there is no active job.
5. Open the dashboard. Press Ctrl+Shift+P, run PC TidyUp: Open Dashboard, and wait for the PC TidyUp editor tab. You should see the product icon, dashboard tabs and Run new scan button. No report yet is expected before your first scan.
6. Accept the disclaimer when prompted. Read Before you start: disclaimer, select I have read and accept the disclaimer..., then click Accept and continue. This prompt may appear when opening the dashboard or when you first request a scan. Not now (read-only) lets you browse but prevents scans and file actions until you accept.
7. Run your first scan. Click Run new scan in the dashboard. In Run a new scan, enter the folders or drives to inspect, separated by ;, for example C:\Work; D:\Projects. Start with a small folder for a quick first result. Optionally select Skip duplicate detection for a faster scan. Review the background-continuation option, then click Start scan.
8. Use the results. Follow progress at the top of the dashboard or in Explorer > PC TidyUp Jobs. When the scan finishes, the dashboard loads its report automatically. Open Overview, then review Clean up, Compress or OneDrive as needed. File changes require a separate action and your confirmation. Saved results also appear in Explorer > PC TidyUp Reports.

Already installed in a custom folder? Before step 3, run PC TidyUp: Choose Existing Installation, select the folder containing your existing Run-TidyUp.ps1, then continue with Start PC TidyUp. Source developers can instead set an absolute launcher path in the User setting pcTidyUp.runtimeLauncher; workspace overrides are ignored.

Next time you use PC TidyUp

Run PC TidyUp: Open Dashboard from Ctrl+Shift+P. It starts or reconnects to the shared app automatically, so a separate Start PC TidyUp command is optional. Opening the dashboard does not start another scan; use Run new scan when ready.

Command reference and startup help

• No PC TidyUp commands: open Extensions (Ctrl+Shift+X), check that PC TidyUp is installed and enabled in this profile, then run Developer: Reload Window from the Command Palette.
• Trust error: complete step 2, then retry Open Dashboard.
• Disconnected before first startup: continue with step 3. If startup reports an error, read its VS Code notification; finish and close any older standalone app before retrying. After correcting the error, run Open Dashboard again.
• Dashboard open but empty: click Run new scan and complete steps 6–8. Reports only appear after a scan completes.

Reports and jobs

Open Explorer > PC TidyUp Reports for read-only saved reports, and PC TidyUp Jobs for shared processing state. The status bar always shows running/paused counts while connected. Disconnect means status is unknown, not that work stopped. The dashboard includes settings, rule editing, current progress and file actions.

Only one unfinished job is allowed. Pause waits for a safe checkpoint; an individual move/copy/Windows operation may finish first. Resume continues remaining work and rechecks files. Cancel waits for cleanup; completed file changes are not undone. Paused work keeps the runtime alive and blocks updates until resumed or cancelled.

Closing and background work

Use Close PC TidyUp View... to continue in background, pause and close, cancel and close, or keep the view open. Pause/cancel affect the shared job everywhere. The view waits for acknowledgement before claiming processing stopped.

New VS Code jobs default to pausing after 30 seconds without an interface unless you approve Allow this job to continue after all PC TidyUp interfaces are closed. Native tab/window closure cannot always show a custom dialog, so the recorded job policy applies. Existing standalone and headless/scheduled jobs keep their background behavior. Opening a different interface never changes a job's policy.

The standalone browser remains available via Open in Browser. Removing this extension retains the independent app, its data, and accepted work. With no unfinished jobs, the runtime stops after its configured idle timeout (20 minutes by default). No sign-in startup or new scheduled task is created by this extension.

Update and recovery

Finish or cancel unfinished work, then choose Update Shared Runtime. Updates retain prior code, runtime-installation.previous.json, and a recovery backup of replaced entry points. Never edit a version currently in use. To roll back, stop the idle app and restore the previous installation pointer; keep all data in place. Standalone updates still use the public installer. A running legacy process is never force-killed: close it after its work finishes, then retry.

Use Help and About, License and Disclaimer without starting the runtime. Windows administrator restart uses UAC for the app; VS Code need not be elevated.

Safety and license

Review the disclaimer and every proposed action. Use backups and disposable test folders. File actions retain protected paths, age checks and confirmation dialogs; only current-report items can be modified. Reports contain personal file paths.

Copyright (c) 2026 Agentics B.S.. Free for personal and other noncommercial use under the PolyForm Noncommercial License 1.0.0. Use outside the license grants requires separate written permission from the relevant rights holder. See LICENSE.md and DISCLAIMER.md for the full terms.

Software license and included components

PC TidyUp is free for personal use and other purposes permitted by PolyForm Noncommercial 1.0.0. Ordinary commercial/business use requires separate written permission. Read LICENSING.md, LICENSE.md and DISCLAIMER.md; source availability is not an unrestricted business-use license.

Bundled Python and its libraries keep their independent licenses. See THIRD-PARTY-NOTICES.md for component versions, attribution, Microsoft runtime conditions and full notice locations. These product restrictions do not remove permissions granted by independent component licenses.

After installation, press Ctrl+Shift+P and run PC TidyUp: About, License and Disclaimer to read product terms and full component notices offline. PRIVACY.md explains local reports and synced-folder cloud effects. Agentics B.S. is the publishing name; no registered company status or third-party endorsement is asserted.

Development

Build tooling requires Node.js 22+ and PowerShell 7.4+; neither is required by end users. From pc-tidy-up/, use pwsh -File scripts/Build-Extension.ps1 to restore locked build tooling and create out/PC-TidyUp-VSCode-1.2.6.vsix. Pinned interpreter downloads occur on the build machine; installed first use is offline. scripts/Open-ExtensionDevelopment.ps1 prepares the payload and opens the extension folder; press F5 for an Extension Development Host.

Run python -m unittest discover -s tests and npm --prefix integrations/vscode test. Builds do not publish or install. The public Marketplace candidate must pass standalone compatibility and isolated-profile acceptance before publication.