Workspace Cleanup Policy with Claude Code: API Runtime Pattern
A production playbook for workspace cleanup policy in cross-industry operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Platform teams managing ephemeral execution
The problem
Platform teams managing ephemeral execution need workspace cleanup policy to run repeatedly against temporary files, terminal states, storage rules, and retention policy. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the workspace cleanup policy instructions as a skill, send temporary files, terminal states, storage rules, and retention policy as run-scoped inputs, execute with Claude Code, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. For workspace cleanup policy, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run request
POST /api/skills/<skill_id>/run
provider=claude-code
workflow=workspace-cleanup-policy
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo