Linux

Shadowfetch Linux 4.0

Mission Control

Turn a task into files, test results and changes you can inspect. A native queue for scoped work on your Shadowfetch desktop.

Mission Control. Mission Control on Shadowfetch Linux 4.0. Request, execution and review stay on one desktop.
Mission Control on Shadowfetch Linux 4.0. Request, execution and review stay on one desktop.

One mission. An explicit scope.

  1. Create a project in Element Workbench, then choose New mission.
  2. Select the existing project folder, workflow, instructions and provider.
  3. Approve the connection and, for code, the exact test command.
  4. Watch Activity. Inspect Changes, Results and the execution receipt.
  5. Accept the result or restore the mission's local changes.

Projects live directly inside ~/Workspaces. In Dolphin, right-click a project folder and choose Shadowfetch Mission to open the same form.

Code & tests

Describe a concrete change and supply a test program and arguments. The agent works inside the approved project, attempts bounded repairs when tests fail, and leaves the diff and validation receipt for review. Use your configured Codex cloud provider.

shadowfetch-workbench create software-studio demo-project
shadowfetch-control --workspace ~/Workspaces/demo-project --kind code

Test commands are argument arrays; shell syntax is not silently evaluated. Cloud execution requires explicit network approval and the provider's own account or credentials.

Reports with sources

Select text files by their relative paths inside the project. The workflow builds a report with source citations and an execution receipt. Check whether each source supports its claim; the citation check does not replace editorial judgment.

Source reports use configured Codex cloud access and require explicit network approval. Select only the project material you intend to send to that provider.

Media exports with receipts

Choose source media files. The deterministic FFmpeg workflow exports them and checks the resulting streams. Output files, sizes, digests and validation records stay together, ready for review.

Results you can check.

Code missions retain their diff and test results. Reports retain citations for review against the selected inputs. Media exports retain stream checks, sizes and digests. The release evidence records the actual tasks and test conditions for the published image.

Persistent work, deliberate recovery

A queue that survives interruption

Queued tasks persist locally. One execution slot controls concurrent work. Running tasks have time and process limits, cancellation and bounded retries; interrupted tasks need attention instead of silently repeating.

Review before acceptance

A successful task waits for review. Check its activity, diff and artifacts. Local restore uses its project checkpoint and refuses conflicts with newer edits. Recovery cannot reverse external effects of an approved network action.

Grok Bot has its own native workspace.

The official Grok Bot desktop is featured alongside Mission Control. Its cloud tasks, permissions and sign-in are managed in that application. Meet Grok Bot →