Documentation
Build with agents
Give a coding agent one task, the relevant code, and checks to run.
Give the agent the application repository and one concrete user outcome.
Read its AGENTS.md, composer.json, and the code that handles the task.
Find the operation that owns the rule before changing HTTP handlers or templates.
- Reproduce the requested behavior with a small input.
- Find where permissions are checked and where data is stored or changed.
- Change the owning operation and its callers together.
- Test successful, denied, and malformed calls.
- Run the application's check command and inspect the actual result.
- Report the changed behavior, checks, and remaining limits.
The first HTTP application provides a runnable entry point
and response checks. Compose features builds operations with
permissions in the application's own namespace. Use the HTTP reference
to look up request and response behavior. The framework's development tools and
composer check script are not inherited by applications through Composer.
Stage does not require a model vendor, subscription, or autonomous runtime.
When exposing an operation to a remote agent, authenticate its credential on the server. Grant only the permissions needed for its task. Apply resource authorization inside the operation. A tool description, prompt, or caller- supplied permission list is not evidence of authority.
Version and source
Examples use Stage 0.1.5. Framework guide.