HeyCC
Sandbox workflow

Inspect the runtime before running the script.

HeyCC can run shell tasks in a sandboxed command environment. Python can run when python3 is already available or after the required package is installed; it should not be described as permanently preinstalled.

A HeyCC task producing an openable file on iPhone

First checkThe shell, working directory and available commands.

Separate decisionAny package installation or network access.

BoundaryA sandbox, not unrestricted iPhone system access.

Reusable prompt

First report the working directory and whether python3 is available. Do not install anything yet. After I approve the environment, create a small script that reads [input], writes [output], and prints a validation summary. Show every command before running it.

Workflow

  1. Inspect the shell, current directory and whether python3 exists.
  2. Review any proposed package installation separately.
  3. Start with a small script whose expected result is known.
  4. Run inside the sandbox and preserve stderr and the exit status.
  5. Open the output file and keep a record of commands and dependencies.

Expected deliverable

A script, command transcript, dependency note, exit status and inspected output file. Generated commands can be destructive or simply wrong, so review paths, network calls and file changes first.

“Runs Python” does not mean “Python is always installed” or “the app can control the whole phone.”

Questions

Is Python always preinstalled?

No. The audited source supports Python when available or installed in the sandboxed environment.

Can commands access any file on the iPhone?

No. A sandboxed command environment does not imply unrestricted access to the phone or host system.

Does generated code run safely by default?

No. Review commands, inputs, network access and file changes before execution.

Continue