Put an agent inside your app

Use Codex SDKs for background jobs, or app-server for a product with ongoing conversations, streamed progress and approval controls.

What this stack does

A task interface with a working agent

Components and their roles

How to get started

1. Choose one bounded task and define which records and tools it may access.
2. Use an SDK for jobs, or app-server when your interface needs conversations, progress and approvals.
3. Enforce access in your app, test rejected actions and interrupted runs, then review the output before releasing it.

Limitations

This is an engineering recipe, not a finished app. Your application owns authentication, access control and business rules. The old codex mcp-server integration has been removed; use the current SDK or app-server documentation.

Costs and licensing

Open-source integration components; model access and application hosting have separate terms and costs.

Evidence level

Documentation reviewed · not hands-on tested. This is an editorial combination, not a packaged product or a benchmark result.

Sources

Content checked: 2026-11-04. This page reflects the current validated published catalog. Update method and live status ↗