register_manifest() to declare more than a run shows, such as full tool schemas. The table shows what each integration records.
See the Manifests guide for the conceptual model.
decimalai.register_manifest()
Explicitly register an agent’s configuration for version tracking.
dict):
true only when a fresh manifest row was created. A re-register of an unchanged config dedups and returns false.decimalai.flush_manifest_for_ci()
Register the manifest as a regression-check candidate and write its ID for the next CI step to read. This is the helper your CI init script (typically init_for_decimal.py) calls under DECIMALAI_MODE=manifest_only, after building the agent. It requires agent_name.
chain= (below) or the explicit tools / prompts / models dicts, otherwise you register an empty manifest and every later PR diffs against nothing.
The manifest ID is written to (in order): the output_path= you pass, else $GITHUB_OUTPUT if set (appended as decimal_manifest_id=<id>, the standard GitHub Actions mechanism), else ./decimal_manifest_id.txt in the current directory. An explicit output_path therefore overrides the GitHub Actions handoff — the Action itself only auto-discovers $GITHUB_OUTPUT and ./decimal_manifest_id.txt, so if you write somewhere else, pass that ID to the Action’s candidate-manifest-id input yourself. The path actually used comes back as output_path in the return value.
You can also let flush_manifest_for_ci introspect a LangChain/LangGraph agent instead of passing component dicts:
What’s next
Evaluations
Push scores onto traces and read back the verdict.
Manifests guide
Conceptual deep-dive on what a manifest is and how diffs work.