Autochain docs
Setup and troubleshooting for AI workflows on your Mac.
Getting started
Set up once, then build your first workflow.
Before you begin
You need macOS 12 or later, an internet connection, and your own Claude Code or Codex subscription access. Autochain uses your AI tool’s sign-in; no AI API key is needed. Your provider’s usage limits still apply.
- Open Autochain and follow the account sign-in prompts.
- In Setup check, choose the AI tools you use. Use Install if needed, then Log in.
- Finish the AI provider’s official sign-in in Terminal or the browser. Return to Autochain and use Re-check if the status has not updated.
- Connectors and skills are optional. You can finish setup without connecting any.
You can return here through Settings → AI tools → Setup check.
Your first workflow
Start small: one input, one task, one result.
- From Home, create a New pipeline or choose a template for your AI tool.
- Open the pipeline’s Assistant and describe the result you want. For example: “Take a topic, research it, then write a short summary.”
- Review the suggested changes with Preview, then choose Apply when they match your intent.
- Select each step to check its instruction, AI tool and inputs. Connections determine which steps wait for earlier work.
- Choose Check, resolve any issues it lists, then Run and fill in the required inputs.
The Assistant can explain your pipeline and suggest fixes. Review its proposed changes and action buttons before applying or running them.
Passing work between steps
In a step’s Receives from control, choose the inputs and earlier results it needs. Use Files used for input files or files made by earlier steps. Type @ in an instruction to insert an available input or output reference.
Runs and approvals
Read the result before deciding what to do next.
Open Runs in the Builder, or Run history from Home. Select a run, then a step to see its status, output, files and error details. Received shows what that step was given.
- Waiting for approval: inspect the output, then Approve or Reject.
- Waiting for a manual start: use Start step when you are ready.
- Failed or cancelled: fix the reported issue, then Resume. Resume uses the pipeline as it is now.
- Re-run from a step: runs that step and everything after it again.
Resuming or re-running can repeat work and use your AI subscription. Check whether an interrupted step already sent a message or changed something before trying it again.
Where approval belongs
Approval after pauses after a step has finished. To review content before it is sent or posted, put approval on the step that prepares it, before the separate step that performs the action.
Inputs and saved files
Find your work, and know which copy a step uses.
Add input files in Pipeline details → Files, then select them in the receiving step. Autochain keeps a local copy: changing or deleting the original does not update that copy. Add and select a replacement when the content changes.
Find a generated file
- Open the run in Run history.
- Select the step that made the file and open its files list.
- Use Show in Finder to locate it.
To create files, an AI step needs File output → Allow file creation enabled and an instruction that asks for a file. A text reply alone is not a generated file.
Save to working directory also copies a step’s generated files into the pipeline’s working directory. Check that location in Pipeline details. A later run can replace files with the same name, so keep separate copies of work you want to preserve.
Run files follow the retention setting in Settings → Runs. Input files and past run results are local; on another Mac, add the input files again.
Schedules and sleep
Your Mac runs the schedule.
In Pipeline details → Run settings → Schedule, choose when the workflow should run. Times use your Mac’s local time. Set a value for every required input and complete a manual run first.
Keep Autochain running and your Mac awake and online. A schedule cannot run while the app is quit or the Mac is asleep.
- On waking, the latest scheduled run starts if it is less than two hours late. Older times are recorded as missed or superseded in history.
- If the Mac sleeps during a run, the run pauses. It carries on automatically after waking if it started less than two hours ago; older runs wait for Resume.
- A step interrupted by sleep starts again from the beginning. Finished steps keep their results.
If a schedule did not run, check Run history for the reason, confirm the schedule is enabled, and resolve any pipeline issues shown by Check.
Connectors and code
Connect only what your workflow needs.
Open Settings → AI tools → Setup check to manage the connectors, plugins and skills available to each AI tool. Finish any required sign-in through the tool’s official flow.
A connected item is available to every Autochain step using that AI tool. It is not limited to the selected pipeline. Disconnect anything you do not need; this changes Autochain’s access without changing your usual CLI setup.
Tools that place, modify or cancel orders or move money are not allowed. If Autochain blocks a connection, choose another workflow rather than trying to bypass the restriction.
Code steps
Code steps run commands or scripts on your Mac with your user permissions. Review the code and the files it can affect before running it. If a script needs a secret, enter it in the step’s Script secrets controls rather than pasting it into instructions or shared workflow definitions.
Troubleshooting
Start with the message on the affected step.
AI tool is missing or signed out
Return to Setup check. Make sure the tool is selected, use Install or Log in as offered, finish the official sign-in and re-check. A sign-in in another copy of a CLI may not mean Autochain’s copy is ready.
Usage limit reached
Wait until your AI provider’s limit resets, then open the run and Resume. For future runs, reduce Parallel steps or run less often. An Autochain subscription does not increase your AI provider’s allowance.
A step fails or times out
Open that step’s error and Received details. Check its instruction, required inputs, selected files and connector sign-in. Fix the cause before resuming. For work that legitimately takes longer, adjust Timeout in Run settings or the step’s Advanced controls; avoid repeatedly retrying an unexplained failure.
A file or earlier result is missing
Check Receives from and Files used on the receiving step. Confirm the earlier step actually produced the expected file. If an input file changed, add a new copy and select it. See Inputs and saved files.
A connector is unavailable
Check that it is connected for the AI tool used by the step, and finish any sign-in it requests. An item disabled in the AI tool itself may need attention there first. Some connections are intentionally blocked for safety.
Still stuck?
Use Settings → About → Report a problem. Describe what you tried, what you expected and what happened. Review the listed report contents; you can leave logs out. The report is saved to Downloads, and is not sent automatically. Inspect it before sharing and remove private material, passwords or tokens.
Privacy essentials
What stays local, and what connects to a service.
Autochain keeps run results and generated files on your Mac. Account, license, device and workflow definitions are stored in Autochain’s cloud. Avoid putting secrets or sensitive source material directly into workflow instructions.
The AI tools contact their providers to process requests; local execution does not mean offline AI. Connected services receive what you ask them to process. A Notify step can send results and attachments to destinations you configure, so check the recipient and contents before running it.
Autochain does not read, copy or transmit the AI CLIs’ credential files. Complete sign-in only through the official provider flow, and never share those files or paste login tokens into a pipeline or support report.
Local app logging can be managed in Settings → Privacy. Creating a problem report gives you a local file to review; it does not upload it.
No matching guides. Try “sign in”, “files” or “Resume”, or clear your search.