Published in Factory API and automation
Agent Pipeline Configuration
Every ticket runs as a graph of nodes, and each node kind runs on a fixed model chain (see Pipeline permutations). There are no per-phase model pickers. The Model preferences panel, in the Settings tab of a project, sets the defaults new tickets start with.
Routing mode
Routing mode (default for new tickets) has two options:
- Cost-optimized — holds quality while optimizing for cost. This is the default.
- Fast and best — fastest strong models on the fastest providers, with no regard to cost.
A ticket can pick the other mode when it is created. A node-level model pin in the ticket text is the only per-model override.
Ticket budget cap
Default ticket budget cap is the most a single ticket may spend before it pauses for your approval. Leave it blank, or click Use platform default, to use the platform default. The panel shows the effective cap and whether it comes from the platform default or your project override.
A lower cap means more tickets pause for approval; a higher cap means fewer pauses but more unattended spend per ticket.
Builder drafts
The same panel sets Sleep after this many idle minutes for Builder sandboxes (default 15 minutes) and a Monthly Builder budget.
Research and image tools for the AI Engineer lets the AI Engineer search the web, read web pages and make images while it works on your app. Each search, page and image uses credits. It is on for every new project. A project you created earlier keeps the setting it has now. To turn it off for one project, switch it off on that project’s settings page. It stays off until you turn it back on.
Ready to build it?
Tell Chipp what you want. Start free, or book a session and build it with our team.