OCTOSENSE / EXPERIENCE MANUAL

System & devices

Understand a maintenance task before it runs

01 / TRY THIS SCENARIO

Storage is running low. The agent prepares a proposal to remove temporary files while leaving documents alone.

02 / FOLLOW THE EXPERIENCE
System & devices

Storage · Low space in this example

Candidate · Temporary app files

Documents · Outside this proposal

On your desktop

The next action will appear here

Place the same card
Shared contextStorage inventoryBackup statusDevice activity

The system view shows the issue and the inspected categories.

Step 1 / 4

Concept walkthrough · All content and actions are simulated

Using the application

  1. 01

    Open system management to inspect storage, backups, and connected devices directly.

  2. 02

    Expand the cleanup proposal to see categories, the exact scope, and the estimated space to reclaim.

  3. 03

    Exclude anything you want to keep, then authorize the selected maintenance task. Review the result afterward.

Using the desktop App Card

  1. 01

    A desktop card summarizes the storage issue and proposed cleanup, with an entry point to inspect the details.

  2. 02

    Approve this cleanup or define a narrow recurring rule. A rule remains visible and can be turned off.

How the context connects

Only the sources you have connected and allowed

Storage inventory

Distinguish temporary files from documents and show what was actually inspected.

Backup status

Surface backup information when it matters to the selected operation.

Device activity

Schedule permitted maintenance for a suitable idle period.

What you authorize

Authorize specific categories and actions. A temporary-file cleanup rule does not extend to personal documents, account changes, or software installation.

When the agent works

A threshold or scheduled check can prepare a proposal. Execution follows approval or the scope of an existing rule.