Now for any agent

Synthex was written for Claude Code and is still developed and used there first. Starting with Synthex 1.0, the same command and specialist workflows are also available to Codex CLI, Gemini CLI, OpenCode, and other coding agents that support Agent Skills. One set of reviewed Markdown; no copied prompts to keep in sync.

#Choose your installation

All four harnesses are mechanically tested against the published skill inventory. The harness chooses its own interface; the workflow and specialist source are shared.

#Claude Code

Claude Code remains Synthex's home and has the fullest native experience, including namespaced slash commands, plugin agents, hooks, and native looping.

Run these inside Claude Code:

/plugin marketplace add bluminal/lumenai
/plugin install synthex

Then, in the repository you want Synthex to manage:

/synthex:init

See Getting started for the first delivery loop.

#Codex CLI

Codex installs the same marketplace and plugin through its CLI:

codex plugin marketplace add bluminal/lumenai
codex plugin add synthex@lumenai

Start a new Codex session after installation. Codex exposes every Synthex command and specialist as a skill. Invoke one explicitly, for example:

$init
$review-code
$architect

Or open /skills and select the workflow you need. The wrappers are deliberately thin: they load the corresponding canonical file in Synthex's commands/ or agents/ directory.

#Gemini CLI

Gemini CLI uses its workspace Agent Skills installation. From the project root, make a temporary source checkout, install each Synthex skill, and copy the small shared-support bundle it reads:

git clone --depth 1 --filter=blob:none --sparse https://github.com/bluminal/lumenai.git .synthex-source
git -C .synthex-source sparse-checkout set plugins/synthex
mkdir -p .gemini
cp -R .synthex-source/plugins/synthex/{agents,commands,config,scripts} .gemini/
for skill in .synthex-source/plugins/synthex/skills/*; do
  gemini skills install "$skill" --scope workspace --consent
done

Use Gemini normally and name the workflow when it helps, such as “use Synthex's review-code skill.” Run gemini skills list to inspect the installed inventory. Keep the source checkout to repeat the install when you update, or remove it after installation; add .synthex-source/ to your .gitignore if you do not want it tracked. If .gemini/ already contains project-managed files, merge the agents/, commands/, config/, and scripts/ directories deliberately rather than overwriting them.

#OpenCode

OpenCode discovers project-local Agent Skills under .agents/skills. From the project root, create the same temporary source checkout and place the complete portable bundle in .agents:

git clone --depth 1 --filter=blob:none --sparse https://github.com/bluminal/lumenai.git .synthex-source
git -C .synthex-source sparse-checkout set plugins/synthex
mkdir -p .agents
cp -R .synthex-source/plugins/synthex/{skills,agents,commands,config,scripts} .agents/

Start OpenCode in that project and ask for a named Synthex workflow, for example “use the Synthex write-implementation-plan skill.” opencode debug skill lists the skills OpenCode discovers. Commit .agents/ when you want the project to carry a reproducible, shared Synthex installation; keep .synthex-source/ ignored or remove it when you no longer need it. If .agents/ already contains project-managed files, merge the copied directories deliberately rather than overwriting them.

#Your AGENTS.md still belongs to you

AGENTS.md is where a project records its own conventions, architecture, test commands, and guardrails. Synthex does not overwrite or replace it. Agent Skills hold reusable workflows; AGENTS.md supplies the project-specific context when your harness honors that convention. If your harness uses a different instruction-file convention, keep using it alongside Synthex.

#What is shared—and what stays native

commands/*.md and agents/*.md are the behavioral source of truth. Generated skills/*/SKILL.md entrypoints carry only discovery metadata and instructions to load those canonical files. Editing a workflow therefore changes it for every supported harness.

Claude Code-only primitives remain Claude Code-only: its slash-command UI, plugin hooks, native looping implementation, and Task primitive have no universal equivalent. On another harness, Synthex preserves the workflow's intent and uses that harness's closest available skills and delegation mechanisms. Check the relevant harness documentation for its own authentication, model, and permission setup.

#Another Agent Skills host

If your coding agent supports project or workspace Agent Skills, it can use Synthex's portable bundle. Put skills/ and its sibling agents/, commands/, config/, and scripts/ directories under the host's documented skills root, preserving that layout. The relative links inside each SKILL.md then resolve to the shared canonical source.

Support for an additional harness is accepted when its clean install, full skill discovery, reference handling, and mechanical skill activation have been verified in Synthex's isolated compatibility suite. See the Synthex source to contribute one.

#Next

• Getting started — Claude Code's native first-delivery walkthrough
• Plugin architecture — the shared source and generated skill layer
• Configuration — configure a Synthex project, regardless of harness