Ax Python Flow

AxFlow For Python

This skill helps an agent write Python code with the generated Ax package axllm. Use the generated package API, examples, and manifests; do not import TypeScript-only APIs unless you are editing the TypeScript package.

When To Use

• Compose generators, agents, and nested flows into a workflow graph.
• Reason about flow state, node inputs, returns, caching, and errors.
• Use generated package examples for flow graphs and provider-backed flows.

Package Facts

• Language: Python.
• Package: axllm.
• Package API docs: API.md and axir-api.json.
• Capability manifest: axir-capabilities.json.
• Runnable examples: examples/.
• Real network support: yes.
• Scripted no-key transport support: yes.
• Runtime profiles: javascript-quickjs, python-pyodide.

Core Pattern

from axllm import ax, flow

draft = ax("topicText:string -> draftText:string")
wf = (
    flow({"id": "docs.coreFlow"})
    .execute("draft", draft, {"reads": ["topicText"], "writes": ["draftResult", "draftText"]})
    .returns({"draftText": "draftText"})
)

More Patterns

Typed programs

Build each flow node from its own input/output contract.

classifier = ax('requestText:string -> route:class "support, sales, engineering"')
responder = ax("requestText:string, route:string -> responseText:string")

Class decision

Declare reads and writes so the responder waits for the typed route.

branch_flow = (
    flow({"id": "docs.branchFlow"})
    .execute("classifier", classifier, {"reads": ["requestText"], "writes": ["classifierResult", "route"]})
    .execute("responder", responder, {"reads": ["requestText", "route"], "writes": ["responderResult", "responseText"]})
    .returns({"route": "route", "responseText": "responseText"})
)

Fan-out and join

Independent reads place research and audience analysis in one planner group. Owned clients and programs run concurrently; unsupported custom workers use a traced serial fallback.

parallel_flow = (
    flow({"id": "docs.parallelFlow"})
    .execute("research", research, {"reads": ["topicText"], "writes": ["researchResult", "factList"]})
    .execute("audience", audience, {"reads": ["topicText"], "writes": ["audienceResult", "audienceAngle"]})
    .execute("join", join, {"reads": ["factList", "audienceAngle"], "writes": ["joinResult", "briefText"]})
    .returns({"briefText": "briefText"})
)

Draft, critique, revise

A linear refinement pipeline makes each dependency explicit.

refine_flow = (
    flow({"id": "docs.refineFlow"})
    .execute("draft", draft, {"reads": ["topicText"], "writes": ["draftResult", "draftText"]})
    .execute("critique", critique, {"reads": ["draftText"], "writes": ["critiqueResult", "critiqueText"]})
    .execute("revise", revise, {"reads": ["draftText", "critiqueText"], "writes": ["reviseResult", "revisedText"]})
    .returns({"revisedText": "revisedText"})
)

Run a flow

Forward accepts the provider client and the public flow inputs.

output = parallel_flow.forward(client, {"topicText": "Typed LLM workflows"})

Start from the complete programs under examples/, then browse the larger gallery at https://axllm.dev/python/subsystems/flow/.

Astra Session Work

Select gpt-6-astra through the ordinary OpenAI factory. The adapter chooses Responses automatically; existing model defaults are unchanged. Use low reasoning and standard processing. Portable minimal reasoning maps to low; none is rejected. EU residency does not support priority processing.

Keep applications on their generation, agent, and flow entrypoints. Declare only independent tools as background; ordinary and imported MCP tools stay blocking unless the application explicitly changes their declaration. A promise, thread, or MCP hint is not a background declaration. Set asyncMode to off for the ordinary tool loop; chat-only services retain that loop automatically.

Declared-background native agent tools retain the imported MCP schema, handler, namespace, and raw result. Discovery must expose the tool before the model can call it. Invalid arguments are corrected before handler execution; the responder waits for the incorporated result. Native calls appear in action logs and must not be repeated through actor code. Owned child agents inherit selected MCP clients at delegation. Parent stages keep their own clients; none or an empty namespace list passes no parent clients. Explicit child context wins over inherited context. Each run refreshes protocol modules without serializing live client handles into model requests. Cancellation propagates through a delegated child into its pending MCP tool; completed child work is not replayed. Imported MCP tools forward cancellation to context-aware transports, including built-in HTTP. Custom transports using the older send method receive cancellation checks before and after their call; noncooperative work may finish later and its result is discarded. Cancellation does not undo an external action or replay a request. MCP host policy applies to native background calls too. Configure authorizeToolCall in Python, Go, and Java client options, or set_tool_authorizer on C++ and Rust clients before exposing their tools. The callback receives the client and call metadata; returning false denies the call before a tool request is sent. Use shared application policy state when permissions must change during a run.

Register child agents before running the parent: add_child_agent(namespace, name, child) in Python/C++, AddChildAgent in Go, addChildAgent in Java, and with_child_agent in Rust. Registered children are available automatically as namespaced actor calls, such as team.researcher({question}). Calls use discovery, validation, and invocation accounting. Child invocation remains serialized on the owning run thread and owns a separate conversation. Retained callbacks reject calls after the run closes. Controls target paths such as root/team.researcher/executor. Child results return through the parent invocation log, and parent usage includes a children section.

Attach the language-native run controller through forward options for steering, reasoning changes, cancellation, and lifecycle events. Queued and applied are different states. HTTP applies updates at a response boundary; an optional host WebSocket enables native steering. Do not manage response IDs, socket messages, or tool-result submission in application code.

A provisional answer is not successful completion while started tools remain unresolved. Cancellation closes the session, reports unresolved call IDs, and retains unresolved started calls in tool traces and native agent action logs; it cannot undo an external action. Handlers may cooperate through the invocation cancellation context. Late results from noncooperative work must not change a closed run or trigger replay.

Java, C++, and Rust WebSocket adapters track activity when frames arrive. Consuming buffered events does not reactivate a completed response. When no response is active, steering is queued for the next response; an active successor can still receive native steering. Observe lifecycle timing instead of assuming native application.

All five session adapters validate completed raw arguments against the shared Core validator before invoking handlers, including local references, unions, nested schemas, additional properties, and numeric/string/array constraints. Raw schema patterns use shared flagless ECMAScript semantics, including UTF-16, lookarounds, named captures, and backreferences. Invalid arguments enter correction; step exhaustion fails the run.

Independent flow nodes use owned program and client workers. Built-in providers, routers, and balancers supply factories; custom implementations without them run the entire group serially and emit a flow_parallel_fallback trace. Rust does not require Send/Sync on the existing client trait. Rust nested flows and custom AxExecutableProgram implementations use execute_program; an optional AxOwnedProgramFactory constructs state on its worker. Workers deliver events and results to the owner, which merges successful results in plan order. On group failure, cancellation preserves completed diagnostics and discards late deliveries.

Use the provider-backed Astra examples under src/examples/python/generation/, short-agents/, and flows/. All-five generated parity remains under verification in the shared-session AxIR backlog; do not infer full agent, parallel-flow, or transport parity from these examples alone.

Relevant API Surface

• Flow: flow, AxFlow, AxProgram.owned_worker_factory

Guardrails

• Start from package examples for exact native syntax before inventing a new call shape.
• Use provider-api examples only when the user explicitly has provider credentials available.
• Use no-key examples for deterministic local checks and provider request mapping.
• Treat AxIR as the source of generated package truth: if package docs disagree with source code, update the compiler and regenerate packages.
• Do not copy repo-maintainer skills from tools/*/skills/ into user packages.