Getting started

Set up Codex

Add the marketplace to make its plugins available. Install the ones you want, whenever you need them.

Your terminal shell

Compatibility and verification

Verification pending

The supplied screenshots show the Add a marketplace menu and its source fields. A complete installation check in this interface is still awaiting confirmation; the screenshots do not establish that a plugin was installed or activated.

Recorded: 2026-09-30

Supporting documentation

Add the marketplace in Codex

Open Plugins, then choose Add → Add a marketplace. The Source field accepts a GitHub repository, Git URL, or local folder.

Leave Git ref and Sparse paths empty to use the repository defaults and the complete marketplace. The grey examples in those fields are placeholders, not values you need to enter.

For this target, enter https://github.com/Fayegram-AI/plugin-market.git in Source.

Select Add marketplace. Once the source is available in Plugins, browse its entries and install the plugins you want. If the source cannot be added, use the official documentation linked below.

Codex Add menu with the Add a marketplace action. — Add → Add a marketplace

Codex Add plugin marketplace dialog with Source, Git ref, and Sparse paths fields. — The marketplace source dialog

Official OpenAI marketplace documentation

Requirements

Install Codex and sign in before running skills. Use the official documentation if the application is not yet available.
Check the chosen plugin's requirements; some skills need additional tools or runtimes.

Compatibility and verification

Documented procedure

Git syntax is documented and confirmed by CLI help. A complete Git installation has not been newly verified for this guide.

Recorded: 2026-09-30

Supporting documentation

Requirements

Install Codex and sign in before running skills. Use the official documentation if the application is not yet available.
Check the chosen plugin's requirements; some skills need additional tools or runtimes.
Use PowerShell on Windows or Bash/zsh on macOS/Linux. Interactive slash commands are entered inside the application.
Git and access to the configured repository are required. Registration can run from any directory; it fetches the source for you.

Add Faye Plugin Market

Run this once for the selected source. If the same source is already registered, reuse it. Adding a marketplace makes its plugins available to choose; it does not install them all.

codex plugin marketplace add https://github.com/Fayegram-AI/plugin-market.git

codex plugin marketplace add https://github.com/Fayegram-AI/plugin-market.git

What you should seeThe source is registered. Its native marketplace identity is faye-plugin-market.

Available plugins

Once the marketplace is added, you can stop here or install any of these plugins. Adding the marketplace does not install every plugin.

Faye Coding Assistantv0.1.0-beta.7Focused, scope-preserving coding skills.

Install Faye Coding Assistant only if you want its skills. Review any permission or trust prompts shown by the application.

codex plugin add faye-coding-assistant@faye-plugin-market

codex plugin add faye-coding-assistant@faye-plugin-market

What you should seeFaye Coding Assistant appears in the installed plugin list. Compare its version with 0.1.0-beta.7 shown by this marketplace.

Explore Faye Coding Assistant skills Set up with an agent

Faye Image Utilityv0.1.0-beta.6Image auditing, editing, conversion, and rating estimates.

Install Faye Image Utility only if you want its skills. Review any permission or trust prompts shown by the application.

codex plugin add faye-image-utility@faye-plugin-market

codex plugin add faye-image-utility@faye-plugin-market

What you should seeFaye Image Utility appears in the installed plugin list. Compare its version with 0.1.0-beta.6 shown by this marketplace.

Explore Faye Image Utility skills Set up with an agent

Faye UI System Engineerv0.1.0-beta.4Web UI design, implementation, review, and inspection.

Install Faye UI System Engineer only if you want its skills. Review any permission or trust prompts shown by the application.

codex plugin add faye-ui-system-engineer@faye-plugin-market

codex plugin add faye-ui-system-engineer@faye-plugin-market

What you should seeFaye UI System Engineer appears in the installed plugin list. Compare its version with 0.1.0-beta.4 shown by this marketplace.

Explore Faye UI System Engineer skills Set up with an agent

Confirm installation and start a new session

Check the plugins you selected are installed and enabled where the application exposes that state. The list command below is a quick confirmation, not a test of every skill.

Start a new Codex session, open its skill picker or Plugins interface, and choose a task from the installed plugin's skill guides. Read that skill's inputs and requirements before sending your request.

Codex skill requests may use $skill-name. Copy the example from the selected skill's guide, including any explicit invocation it requires.

codex plugin list --marketplace faye-plugin-market

codex plugin list --marketplace faye-plugin-market

What you should seeYour selected plugins are installed and their applicable skills can be found or explicitly invoked in a fresh session.

Other ways to install

Check an existing installation

