NotesAPEXlangAPEXSQLclOracle AI World

Oracle and OpenAI's App Composer supports APEXlang. You don't need App Composer to start

App Composer supports APEXlang, but you can start now: since APEX 26.1, Codex or Claude Code can edit your app as text, gated by SQLcl's apex validate.

At Oracle AI World, Oracle and OpenAI announced App Composer: you build apps with Codex, and Oracle manages deployment and operations on OCI. One line in Oracle's announcement matters to every APEX team: App Composer supports APEXlang.

You don't need App Composer to use APEXlang. It shipped with APEX 26.1 as a readable text format for your app, and the agent workflow works today.

The setup Oracle's APEX team documents

  1. Install the Oracle SQL Developer extension for VS Code and connect to a schema on APEX 26.1. Add the EMP/DEPT sample dataset from SQL Workshop.
  2. Add a coding agent, such as Codex or Claude Code.
  3. In SQLcl (26.1.2 or later), run skills sync -skill-name apex,db to install Oracle's APEX and database skills.
  4. In the agent's instruction file (AGENTS.md or CLAUDE.md), tell it where SQLcl is installed. Keep passwords and connection details out of project files.
  5. Generate a starter app, import and run it, then prompt for a new page and re-import.

Make validation the gate

apex validate in SQLcl compiles the APEXlang source and reports syntax and compilation errors, without a database connection. Import only after it validates cleanly and a person has reviewed the diff.

Takeaway: treat your APEX app like code. Keep the APEXlang source in Git, let the agent propose changes, and start with one page. The agent and its LLM aren't included with APEX; you set them up separately, and they may cost extra. Sources: Oracle and OpenAI announcement, Getting Started with Oracle APEX Development in VS Code, Using APEXlang with AI coding agents.

Get the Oracle + AI digest

One email when a new tested guide, template or APEX release note lands — English or Arabic. No spam; unsubscribe anytime.

← All notes