Custom functions and agents
Turn recurring work into a capability of your system.
How it fits together.
A function connects inputs, behavior and a visible way to start it. AIOS creation options distinguish scheduled actions, manual functions and agents. Actual execution follows configured triggers; a function can also gain a schedule later. Its interface can include a name, icon, button text and input dialog.
Assignments determine which models or individual objects offer a function. Manually executable functions appear in their Actions menu. A function with input fields opens a dialog; without them, it can start immediately. The associated run keeps work and results together. Requested agent approvals are shown inside the flow.
Step by step in AIOS
Open Settings → Capabilities at personal or organization level.
Choose scope according to who should use the capability. Personal and organization configuration are displayed separately; background capabilities belong to the organization.
Choose Functions, Agent, Skills or Models for the relevant configuration.
Function creation offers scheduled actions, manual functions and agents. A manually started draft is a useful first controlled workflow.
Define the function’s inputs and behavior. Decide which objects or models should have access to it.
Describe inputs and expected output concretely. Assign the function to appropriate models or objects and choose clear button text. The sample prompt uses no placeholder or API syntax.
Open an eligible object and choose the function under Actions. Supply any requested values and run the function.
Manually executable functions appear in the assigned object’s Actions menu. Input fields open a dialog; a function without inputs may start immediately.
Inspect the run and its result. Further steps follow the configured tools and approvals.
Compare the result, sources and open questions. A requested approval appears inside the flow and stays linked to the run. The prompt alone does not replace permission or tool configuration.
AIOSAn example for your work.
Prepare a meeting with the selected contact. Use the linked project brief and explicitly attached documents.
Produce: 1. five supported facts, 2. three agenda topics, 3. open questions, 4. missing information.
Identify the source for each fact. Do not invent information. Create a draft; do not send a message or change contact fields.Use this prompt as a starting point for a manually started function. Attach the required sources and review the first draft.
Parts of a function
| Area | Meaning in daily work |
|---|---|
| Trigger | Determines when work starts, for example manually or on a schedule. |
| Inputs | Values that can be requested in a dialog before execution. |
| Assignment | Determines which objects or models offer the function. |
| Interface | Name, icon, button text and dialog presentation. |
| Run and approval | Execution and results remain in context; requested approvals appear in the flow. |
If something does not work.
- The function is absent from Actions: Check object/model assignment and whether it is manually executable.
- The function starts without a dialog: It may have no input fields, in which case direct execution is expected.
- The run is waiting: Check the flow for a requested approval and read its decision context.