Ways to automate engineering work

Agents run as steps in your workflow and only use the tools you allow.

Each workflow is a file in your repository. Changes go through code review, so your whole team uses the same process. A workflow mixes agent steps with normal commands, which are fast and give the same result every time. It can repeat a step until your checks pass, or wait for a review comment and continue with the earlier context. You set the checks and approvals, as strict or as light as you want. Each agent gets only the access it needs, never a personal account.

Pick any model for each step, and run on our cloud or your own.

Use a low-cost model for simple work, and a stronger model only when you need it. You see the cost of each run. Shipfox is MIT licensed and self-hostable, so you can move your workflows to another system at any time.

Workflows watch your other runs, find what breaks, and suggest a fix.

Every run keeps a full log and its cost. A workflow can start when another run fails, read its logs, and report the cause. Your coding agent reads the same runs through Shipfox and proposes changes to your workflows, such as a fix or a different model for a step. You review each change as a pull request.

Start a workflow from your tools, and let agents use them.

A workflow can start from many sources: a ticket, an alert, a chat message, a failed check, or a schedule. During the workflow, agents can read and write in your other tools, and you give this access one step at a time. Shipfox is not limited to where you store your code. You can connect a new tool in a few minutes.