APEXREST FOR CODEX AND CLAUDE CODE / OPEN-SOURCE PLUGIN

Oracle APEX.
Built with Codex
or Claude Code.

Create and change Oracle APEX applications in your Codex or Claude Code conversation. One plugin works in both. APEXREST brings the APEX tools, a local preview, compiler checks and controlled imports into the same workflow.

Install the plugin Read the docs

01Your current Codex or Claude Code session

02Readable, versioned source

03Imports within your approval

FROM REQUEST TO CHECKED SOURCE

You describe. Your agent builds.APEXREST / ORACLE APEX

Illustrative workflow. No live execution.

YOUR CODEX OR CLAUDE CODE CHATAPEXREST TOOLSORACLE APEXYOUR SCOPE · YOUR RELEASE DECISION

01 / EVERYDAY APEX WORK

Start from a task you already have.

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.

01 / CREATE

Start a new application

Generate APEXlang from a blank app or customer CRM template, then adapt it to your requirements.

02 / ADOPT

Work on the app you have

Export into a new project while preserving Oracle IDs and application metadata. Keep the source in version control.

03 / EDIT

Change pages and components

Update forms, reports and shared components with changes scoped to your request.

04 / DATA

Build useful dashboards

Use real database queries, native APEX regions and filters that submit values and refresh the relevant content.

05 / DELIVER

Plan and import a change

Check the named target, bind the plan to the reviewed source and back up the application. On APEX 26.2, import only the changed pages and shared components.

06 / VERIFY

Preview, test and diagnose

Open the pages locally before import, then check the imported result in your host’s in-app browser. Inspect diagnostics and repair failures with the evidence available.

02 / WHY APEXREST

APEX knowledge.
Tools that check the work.

APEXREST gives Codex and Claude Code 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 works

An offline component library
389 pinned Oracle 26.2 definitions, 269 compiler-checked component recipes, 58 UX patterns and 1,350 public Oracle pages, searchable in English or Ukrainian. Your agent reads before it writes and retrieves only what the change needs.
Focused context, less repetition
Project summaries, metadata batches and bounded job waiting help avoid repeated discovery and oversized tool replies.
Your database, your connection
Use a saved direct SQLcl connection or ORDS over HTTPS when the database listener is unavailable.
A real application platform
Oracle APEX supplies forms, reports, authentication and workflow on Oracle Database: a production-grade foundation for your application.

03 / WHAT'S NEW IN 2.5.0

See the page
before you import it.

Since 1.3.0, APEXREST has gained a database-free local preview, partial imports on APEX 26.2 and a much larger offline component library. Eleven tools and six skills, in Codex and Claude Code.

01 / PREVIEW

Run APEXlang without a database

apexrest_preview serves your pages from Node.js and SQLite with the genuine Universal Theme 26.2 templates and JavaScript. An .apx edit appears on the next reload, before anything is compiled or imported.

02 / COVERAGE

Most APEX UI, locally

Interactive reports and editable grids, forms and modal dialogs, faceted search, cards, template components, charts, calendars, maps and native page items. Whatever the preview does not simulate is listed in its diagnostics.

03 / LOGIC

Submits that behave like APEX

A PL/SQL subset interpreter runs processes, validations and computations. Each submit is one transaction that rolls back on error. A developer toolbar shows session state, the debug log and “view as” roles.

04 / APEX 26.2

Import only what changed

Update a page and its shared components without re-importing the whole application. APEXREST compares the baseline, your edits and a fresh export, keeps remote-only changes and blocks conflicts before writing. APEX 26.1 keeps full imports.

05 / LIBRARY

Read before writing

The library grew to 269 compiler-checked recipes, including 93 adapted from official Oracle sources, plus 1,350 public Oracle reference pages. Each recipe carries a data shape, adaptation rules and compiler evidence.

06 / SELECTION

Optional component ranking

With your own OpenAI key, the Decisions API can rank compatible catalog components before generation. It is off unless you configure it; search and read stay fully local, and your host model still writes the APEXlang.

A DESIGN AID, NOT ORACLE EVIDENCE

The preview never replaces compiler validation, an authorized import or browser checks on DEV, QA or TEST. Local repository checks pass; native Codex and Claude Code runs and connected Oracle checks are partial, and the latest repository review lists open defects.

Read the preview guide

04 / THE WORKFLOW

From a request
to a checked change.

EXAMPLE / EXISTING APP

Add an order status report. Preserve the existing pages and authentication. Import into the named test app and verify the filter.

01
SCOPE
Identify the application.
Describe the change and name the project and environment. Your agent checks the available app and database context.
02
BUILD
Edit readable source.
Create or adopt the application, then make bounded changes in APEXlang. Keep schema and data migrations versioned alongside the app.
03
CHECK
Validate before import.
Preview the pages locally, then run the Oracle compiler. The deployment plan records the source, toolchain and target.
04
AUTHORIZE
Keep the target explicit.
Your request to update an identified DEV, QA or TEST app authorizes that scoped import. The app is backed up first; on APEX 26.2 only the changed pages are imported.
05
VERIFY
Check the running result.
When you ask, your agent opens the imported pages in the host’s in-app browser. It reports what it checked, what failed and what it did not verify.