Use this before adding a second source or when setup reports that the plugin already exists. Compare the names and source locations; reuse a matching installation.

codex plugin list --marketplace faye-plugin-market

codex plugin list --marketplace faye-plugin-market

codex plugin marketplace list

codex plugin marketplace list

What you should seeThe intended source and installed package are identified without removing other registrations.

Manage later

Refresh the Git marketplace

Refresh the source when you want to check for new package versions. Compare installed versions afterward; refreshing the catalog alone is not evidence that each installed plugin was updated.

codex plugin marketplace upgrade faye-plugin-market

codex plugin marketplace upgrade faye-plugin-market

What you should seeThe marketplace refresh succeeds; inspect the desired plugin's current and available version before changing its installation.

Enable or disable a plugin

Open /plugins inside Codex. Select an installed plugin and use the displayed enable/disable action. Disabling keeps the installation but makes its capabilities unavailable until enabled again.

/plugins

What you should seeThe plugin browser shows the intended enabled state.

Uninstall Faye Coding Assistant

Only use this when you intend to remove this plugin. It removes the selected installation and its capabilities; it is not a troubleshooting prerequisite. Leave other plugins and marketplace sources intact.

codex plugin remove faye-coding-assistant@faye-plugin-market

codex plugin remove faye-coding-assistant@faye-plugin-market

What you should seeFaye Coding Assistant is no longer listed as installed.

Uninstall Faye Image Utility

codex plugin remove faye-image-utility@faye-plugin-market

codex plugin remove faye-image-utility@faye-plugin-market

What you should seeFaye Image Utility is no longer listed as installed.

Uninstall Faye UI System Engineer

codex plugin remove faye-ui-system-engineer@faye-plugin-market

codex plugin remove faye-ui-system-engineer@faye-plugin-market

What you should seeFaye UI System Engineer is no longer listed as installed.

Add the marketplace with your agent

The agent checks existing registrations and adds or reuses Faye Plugin Market first. Installing plugins is optional: ask for the ones you want, or leave them for later.

Assistance uses supported commands. It does not include computer-use automation of graphical application controls. Interactive catalog and trust prompts remain yours to confirm.

Prompt for your agent

# Agent assistance: Codex · Terminal · Git repository

Target: release (public). Marketplace: faye-plugin-market.

## Request and operating rules

Help the user add or reuse Faye Plugin Market. Establish the requested application, source, and shell, then check existing registrations before making changes. Register the selected source before any optional plugin installation. Do not install plugins by default; ask which, if any, the user wants. A plugin mentioned in the request is an interest, not permission to skip marketplace registration or install every package.

If the user only wants to add the marketplace, confirm the registered source and stop. The plugin installation, fresh-session discovery, and later-management sections apply only when the user requests those actions.

This document includes the selected procedure, marketplace identity, repository address where configured, available package identities, and expected versions. You can begin from these embedded facts without opening the website. The linked setup.json, manifest.json, and registry are source metadata: inspect them in the actual local or fetched marketplace when available, rather than requiring access to a preview URL. Treat differences from these expected facts as a reason to explain the mismatch before making further changes. The relative links below are optional website navigation, not required downloads.

Use supported commands, not graphical computer-use automation. If the procedure requires an interactive catalog, trust prompt, or TUI action, explain what the user must do and wait. Do not silently replace an interactive marketplace workflow with direct CLI installation.

For a local source, first reuse, clone, or obtain the user's chosen copy as described below. These acquisition options are alternatives. Resolve the actual marketplace root and change the shell's working directory to it before running commands with . or ./plugins/. Confirm that folder contains plugins and .agents/plugins/marketplace.json. Replace example paths with the real path, preserving shell quoting. Check package identities and expected versions before registering or installing. Do not pull, overwrite, or replace an existing copy without the user's request.

If this platform only documents direct plugin installation, explain that limitation and ask before substituting it for marketplace registration. Pending procedures remain pending: do not invent commands or claim verification. Report the observed result and any action still required from the user.

## Selected repository procedure

# Codex: terminal setup — Git repository

[All procedures and operating rules](/marketplace/market-info/SETUP.md) · [Machine-readable setup](/marketplace/market-info/setup.json) · [Distribution manifest](/marketplace/market-info/manifest.json)

Procedure: `codex-terminal-git`. Status: `ready`. Marketplace: `faye-plugin-market`. Target: `release`.

Add the marketplace using its Git repository URL. The app fetches the source; no manual clone is needed.

## Before making changes

