Edit function files and dependencies

Where: Functions → select a function. The Files bar and code editor operate on its draft.

The selected function opens its default entry file in the editor.

Add and choose files#

Click + Add file and enter a relative path such as helpers/format.py. Select a file tab to edit it. Use File actions for Make default or Remove file as offered. The function must retain at least one source file.

Add file accepts a relative path for a supporting source file.

Keep imports consistent with the actual paths. Changing the default entry file does not rewrite the handler contract or import paths automatically. Preserve the correct handler/export shape for the chosen runtime language.

Add dependencies#

Open the function's edit/settings form and review Packages or Dependencies. Search or add the required package and its supported version specification. Do not add a package for a standard-library module. Save the configuration and test again after a dependency change.

Dependency availability and startup depend on the runtime configured by the installation. A code file that parses is not evidence that the runtime can install or import every requested dependency.

Use SDK helpers intentionally#

Open SDK reference when available to inspect current helper examples for ontology, AI, secret access, and the caller. Bind the corresponding resources in Access before invoking them. Copy the example for the chosen language rather than translating a method name by guesswork.

Verify changes#

Save, run a known input, inspect the output and logs, and reopen the function to confirm the edited files persisted. Test both the ordinary input and an input that exercises the supporting file or dependency. A successful earlier run does not cover a newly changed package or entry point.

When promoting a release, review the saved files and bindings together. Function users with Executor access should not need implementation visibility to run the active version.