Local direct execution

write-report→daemon hostresult.txt

This Showcase executes one real activity through the local runtime. The daemon starts the activity command on the same host as the daemon, then observes its workspace for created or changed files. It is useful for a controlled first real execution or a small trusted host-local tool.

Do not use this runtime to isolate untrusted workloads. It is not a container sandbox, and it does not submit work to a Kubernetes cluster or a SLURM allocation.

Prerequisites

• An AkôFlow daemon running on the host that is allowed to execute the command.
• A POSIX sh and printf available to that daemon process.
• Permission to run a trusted command and to create its temporary activity workspace.

The bundle declares busybox:1.36 as an executable reference because portable real-workflow imports require one. The local adapter does not pull or run that image: it invokes command.entrypoint and command.arguments on the daemon host.

Download the inputs

Environment YAML ↓Execution scope YAML ↓Network topology YAML ↓Workflow YAML ↓Manual plan envelope ↓Execution envelope ↓Submission script ↓

AkôFlow Desktop

Run with AkôFlow Desktop

1. In Infrastructure → Environments, create the local environment and its local-host resource from environment.yaml. Keep its execution target as Direct.
2. Create the scope and topology from the supplied YAML. This one-host Showcase deliberately has no network links.
3. In Workflows → Definitions, import workflow.yaml. Open its definition and confirm that write-report is a real activity assigned to the local runtime.
4. Create a manual plan with write-report on local-host, or import plan.yaml through the plan API. Start a Real execution.
5. When the run is complete, open its activity details and artifacts. Verify that result.txt is listed as a created file.

The host that runs Desktop is not necessarily the execution host; the daemon's host is. Check that distinction before starting a direct run.

API

Run through the API

From the repository root, submit the versioned files in their required order:

export AKOFLOW_API_URL="http://127.0.0.1:8080/akoflow-api"
# Set AKOFLOW_API_TOKEN too when this daemon requires authentication.
sh examples/local/direct-hello/run.sh

curl --fail-with-body "$AKOFLOW_API_URL/execution-runs/local-direct-hello-run-v1/"

When the daemon requires a token, set AKOFLOW_API_TOKEN; the supplied script adds the matching bearer header to each request.

Verify the result

The checked-in files were run against an isolated local daemon on 2026-09-12. local-direct-hello-run-v1 completed its one activity; the recorded artifact manifest contained one created file, result.txt, at 24 bytes with checksum:

sha256:602b3cbda35539a2cd4c0504fe198cb423493832d93cf78147a470b2d82329db

The observed runtime was approximately 0.006 seconds on that host. Treat that duration as evidence for this small command, not as a performance baseline for another machine. The expected content is:

Akoflow local execution

The run has no data dependency and therefore reports zero transferred bytes. Use the Kind real-execution Showcase when you need a workflow that transfers output between activities.

Troubleshooting

Symptom	Cause and recovery
activity entrypoint is required	Use the supplied workflow or set command.entrypoint; run is converted to sh -c by the portable workflow importer.
start local activity fails	The daemon host cannot find or execute the command. Verify sh is on its PATH, then use an absolute entrypoint if needed.
The activity writes no artifact	The run only records changes made below its activity workspace. Make the command write relative to its working directory, as this example does.
The wrong machine executes the command	Direct execution always occurs on the daemon host. Run a daemon in the target environment, or use a remote runtime such as Kubernetes or SLURM instead.

Read Execution modes and runtimes for the execution boundary and Workflow runs for monitoring and cancellation.