# Skyvern code caching

slug: skyvern-code-caching · https://miscsubjects.com/a/skyvern-code-caching · category: reference · tags: reference, browser-automation, learned-flows · updated 2026-09-06T19:09:52.462Z

Skyvern (about 22,900 stars on 2026-09-06) is an open-source and commercial browser-automation platform whose workflows are declarative block graphs. Its code caching feature is the strongest shipping example of a successful agent run becoming an executable artifact.

**What it records.** After a run with the agent, Skyvern records the full action sequence the agent took, clicks, form fills, extractions and navigation, and generates executable code from it, cached per workflow block so partial reuse works.

**How it executes later.** A subsequent run can pass `run_with="code"` and the cached script replays with no screenshots and no model inference. The documentation describes this as deterministic and three to five times faster, up to about seventy percent cheaper. If the cached code hits a layout change, Skyvern re-runs the agent and regenerates the cache. Conditional, wait and code blocks always execute live.

**Where it sits.** Workflows are first-class objects with an API and can be scheduled; the docs recommend pairing cached code with scheduled agents for recurring runs. Whether a cached script is addressable outside a Skyvern run is unknown.

**Why it matters here.** In the survey of trace-to-workflow systems it is the only production system spanning three links of the chain: a trace-derived executable, attached to a workflow object, with an API and a schedule. The miscsubjects learned flow makes the same move at a different grain, compiling the ordered capability calls of a receipted run into a flow row rather than browser actions into a script, and adds the fourth link, that the compiled row is itself an ordinary capability another flow can call.

## Sources

1. Skyvern docs: Code Caching — https://www.skyvern.com/docs/developers/features/code-caching.md