- Identify the selected product, interface, Git or local method, operating system/shell, and desired plugins. Ask only for missing decisions; reuse the user's existing authorization.
- Read this target's setup.json, manifest.json, and native registry. Use their actual marketplace identity, repository URL, available plugin IDs, versions, and skills. Do not borrow facts from another target.
- A route marked needs-input is not executable guidance. Describe the missing procedure and ask for the user's demonstration or confirmation. Never guess app controls or treat a placeholder as evidence.
- Inspect existing registrations and installed packages using supported read-only commands. Reuse a matching source and installed version. Explain conflicts before replacing anything.
- Choose the declared shell variant. Run only the selected route and plugins, using automation output flags where provided. Interactive slash commands belong in the product, not the operating-system shell.
- Keep authentication in the application's supported sign-in flow. Never ask for credentials in a prompt. Respect existing trust authorization; do not silently add automatic trust flags.
- Preserve unrelated settings and working installations. Do not clear caches, remove unrelated packages, rewrite global configuration wholesale, or weaken permissions to make setup pass.
- Verify installed identity, version, enabled state where exposed, and skill discovery. A zero exit code or copied files alone do not establish successful setup.
- Start or request a fresh session when needed. Run a functional skill request only if the user authorizes that execution; installation does not require a model call.
- Report the selected route, packages installed or reused, observed verification, and the next user action. Separate documented behavior, observations, and untested or blocked work.

- Install Codex and sign in before running skills. Use the official documentation if the application is not yet available.
- Check the chosen plugin's requirements; some skills need additional tools or runtimes.
- Use PowerShell on Windows or Bash/zsh on macOS/Linux. Interactive slash commands are entered inside the application.
- Git and access to the configured repository are required. Registration can run from any directory; it fetches the source for you.

## Selection and source facts

Source method: Git repository. Channel: public.

Repository: https://github.com/Fayegram-AI/plugin-market.git

Confirm the requested application, interface, source method, shell and plugins before changing anything. Example filesystem paths are placeholders: resolve the user's actual absolute path and never execute a placeholder path.

## Inspect first and reuse matching state

Use `codex plugin list --json` to inspect the existing installation. Read the installed entries and compare pluginId, marketplaceName, version, installed, and enabled where present.

Use `codex plugin marketplace list --json` to compare registered source locations. Reuse the intended source; ask about conflicting sources before replacing them.

## Install through the selected method

### Add Faye Plugin Market

Run this once for the selected source. If the same source is already registered, reuse it. Adding a marketplace makes its plugins available to choose; it does not install them all.

Add marketplace — PowerShell or Bash/zsh:

```text
codex plugin marketplace add https://github.com/Fayegram-AI/plugin-market.git --json
```

Expected: The source is registered. Its native marketplace identity is faye-plugin-market.

### If requested: Faye Coding Assistant

Identity: `faye-coding-assistant`; expected version: `0.1.0-beta.7`.

Install Faye Coding Assistant only if you want its skills. Review any permission or trust prompts shown by the application.

Install Faye Coding Assistant — PowerShell or Bash/zsh:

```text
codex plugin add faye-coding-assistant@faye-plugin-market --json
```

Expected: Faye Coding Assistant appears in the installed plugin list. Compare its version with 0.1.0-beta.7 shown by this marketplace.

### If requested: Faye Image Utility

Identity: `faye-image-utility`; expected version: `0.1.0-beta.6`.

Install Faye Image Utility only if you want its skills. Review any permission or trust prompts shown by the application.

Install Faye Image Utility — PowerShell or Bash/zsh:

```text
codex plugin add faye-image-utility@faye-plugin-market --json
```

Expected: Faye Image Utility appears in the installed plugin list. Compare its version with 0.1.0-beta.6 shown by this marketplace.

### If requested: Faye UI System Engineer

Identity: `faye-ui-system-engineer`; expected version: `0.1.0-beta.4`.

Install Faye UI System Engineer only if you want its skills. Review any permission or trust prompts shown by the application.

Install Faye UI System Engineer — PowerShell or Bash/zsh:

```text
codex plugin add faye-ui-system-engineer@faye-plugin-market --json
```

Expected: Faye UI System Engineer appears in the installed plugin list. Compare its version with 0.1.0-beta.4 shown by this marketplace.

## Confirm installation and start a new session

Check the plugins you selected are installed and enabled where the application exposes that state. The list command below is a quick confirmation, not a test of every skill.

Start a new Codex session, open its skill picker or Plugins interface, and choose a task from the installed plugin's skill guides. Read that skill's inputs and requirements before sending your request.

Codex skill requests may use $skill-name. Copy the example from the selected skill's guide, including any explicit invocation it requires.

