fusedio/agent-core

Reference for the fused CLI — environment management, file storage, secrets, code execution, and infrastructure commands. Use when writing or explaining shell commands that invoke fused, or when helping users set up, switch between, or provision environments. If the commands are part of building or running a project, load fused-projects first for the end-to-end model.

Best practices for running code with fused code run. Use when writing or reviewing code you will execute through the fused CLI — covers how to structure user code, choose a data library, handle results, write outputs to the file store, pick a project venv, fan out, and what caching code run applies. For static scanning, spec checks, and testing see fused-verify. If this is part of building or running a project, load fused-projects first for the end-to-end model.

Entry-point router for the Fused skills in this repo. Use when a user asks how to get started with, set up, or install Fused, how to build a project or UDF, how to run or validate code with the fused CLI, or is unsure which Fused skill to load. Maps a goal to the specific skill(s) to read next.

Reference for the infrastructure managed by fused — what resources exist, why each one is needed, and when they are created, updated, or deleted. Covers the AWS backend (IAM, Lambda, ECR, S3) and the local backend (data directories + venvs, see "Local backend infra"). Use when helping users understand, provision, or troubleshoot the resources that back an fused environment.

The canonical end-to-end guide for an agent driving Fused — pick an environment, create a project, decompose a task into UDFs, author specs and code, validate + commit, run locally, and deploy through preview to release. Code is authored by the driving agent (no codegen command, no API key); fused supplies validation, the spec↔code pairing hook, and run/deploy, all through the fused CLI. Use to take a user request from prompt to a running result.

Step-by-step guide for installing and setting up fused for the first time, including AWS credential checks, detecting an existing installation, provisioning infrastructure, and verifying the setup. Use when a user asks how to install, configure, or get started with openfused.

The fused storage and secrets CLI commands — inspecting cloud-native datasets and managing secrets. Use when finding/listing/counting S3 objects, reading a Parquet/Arrow/CSV schema, minting a download URL, uploading content, or storing/reading/deleting secrets, via fused files list|count|get|schema|upload and fused secrets put|get|list|delete. For running code over the data see fused-execute; for the full flag reference see fused-cli. If this is a step in building or running a project, load fused-projects first for the end-to-end model.

Static scanning, spec checks, testing, and the audit log for code run with fused. Use when running or reviewing fused code verify, fused code test, or fused audit log, or when advising on what fused's verify layer does (and no longer does). If you're validating code that belongs to a project, load fused-projects first for the end-to-end flow.