Start a new application
Generate APEXlang from a blank app or customer CRM template, then adapt it to your requirements.
APEXREST FOR CODEX / OPEN-SOURCE PLUGIN
Create and change Oracle APEX applications in your Codex conversation. APEXREST brings the APEX tools, source checks and controlled imports into the same workflow.
You describe. Codex builds.APEXREST / ORACLE APEX
Illustrative workflow. No live execution.
01 / EVERYDAY APEX WORK
For APEX developers and teams building business applications on Oracle Database: a new app, an existing page, a dashboard or a change that needs checking.
Generate APEXlang from a blank app or customer CRM template, then adapt it to your requirements.
Export into a new project while preserving Oracle IDs and application metadata. Keep the source in version control.
Update forms, reports and shared components with changes scoped to your request.
Use real database queries, native APEX regions and filters that submit values and refresh the relevant content.
Check the named target, bind the plan to the reviewed source and back up an existing application before import.
Run the configured SQL, API or browser checks. Inspect diagnostics and repair failures with the evidence available.
02 / WHY APEXREST
APEXREST gives Codex specialist skills and tools for Oracle APEX. The application definition lives in readable .apx files; Oracle SQLcl checks it before an authorized import.
Keep the request, source changes and verification in one conversation.
How Oracle APEX worksRetrieve the relevant syntax and component guidance instead of loading the whole reference into every exchange.
Project summaries, metadata batches and programmatic job waiting help avoid repeated discovery and oversized tool replies.
Use a saved direct SQLcl connection or ORDS over HTTPS when the database listener is unavailable.
Oracle APEX supplies forms, reports, authentication and workflow on Oracle Database: a production-grade foundation for your application.
03 / THE WORKFLOW
Add an order status report. Preserve the existing pages and authentication. Import into the named test app and verify the filter.
Describe the change and name the project and environment. Codex checks the available app and database context.
Create or adopt the application, then make bounded changes in APEXlang. Keep schema and data migrations versioned alongside the app.
Run the relevant source and compiler checks. The deployment plan records the source, toolchain and target.
Your request to update an identified development or test app can authorize that scoped import. An existing app is backed up first.
After import, run the configured tests and relevant browser checks. Report failures and missing checks so you can assess the result.
Production requires externally signed approval on a protected runner. AI output still needs review and testing; compiler validation alone does not prove runtime correctness.
04 / YOUR WAY OF WORKING
Start with the Codex conversation you already have. Enable a reviewed team only when you want separate agents for the work.
Single mode works directly in the open conversation, using its model and permissions. It starts no extra agent and opens no panel automatically.
Enable Agent team in Settings to use separate developer sessions, manager code review, independent QA and final manager review.
05 / GET STARTED
BETA · 0.4.0-beta.1Install the CLI. Register the plugin. Start with a setup check.
The public npm package includes the runtime and resources. Use Node 24 LTS and a Codex host with native plugin support.
Run the commands shown here. npm installs the CLI; plugin registration is the next step.
Choose Install tools for missing dependencies, review the Oracle terms, then choose Install plugin.
Restart Codex, open a new task and ask APEXREST to check your setup before your first application change.
A separate guide covers command-line tools with ORDS over HTTPS. Native Cloud plugin discovery, MCP and panel support are not established; the full Cloud workflow still needs end-to-end verification.
Read the Cloud setup guideVersion 0.4.0-beta.1 is published on npm. The project records local tests, native-host checks and Oracle evidence separately. Integration, recovery and platform gaps remain before a stable release.
Review verification statusYOUR NEXT APEX CHANGE
Start with a development or test application, describe the change and let APEXREST guide the source checks, authorized import and verification.
Install the plugin Discuss your project ↗