List installed plugins — PowerShell or Bash/zsh:

```text
codex plugin list --marketplace faye-plugin-market --json
```

Expected: Your selected plugins are installed and their applicable skills can be found or explicitly invoked in a fresh session.

## Optional alternatives — do not run by default

### Check an existing installation

Use this before adding a second source or when setup reports that the plugin already exists. Compare the names and source locations; reuse a matching installation.

Installed plugins — PowerShell or Bash/zsh:

```text
codex plugin list --marketplace faye-plugin-market --json
```

Registered marketplaces — PowerShell or Bash/zsh:

```text
codex plugin marketplace list --json
```

Expected: The intended source and installed package are identified without removing other registrations.

## Later management — requires the corresponding user request

### Refresh the Git marketplace

Refresh the source when you want to check for new package versions. Compare installed versions afterward; refreshing the catalog alone is not evidence that each installed plugin was updated.

Refresh marketplace — PowerShell or Bash/zsh:

```text
codex plugin marketplace upgrade faye-plugin-market
```

Expected: The marketplace refresh succeeds; inspect the desired plugin's current and available version before changing its installation.

### Enable or disable a plugin

Open /plugins inside Codex. Select an installed plugin and use the displayed enable/disable action. Disabling keeps the installation but makes its capabilities unavailable until enabled again.

Inside Codex — enter inside the application:

```text
/plugins
```

Expected: The plugin browser shows the intended enabled state.

### Uninstall Faye Coding Assistant

Only use this when you intend to remove this plugin. It removes the selected installation and its capabilities; it is not a troubleshooting prerequisite. Leave other plugins and marketplace sources intact.

Uninstall selected plugin — PowerShell or Bash/zsh:

```text
codex plugin remove faye-coding-assistant@faye-plugin-market
```

Expected: Faye Coding Assistant is no longer listed as installed.

### Uninstall Faye Image Utility

Only use this when you intend to remove this plugin. It removes the selected installation and its capabilities; it is not a troubleshooting prerequisite. Leave other plugins and marketplace sources intact.

Uninstall selected plugin — PowerShell or Bash/zsh:

```text
codex plugin remove faye-image-utility@faye-plugin-market
```

Expected: Faye Image Utility is no longer listed as installed.

### Uninstall Faye UI System Engineer

Only use this when you intend to remove this plugin. It removes the selected installation and its capabilities; it is not a troubleshooting prerequisite. Leave other plugins and marketplace sources intact.

Uninstall selected plugin — PowerShell or Bash/zsh:

```text
codex plugin remove faye-ui-system-engineer@faye-plugin-market
```

Expected: Faye UI System Engineer is no longer listed as installed.

## Evidence boundary

documented; recorded 2026-09-30. Git syntax is documented and confirmed by CLI help. A complete Git installation has not been newly verified for this guide.

Source: https://learn.chatgpt.com/docs/developer-commands

Finish with what was installed or reused, actual verification observations, anything untested, and the next user action. Do not execute a skill or claim model/tool success unless that functional check was authorized and observed.

Read full instructions

Compatibility and verification

Verified locally

Local installation and one representative skill were checked on the recorded version. This does not certify every workflow, operating system, or app interface.

Recorded: 2026-09-27
Tested with: Codex CLI 0.155.0 on Windows

Supporting documentation

Requirements

Install Codex and sign in before running skills. Use the official documentation if the application is not yet available.
Check the chosen plugin's requirements; some skills need additional tools or runtimes.
Use PowerShell on Windows or Bash/zsh on macOS/Linux. Interactive slash commands are entered inside the application.

Prepare a local copy

Choose one option. These are alternatives; you do not need to do all three.

Use an existing copy

Find the marketplace folder already on your computer. It contains plugins and the hidden .agents/plugins/marketplace.json registry. A plugin folder inside plugins is not the marketplace root.

Keep this copy in a stable location. Do not overwrite it or change its Git branch just to follow this guide.

What you should seeYou know the full path to the marketplace root.

Clone the repository

Git must be installed. Run this from the parent folder where you want to keep the copy. faye-plugin-market is an example destination name; choose another unused name if needed.

If the destination already exists, use that copy or choose a different destination. Do not overwrite it. After cloning, use the full path to the new folder in the next step.

git clone https://github.com/Fayegram-AI/plugin-market.git faye-plugin-market

git clone https://github.com/Fayegram-AI/plugin-market.git faye-plugin-market

What you should seeA new local copy exists in the chosen destination.

Download and extract the repository

Open the repository to download a copy

