fused-executelisted

# Running code via fused > **Part of the Fused skill set — don't work from it alone.** Fused is `workspace ⊃ > project ⊃ UDF`. If the task is part of building or running a project (not a > one-off snippet), load **`fused-projects`** for the end-to-end model, and > **`fused-widgets`** if the result is a rendered UI. See **`fused-guide`** for the > full set. ## Core principle: code should do one thing The code string passed to `execute_code` should be as focused as possible: - One clear task per execution - No boilerplate, no CLI argument parsing, no `if __name__ == "__main__"` guards - Return the result from a `@fused.udf`-decorated function (preferred), or assign it to a top-level `result` variable ## Choosing how to return: `@fused.udf` vs `result` **Prefer a `@fused.udf` entrypoint over a top-level `result =` assignment.** Both return the value identically, but a UDF is the more capable, portable form: - It takes parameters, so the same code runs standalone *and* as a fan-out worker (`.map()` / `fused.load()`) or a served route — kwargs arrive via `_openfused_args.json`. - It matches the real `fused` SDK, so code moves between fused and Fused unchanged. - It keeps the return value in an explicit `return`, not a magic module global. ```python import fused @fused.udf def main(threshold: int = 0): ... return {"count": n} # becomes the return value ``` Use a bare `result = <scalar>` only for a quick one-off where there are no parameters and you won't r