PRODUCTION STAYS YOURS

APEXREST imports only into DEV, QA and TEST targets; production targets always block deployment and restore. Release to production remains your decision. AI output still needs review and testing; compiler validation alone does not prove runtime correctness.

Read the deployment safeguards

05 / YOUR WAY OF WORKING

Your conversation.
Its status when you need it.

APEXREST works in the Codex or Claude Code conversation you already have. Your host keeps the model and permissions; APEXREST supplies the Oracle APEX operations.

HOW YOU WORKCHAT

Your current Codex or Claude Code session

Describe the change in the open conversation. Implementation starts there, with its existing context, model and permissions. No extra agents and no plugin startup call.

Describe the task or use $apexrest-work in Codex, /apexrest:apexrest-work in Claude Code
Set up tools and connections with the apexrest-setup skill
Continue edits in the same conversation

Read the chat workflow

WHEN USEFULSTATUS

The development status

Read the development status for project and connection settings, working copy, jobs, deployments and grants. It is read-only and cannot grant authorization or apply a plan.

Direct Oracle listener or ORDS HTTP(S)
Actual job results and diagnostics
Your host’s in-app browser for verification

Read the development status

06 / GET STARTED

PLUGIN SOURCE · 2.5.0

Bring APEX
into your agent.

Add the marketplace. Install the plugin. Start with a setup check.

The same plugin bundle installs into Codex (desktop and CLI) and Claude Code from the repository. Use Node 24 LTS.

Choose your host
Run the two commands for Codex or for Claude Code. Both register the same APEXREST plugin.
Let the plugin prepare the tools
On request, it previews and installs missing Java and SQLcl. You review the Oracle terms first; nothing creates a database or deploys an application.
Start a new session
Open a new Codex task or Claude Code session and ask APEXREST to check your setup before your first application change.

Full installation guide View source on GitHub

INSTALL THE PLUGINAPACHE-2.0

A short path to your first task.

# Codex
codex plugin marketplace add apexrest-dev/apexrest
codex plugin add apexrest-apex@apexrest

# Claude Code
claude plugin marketplace add apexrest-dev/apexrest
claude plugin install apexrest@apexrest

Both commands read the plugin bundle from the repository, so no build step is needed. Installing the plugin does not configure a connection or deploy an application.

YOUR FIRST REQUEST

Use APEXREST to check my setup. Report the compiler, connection and target checks that still need attention.

For connected Oracle work

Java 21 and SQLcl: 26.1.2 for APEX 26.1, 26.3 for APEX 26.2
An existing Oracle APEX 26.1 or 26.2 development or test application
A saved SQLcl connection or private ORDS credentials

The local preview needs neither Java nor SQLcl. Keep passwords in the local connection settings, outside chat prompts.

Prefer the command-line tool? Install from npm

npm install -g apexrest
apexrest --version
apexrest --help

This installs npm latest, [email protected] at the time of writing. Registry packages lag the repository: the local preview and the current surface are in the 2.5.0 plugin source, so install the plugin for them.

Using Codex Cloud?

A separate guide covers command-line tools with ORDS over HTTPS. Native Cloud plugin discovery and MCP support are not established; the full Cloud workflow still needs end-to-end verification.

Read the Cloud setup guide

Shipped, with visible limits.

The plugin source is 2.5.0; npm latest is 2.1.0. Local unit, contract, installer and packaging checks pass. Native Codex and Claude Code runs and connected Oracle checks are partial, and the open defects, recovery and broader platform checks are tracked upstream.

Review verification status

07 / DOCUMENTATION & SOURCE

Go deeper where
you need to.

apexrest / npm

BLOG / ORCL APEX

APEXREST Journal

Community news, hands-on resources, tools, events and worldwide job listings for Oracle APEX and PL/SQL developers.

Explore the journal

STARTInstallation and first application GUIDESAll plugin documentation PREVIEWLocal preview without a database 26.2Partial imports on APEX 26.2 CONNECTSQLcl and ORDS connections CONTROLImport and release safeguards STATUSEvidence and remaining checks CHANGESWhat changed in each release

YOUR NEXT APEX CHANGE

Bring a real task to your agent.

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 ↗

Oracle APEX.Built with Codex or Claude Code.

Start from a task you already have.

Start a new application

Work on the app you have

Change pages and components

Build useful dashboards

Plan and import a change

Preview, test and diagnose

APEX knowledge.Tools that check the work.

An offline component library

Focused context, less repetition

Your database, your connection

A real application platform

See the pagebefore you import it.

Run APEXlang without a database

Most APEX UI, locally

Submits that behave like APEX

Import only what changed

Read before writing

Optional component ranking

From a requestto a checked change.

Identify the application.

Edit readable source.

Validate before import.

Keep the target explicit.

Check the running result.

Your conversation.Its status when you need it.