Use its source archive download option, then extract the archive into a stable location. Open the extracted folder containing plugins and .agents/plugins/marketplace.json, not the archive or a surrounding downloads folder.

An extracted archive is a local copy without Git history; git pull cannot update it.

What you should seeThe extracted marketplace root is available on your computer.

Open the marketplace folder

Replace the entire quoted example path below with the full path to your marketplace root. Keep the quotes, especially when the path contains spaces. Choose the command for your terminal shell.

All following relative paths use this folder. The single dot means this marketplace root; ./plugins/<plugin-id> means one plugin folder inside it.

Set-Location -LiteralPath 'C:\path\to\Faye Plugin Market'

cd -- '/path/to/Faye Plugin Market'

What you should seeYour terminal is in the folder containing plugins and .agents/plugins/marketplace.json.

Add Faye Plugin Market

Run this once for the selected source. If the same source is already registered, reuse it. Adding a marketplace makes its plugins available to choose; it does not install them all.

Run this from the marketplace folder. Open PowerShell or Bash/zsh in your downloaded or cloned marketplace folder, or change to that folder before running this command. It is the folder containing plugins and .agents/plugins/marketplace.json. The dot (.) means your shell’s current folder.

codex plugin marketplace add .

codex plugin marketplace add .

What you should seeThe source is registered. Its native marketplace identity is faye-plugin-market.

Available plugins

Once the marketplace is added, you can stop here or install any of these plugins. Adding the marketplace does not install every plugin.

Faye Coding Assistantv0.1.0-beta.7Focused, scope-preserving coding skills.

Install Faye Coding Assistant only if you want its skills. Review any permission or trust prompts shown by the application.

codex plugin add faye-coding-assistant@faye-plugin-market

codex plugin add faye-coding-assistant@faye-plugin-market

What you should seeFaye Coding Assistant appears in the installed plugin list. Compare its version with 0.1.0-beta.7 shown by this marketplace.

Explore Faye Coding Assistant skills Set up with an agent

Faye Image Utilityv0.1.0-beta.6Image auditing, editing, conversion, and rating estimates.

Install Faye Image Utility only if you want its skills. Review any permission or trust prompts shown by the application.

codex plugin add faye-image-utility@faye-plugin-market

codex plugin add faye-image-utility@faye-plugin-market

What you should seeFaye Image Utility appears in the installed plugin list. Compare its version with 0.1.0-beta.6 shown by this marketplace.

Explore Faye Image Utility skills Set up with an agent

Faye UI System Engineerv0.1.0-beta.4Web UI design, implementation, review, and inspection.

Install Faye UI System Engineer only if you want its skills. Review any permission or trust prompts shown by the application.

codex plugin add faye-ui-system-engineer@faye-plugin-market

codex plugin add faye-ui-system-engineer@faye-plugin-market

What you should seeFaye UI System Engineer appears in the installed plugin list. Compare its version with 0.1.0-beta.4 shown by this marketplace.

Explore Faye UI System Engineer skills Set up with an agent

Confirm installation and start a new session

Check the plugins you selected are installed and enabled where the application exposes that state. The list command below is a quick confirmation, not a test of every skill.

Codex skill requests may use $skill-name. Copy the example from the selected skill's guide, including any explicit invocation it requires.

codex plugin list --marketplace faye-plugin-market

codex plugin list --marketplace faye-plugin-market

What you should seeYour selected plugins are installed and their applicable skills can be found or explicitly invoked in a fresh session.

Other ways to install

Check an existing installation

Use this before adding a second source or when setup reports that the plugin already exists. Compare the names and source locations; reuse a matching installation.

codex plugin list --marketplace faye-plugin-market

codex plugin list --marketplace faye-plugin-market

codex plugin marketplace list

codex plugin marketplace list

What you should seeThe intended source and installed package are identified without removing other registrations.

Manage later

Update a local copy later

Updating the source is separate from installing a plugin. git pull updates an existing Git checkout; it does not create one and cannot update an extracted archive.

Before updating a checkout, check its branch and local changes. For an archive, obtain a newer copy separately and compare versions. Do not overwrite the existing folder or change an installed plugin without deciding to update it.

What you should seeYou have identified the source and version you intend to use before making an update.

Enable or disable a plugin

Open /plugins inside Codex. Select an installed plugin and use the displayed enable/disable action. Disabling keeps the installation but makes its capabilities unavailable until enabled again.

/plugins

What you should seeThe plugin browser shows the intended enabled state.

Uninstall Faye Coding Assistant

codex plugin remove faye-coding-assistant@faye-plugin-market

