ax-cpp-agent-rlm

Write C++ axllm code implementing AxCodeRuntime loops and session flows.

2.9k|186|Updated Feb 23, 2023

Search Tags:#runtime #c++#sessions #rlm #agent-loops #axllm

Ready to run

npx skills add https://github.com/ax-llm/ax --skill ax-cpp-agent-rlm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ax-cpp-agent-rlm
Source: https://github.com/ax-llm/ax/tree/main/website/static/cpp/.well-known/agent-skills/ax-cpp-agent-rlm
Command: npx skills add https://github.com/ax-llm/ax --skill ax-cpp-agent-rlm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers write correct C++ integrations for Ax-generated agent runtime loops, session handling, and runtime envelopes without drifting into TypeScript-only patterns.

Core Features & Use Cases

C++ Package Guidance: Use the generated axllm package API for agents, sessions, and runtime profiles.
Runtime Loop Wiring: Implement AxCodeRuntime and AxCodeSession flows, including ProcessCodeRuntime when an actor-code session needs a concrete execution path.
Practical Use Case: Build a native C++ agent that follows the generated package contract, runs against real network providers or no-key local checks, and stays aligned with AxIR-generated truth.

Quick Start

Ask for a C++ axllm implementation that uses the package examples and API docs to build an AxCodeRuntime session for an agent loop.

Frequently Asked Questions about ax-cpp-agent-rlm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I implement agent runtime loops in C++ using the axllm package?▼

Implement C++ agent runtime loops by using the axllm package API to construct AxCodeRuntime sessions and wire executor loops that follow AxIR-aligned execution paths. You must supply package examples and capability manifests to guarantee the generated code matches native C++ contracts instead of TypeScript-only call shapes.

How does ProcessCodeRuntime work within an AxCodeSession?▼

ProcessCodeRuntime supplies a concrete execution path within an AxCodeSession when an actor-code session needs to run against real network providers or local no-key checks. It operates inside a runtime envelope that keeps execution aligned with generated AxIR truth and provider-aware constraints.

Can I use optional runtime profiles with AxCodeRuntime in C++?▼

Yes, you can apply optional runtime profiles to AxCodeRuntime sessions in C++ to configure provider-aware execution. The axllm package API supports these profiles to help native C++ agents run against specific network providers or local checks while maintaining AxIR alignment and generated package contracts.

Why does my generated C++ agent code drift into TypeScript-only call shapes?▼

Generated C++ agent code drifts into TypeScript-only call shapes when guardrails are not applied to keep packages aligned with AxIR. You must enforce capability manifests and use the generated package API to prevent incorrect call shapes that do not match native C++ integration requirements.

What do I need to set up before building C++ AxCodeRuntime sessions?▼

Before building C++ AxCodeRuntime sessions, you need package examples, capability manifests, and guardrails prepared. These inputs ensure the generated axllm package APIs align with AxIR and provide the correct contracts for native C++ integration of agent and session workflows without TypeScript drift.

Are there limitations when using axllm for native C++ agent loops?▼

The main limitation is the strict requirement to avoid TypeScript-only patterns; axllm native C++ agent loops must follow generated package contracts and AxIR truth. Without proper capability manifests and guardrails, provider-aware execution and session handling may fail to integrate correctly into the runtime envelope.