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, source 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 an existing application before import.

06 / VERIFY

Test and diagnose

Run the configured SQL, API or browser checks. 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

Component and pattern catalogs
Offline catalogs cover 109 component families and 58 reusable UX patterns with compiler-checked APEXlang recipes. Your agent 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 1.3.0

One plugin. Two hosts.
A smaller, sharper surface.

The 1.3.0 redesign reduces the agent surface from 21 tools to 11 and from 14 skills to 5, adds Claude Code next to Codex and keeps every import behind an explicit, plan-bound grant.

01 / HOSTS

Codex and Claude Code

The same bundle carries a Codex manifest and a Claude Code manifest. The skills are host-neutral and the MCP server starts from the plugin directory, with no global registration.

02 / ENGINE

Persistent SQLcl engine

Offline compiler work runs on pooled SQLcl servers instead of one process per call. Validation returns structured diagnostics: file, line, column, type, valid values and a hint.

03 / SURFACE

Eleven tools, five skills

Project, reference, metadata, validate, ship, sync, test, browser, job, artifact and status. The tool catalog is about 12 KB, so less of each session goes to tool descriptions.

04 / SHIP

Plan, then apply

apexrest_ship plans first, then applies under a grant bound to your request, the project, the target and the plan digest. Progress is reported by phase; production targets are refused.

05 / SYNC

Working copies of existing apps

Keep a single-editor working copy of a development or test application: initialize, check status, refresh or invalidate, and import from frozen local source.

06 / SAFETY

Hardened delivery safeguards

Administrator-owned production trust, plans that expire after 30 minutes, owner-only backups and password files, and flat, uniquely versioned migrations. No service tables in your APEX schema.

VERIFIED LOCALLY SO FAR

1.3.0 passed its local unit, contract, installer and packaging checks. Connected Oracle imports, authenticated browser checks and live Codex or Claude Code sessions that call the tools are not yet recorded.

Release notes

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.
Run the relevant source and compiler checks. The deployment plan records the source, toolchain and target.
04
AUTHORIZE
Keep the target explicit.
Your request to update an identified development or test app can authorize that scoped import. An existing app is backed up first.
05
VERIFY
Check the running result.
After import, run the configured tests and relevant browser checks. Report failures and missing checks so you can assess the result.

PRODUCTION IS A SEPARATE GATE

Production requires externally signed approval on a protected runner. 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.
A panel 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
Set up 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
Codex or external verification browser

Read the development status

06 / GET STARTED

NPM LATEST · 1.3.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 reviewed SQLcl 26.1.2
An existing Oracle APEX 26.1+ target
A saved SQLcl connection or private ORDS credentials

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, 1.3.0 at the time of writing; pin it with [email protected]. The older 1.3.0-beta.1 under the beta tag keeps the previous 21-tool surface.

Using Codex Cloud?

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 guide

Released, with visible limits.

Version 1.3.0 is the npm latest release with the redesigned surface. Local checks passed; connected Oracle imports, authenticated browser checks and live Codex or Claude Code sessions that call the tools remain open, as do recovery and broader platform checks.

Review verification status

07 / DOCUMENTATION & SOURCE

Go deeper where
you need to.

apexrest / npm

STARTInstallation and first application GUIDESAll plugin documentation 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

Test and diagnose

APEX knowledge.Tools that check the work.

Component and pattern catalogs

Focused context, less repetition

Your database, your connection

A real application platform

One plugin. Two hosts.A smaller, sharper surface.

Codex and Claude Code

Persistent SQLcl engine

Eleven tools, five skills

Plan, then apply

Working copies of existing apps

Hardened delivery safeguards

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.A panel when you need it.