codex plugin remove faye-coding-assistant@faye-plugin-market

What you should seeFaye Coding Assistant is no longer listed as installed.

Uninstall Faye Image Utility

codex plugin remove faye-image-utility@faye-plugin-market

codex plugin remove faye-image-utility@faye-plugin-market

What you should seeFaye Image Utility is no longer listed as installed.

Uninstall Faye UI System Engineer

codex plugin remove faye-ui-system-engineer@faye-plugin-market

codex plugin remove faye-ui-system-engineer@faye-plugin-market

What you should seeFaye UI System Engineer is no longer listed as installed.

Add the marketplace with your agent

The agent checks existing registrations and adds or reuses Faye Plugin Market first. Installing plugins is optional: ask for the ones you want, or leave them for later.

Assistance uses supported commands. It does not include computer-use automation of graphical application controls. Interactive catalog and trust prompts remain yours to confirm.

Prompt for your agent

# Agent assistance: Codex · Terminal · Local copy

Target: release (public). Marketplace: faye-plugin-market.

## Request and operating rules

Help the user add or reuse Faye Plugin Market. Establish the requested application, source, and shell, then check existing registrations before making changes. Register the selected source before any optional plugin installation. Do not install plugins by default; ask which, if any, the user wants. A plugin mentioned in the request is an interest, not permission to skip marketplace registration or install every package.

If the user only wants to add the marketplace, confirm the registered source and stop. The plugin installation, fresh-session discovery, and later-management sections apply only when the user requests those actions.

This document includes the selected procedure, marketplace identity, repository address where configured, available package identities, and expected versions. You can begin from these embedded facts without opening the website. The linked setup.json, manifest.json, and registry are source metadata: inspect them in the actual local or fetched marketplace when available, rather than requiring access to a preview URL. Treat differences from these expected facts as a reason to explain the mismatch before making further changes. The relative links below are optional website navigation, not required downloads.

Use supported commands, not graphical computer-use automation. If the procedure requires an interactive catalog, trust prompt, or TUI action, explain what the user must do and wait. Do not silently replace an interactive marketplace workflow with direct CLI installation.

For a local source, first reuse, clone, or obtain the user's chosen copy as described below. These acquisition options are alternatives. Resolve the actual marketplace root and change the shell's working directory to it before running commands with . or ./plugins/. Confirm that folder contains plugins and .agents/plugins/marketplace.json. Replace example paths with the real path, preserving shell quoting. Check package identities and expected versions before registering or installing. Do not pull, overwrite, or replace an existing copy without the user's request.

If this platform only documents direct plugin installation, explain that limitation and ask before substituting it for marketplace registration. Pending procedures remain pending: do not invent commands or claim verification. Report the observed result and any action still required from the user.

## Selected repository procedure

# Codex: terminal setup — Local copy

[All procedures and operating rules](/marketplace/market-info/SETUP.md) · [Machine-readable setup](/marketplace/market-info/setup.json) · [Distribution manifest](/marketplace/market-info/manifest.json)

Procedure: `codex-terminal-local`. Status: `ready`. Marketplace: `faye-plugin-market`. Target: `release`.

Add the marketplace from a local copy on your computer.

## Before making changes

- Identify the selected product, interface, Git or local method, operating system/shell, and desired plugins. Ask only for missing decisions; reuse the user's existing authorization.
- Read this target's setup.json, manifest.json, and native registry. Use their actual marketplace identity, repository URL, available plugin IDs, versions, and skills. Do not borrow facts from another target.
- A route marked needs-input is not executable guidance. Describe the missing procedure and ask for the user's demonstration or confirmation. Never guess app controls or treat a placeholder as evidence.
- Inspect existing registrations and installed packages using supported read-only commands. Reuse a matching source and installed version. Explain conflicts before replacing anything.
- Choose the declared shell variant. Run only the selected route and plugins, using automation output flags where provided. Interactive slash commands belong in the product, not the operating-system shell.
- Keep authentication in the application's supported sign-in flow. Never ask for credentials in a prompt. Respect existing trust authorization; do not silently add automatic trust flags.
- Preserve unrelated settings and working installations. Do not clear caches, remove unrelated packages, rewrite global configuration wholesale, or weaken permissions to make setup pass.
- Verify installed identity, version, enabled state where exposed, and skill discovery. A zero exit code or copied files alone do not establish successful setup.
- Start or request a fresh session when needed. Run a functional skill request only if the user authorizes that execution; installation does not require a model call.
- Report the selected route, packages installed or reused, observed verification, and the next user action. Separate documented behavior, observations, and untested or blocked work.

