System Tools
The always-available core that powers built-in actions and basic OS control.
Underneath the broader capabilities sits a small, always-available core of low-level operating-system operations. These power the built-in UI actions and basic system control, and — unlike most capabilities — they're never unloaded.
Why it's separate
Most capabilities can be unloaded when idle to save memory. The system core can't — it's always available, so MeghaOS can always launch apps, touch the clipboard, and control basic hardware, even under memory pressure.
What it provides
| Operation | Does |
|---|---|
| Launch / close app | Open or quit an application |
| Create folder / file | Make a directory or write a new file |
| Move / delete file | Move, rename, or remove a file |
| Capture screenshot | Grab the screen |
| Read / write clipboard | Access clipboard contents |
| Set volume / brightness | Adjust output volume or screen brightness |
| Toggle Wi-Fi | Turn Wi-Fi on or off |
| Download / extract file | Fetch a file or unpack an archive |
Path safety
File operations run through an internal safety check that validates and normalizes paths before acting — a guardrail against touching unintended locations. Destructive operations are meant to be deliberate, not accidental.
How it's used
- UI actions — volume, brightness, Wi-Fi, open/close app come straight from interactive widgets.
- Workflows — the system core participates like any other capability in a workflow.
Relationship to file management
There's intentional overlap with the rich file management capability (search, bulk operations, archives, the visual explorer). The assistant prefers the full capability for complex file work and falls back to the system core for basic operations.
Because the system core can write and delete files and control hardware, sensitive operations may surface a confirmation first.