Skip to main content
Use a catalog Tool when it fits your dependency. If not, your coding agent can author a private stateful Tool with explicit operations, schemas, starting records, and modeled behavior. Your application stays where it runs. The Tool runs in Firedrill.

​
Generate a small starting point

From your application’s repository:
This creates a new visible directory. It refuses existing destinations rather than overwriting your files. The supplied model implements list, get, and put for text records. Adapt it to the real dependency seam. Generating a scaffold does not publish source, allocate an instance, or prove fidelity.

​
Implement only the behavior you need

Declare operations and their schemas in the manifest. The source uses the supplied defineToolBehavior interface and controlled state APIs. Do not add filesystem access, network access, provider keys, ambient randomness, or wall-clock reads. The builder supplies the Tool-authoring module; you do not need to install a separate runtime into your application. Scheduled work and clock behavior must use the supported Tool capabilities. A familiar service name does not make an implementation equivalent to its complete public API. Record what your model supports and omits.

​
Publish selected files

After review, authenticate and select the project/environment, then:
Only the explicitly selected files are uploaded. Inspect the returned build status and diagnostics. A ready build is distinct from passing all intended behavioral cases. The conformance cases exercise only their supplied conditions. Include read/write behavior, empty state, invalid input, and denied operations that matter for your model; do not infer universal fidelity from a small fixture set.

​
Save data and use the Tool

Set FD_BUILD_ID from the ready publication response:
Select the saved build and compatible dataset, or pin those IDs in a simulation recipe. See starting data. Source and datasets stay private to their authorized scope. Public contribution is not required.

​
Recover publication

Preserve the exact selected files, scope, and original key after an uncertain reply. Reconcile that request rather than publishing a replacement. A deliberate source change is a different request and needs a different key.