- Install Codex and sign in before running skills. Use the official documentation if the application is not yet available.
- Check the chosen plugin's requirements; some skills need additional tools or runtimes.
- Use PowerShell on Windows or Bash/zsh on macOS/Linux. Interactive slash commands are entered inside the application.

## Selection and source facts

Source method: Local copy. Channel: public.

Repository: https://github.com/Fayegram-AI/plugin-market.git

Confirm the requested application, interface, source method, shell and plugins before changing anything. Example filesystem paths are placeholders: resolve the user's actual absolute path and never execute a placeholder path.

## Inspect first and reuse matching state

Use `codex plugin list --json` to inspect the existing installation. Read the installed entries and compare pluginId, marketplaceName, version, installed, and enabled where present.

Use `codex plugin marketplace list --json` to compare registered source locations. Reuse the intended source; ask about conflicting sources before replacing them.

## Prepare the local copy — choose one option

These are alternatives, not consecutive steps. Reuse an appropriate existing copy before obtaining another. Resolve the actual marketplace root, check its registry identity and selected package manifests, and compare versions with this guide. Explain any mismatch before updating or replacing the source.

### Use an existing copy

Find the marketplace folder already on your computer. It contains plugins and the hidden .agents/plugins/marketplace.json registry. A plugin folder inside plugins is not the marketplace root.

Keep this copy in a stable location. Do not overwrite it or change its Git branch just to follow this guide.

Expected: You know the full path to the marketplace root.

### Clone the repository

Git must be installed. Run this from the parent folder where you want to keep the copy. faye-plugin-market is an example destination name; choose another unused name if needed.

If the destination already exists, use that copy or choose a different destination. Do not overwrite it. After cloning, use the full path to the new folder in the next step.

Clone into a new folder — PowerShell or Bash/zsh:

```text
git clone https://github.com/Fayegram-AI/plugin-market.git faye-plugin-market
```

Expected: A new local copy exists in the chosen destination.

### Download and extract the repository

Open the repository: https://github.com/Fayegram-AI/plugin-market

Use its source archive download option, then extract the archive into a stable location. Open the extracted folder containing plugins and .agents/plugins/marketplace.json, not the archive or a surrounding downloads folder.

An extracted archive is a local copy without Git history; git pull cannot update it.

Expected: The extracted marketplace root is available on your computer.

## Install through the selected method

### Open the marketplace folder

Replace the entire quoted example path below with the full path to your marketplace root. Keep the quotes, especially when the path contains spaces. Choose the command for your terminal shell.

All following relative paths use this folder. The single dot means this marketplace root; ./plugins/<plugin-id> means one plugin folder inside it.

Open your local copy — replace the example path

PowerShell:

```powershell
Set-Location -LiteralPath 'C:\path\to\Faye Plugin Market'
```

Bash/zsh:

```bash
cd -- '/path/to/Faye Plugin Market'
```

Expected: Your terminal is in the folder containing plugins and .agents/plugins/marketplace.json.

### Add Faye Plugin Market

Run this once for the selected source. If the same source is already registered, reuse it. Adding a marketplace makes its plugins available to choose; it does not install them all.

Add marketplace — PowerShell or Bash/zsh:

```text
codex plugin marketplace add . --json
```

Expected: The source is registered. Its native marketplace identity is faye-plugin-market.

### If requested: Faye Coding Assistant

Identity: `faye-coding-assistant`; expected version: `0.1.0-beta.7`.

Install Faye Coding Assistant only if you want its skills. Review any permission or trust prompts shown by the application.

Install Faye Coding Assistant — PowerShell or Bash/zsh:

```text
codex plugin add faye-coding-assistant@faye-plugin-market --json
```

Expected: Faye Coding Assistant appears in the installed plugin list. Compare its version with 0.1.0-beta.7 shown by this marketplace.

### If requested: Faye Image Utility

Identity: `faye-image-utility`; expected version: `0.1.0-beta.6`.

Install Faye Image Utility only if you want its skills. Review any permission or trust prompts shown by the application.

Install Faye Image Utility — PowerShell or Bash/zsh:

```text
codex plugin add faye-image-utility@faye-plugin-market --json
```

Expected: Faye Image Utility appears in the installed plugin list. Compare its version with 0.1.0-beta.6 shown by this marketplace.

### If requested: Faye UI System Engineer

Identity: `faye-ui-system-engineer`; expected version: `0.1.0-beta.4`.

Install Faye UI System Engineer only if you want its skills. Review any permission or trust prompts shown by the application.

Install Faye UI System Engineer — PowerShell or Bash/zsh:

