agentstack-wrapper

Add agentstack-sdk to your existing dependency manifest, create a server wrapper with @server.agent() around your agent logic, and wire configuration through platform extensions. The skill's 11-step checklist covers dependencies, entrypoint, LLM wiring, forms, secrets, and output handling.

Use the Secrets extension to request credentials at runtime and pass them explicitly to client constructors, never via os.environ. Agent Stack runs multi-tenant infrastructure, so setting environment variables would expose one user's keys to other executions.

No. The wrapping constraints explicitly prohibit business-logic changes; only compatibility modifications are allowed. If a compatibility issue forces a logic change, the workflow requires stopping and requesting explicit approval with justification.

Yes, but filesystem reads must be replaced with platform file uploads using FileField forms and the File API, since local filesystem access is unavailable at runtime. Non-plaintext files like PDFs use platform text extraction with polling.

The wrapped agent requires Python 3.12 or higher but below 3.14, and the interpreter must be actively selected in the environment, not merely installed. The readiness check fails otherwise and asks the user to fix it.

Do not use it for non-Python runtimes or for building a new agent from scratch; it targets migrating existing Python or framework-based agents. Containerization and auth setup are also out of scope unless explicitly requested.