```text
codex plugin add faye-ui-system-engineer@faye-plugin-market --json
```

Expected: Faye UI System Engineer appears in the installed plugin list. Compare its version with 0.1.0-beta.4 shown by this marketplace.

## Confirm installation and start a new session

Check the plugins you selected are installed and enabled where the application exposes that state. The list command below is a quick confirmation, not a test of every skill.

Start a new Codex session, open its skill picker or Plugins interface, and choose a task from the installed plugin's skill guides. Read that skill's inputs and requirements before sending your request.

Codex skill requests may use $skill-name. Copy the example from the selected skill's guide, including any explicit invocation it requires.

List installed plugins — PowerShell or Bash/zsh:

```text
codex plugin list --marketplace faye-plugin-market --json
```

Expected: Your selected plugins are installed and their applicable skills can be found or explicitly invoked in a fresh session.

## Optional alternatives — do not run by default

### Check an existing installation

Use this before adding a second source or when setup reports that the plugin already exists. Compare the names and source locations; reuse a matching installation.

Installed plugins — PowerShell or Bash/zsh:

```text
codex plugin list --marketplace faye-plugin-market --json
```

Registered marketplaces — PowerShell or Bash/zsh:

```text
codex plugin marketplace list --json
```

Expected: The intended source and installed package are identified without removing other registrations.

## Later management — requires the corresponding user request

### Update a local copy later

Updating the source is separate from installing a plugin. git pull updates an existing Git checkout; it does not create one and cannot update an extracted archive.

Before updating a checkout, check its branch and local changes. For an archive, obtain a newer copy separately and compare versions. Do not overwrite the existing folder or change an installed plugin without deciding to update it.

Expected: You have identified the source and version you intend to use before making an update.

### Enable or disable a plugin

Open /plugins inside Codex. Select an installed plugin and use the displayed enable/disable action. Disabling keeps the installation but makes its capabilities unavailable until enabled again.

Inside Codex — enter inside the application:

```text
/plugins
```

Expected: The plugin browser shows the intended enabled state.

### Uninstall Faye Coding Assistant

Only use this when you intend to remove this plugin. It removes the selected installation and its capabilities; it is not a troubleshooting prerequisite. Leave other plugins and marketplace sources intact.

Uninstall selected plugin — PowerShell or Bash/zsh:

```text
codex plugin remove faye-coding-assistant@faye-plugin-market
```

Expected: Faye Coding Assistant is no longer listed as installed.

### Uninstall Faye Image Utility

Only use this when you intend to remove this plugin. It removes the selected installation and its capabilities; it is not a troubleshooting prerequisite. Leave other plugins and marketplace sources intact.

Uninstall selected plugin — PowerShell or Bash/zsh:

```text
codex plugin remove faye-image-utility@faye-plugin-market
```

Expected: Faye Image Utility is no longer listed as installed.

### Uninstall Faye UI System Engineer

Only use this when you intend to remove this plugin. It removes the selected installation and its capabilities; it is not a troubleshooting prerequisite. Leave other plugins and marketplace sources intact.

Uninstall selected plugin — PowerShell or Bash/zsh:

```text
codex plugin remove faye-ui-system-engineer@faye-plugin-market
```

Expected: Faye UI System Engineer is no longer listed as installed.

## Evidence boundary

tested; recorded 2026-09-27 with Codex CLI 0.155.0 on Windows. Local installation and one representative skill were checked on the recorded version. This does not certify every workflow, operating system, or app interface.

Source: https://learn.chatgpt.com/docs/developer-commands

Finish with what was installed or reused, actual verification observations, anything untested, and the next user action. Do not execute a skill or claim model/tool success unless that functional check was authorized and observed.

Read full instructions

Set up Codex

Compatibility and verification

Add the marketplace in Codex

Agent assistance uses commands

Compatibility and verification

Add the marketplace in Codex

Agent assistance uses commands

Compatibility and verification

Add Faye Plugin Market

Available plugins

Confirm installation and start a new session

Check an existing installation

Refresh the Git marketplace

Enable or disable a plugin

Uninstall Faye Coding Assistant

Uninstall Faye Image Utility

Uninstall Faye UI System Engineer

Add the marketplace with your agent

Compatibility and verification

Prepare a local copy

Open the marketplace folder

Add Faye Plugin Market

Available plugins

Confirm installation and start a new session

Check an existing installation

Update a local copy later

Enable or disable a plugin

Uninstall Faye Coding Assistant

Uninstall Faye Image Utility

Uninstall Faye UI System Engineer

Add the marketplace with your agent