# Set up Codex Choose your app, install the plugins you need, and start using their skills. ## Codex · app · Git repository Procedure status: needs-input. Verification: pending. Recorded: 2026-09-30. 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. [Verification evidence](https://learn.chatgpt.com/docs/developer-commands) ## 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. ### Procedure awaiting confirmation Use a confirmed terminal guide while the app-specific instructions are prepared. The requests below describe exactly what is missing. What you should see: This route becomes actionable after the missing procedure is confirmed. ## Source procedure and agent guidance # Codex: desktop app 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-app-git`. Status: `needs-input`. Marketplace: `faye-plugin-market`. Target: `release`. This route is awaiting the owner’s confirmation of the app-specific installation procedure. ## 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. ## Stop: procedure needs confirmation Do not execute or invent installation steps for this route. Ask for the specific missing procedure below, or offer the confirmed terminal/local alternative when it meets the user's intent. ### Confirm Codex desktop app git setup - Show how to open the controls for adding this custom marketplace in Codex (Desktop app). Record exact menu and button labels. - Confirm whether this interface accepts our Git repository URL directly, the required source format, and the registration result. A curated listing alone does not establish custom Git registration. - Show how to install one Faye plugin, identify its installed/enabled state, and find its skills in a new session. Record the application version. - If this interface needs a different supported workflow, provide that procedure instead; do not infer it from another interface. ### Screenshots for Codex desktop app - Capture the marketplace/source entry point before adding anything, with the relevant control visible. - Capture the Git source input with the repository URL and the marketplace after successful registration. - Capture one Faye plugin's installation/details screen, its installed state, and the skill-discovery view. Keep the relevant labels readable. - Exclude account details, credentials, private projects, and unrelated windows. Use real captures, not simulated screens. ## Codex · app · Local copy Procedure status: needs-input. Verification: pending. Recorded: 2026-09-30. 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. [Verification evidence](https://learn.chatgpt.com/docs/developer-commands) ## 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. ### Procedure awaiting confirmation Use a confirmed terminal guide while the app-specific instructions are prepared. The requests below describe exactly what is missing. What you should see: This route becomes actionable after the missing procedure is confirmed. ## Source procedure and agent guidance # Codex: desktop app 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-app-local`. Status: `needs-input`. Marketplace: `faye-plugin-market`. Target: `release`. This route is awaiting the owner’s confirmation of the app-specific installation procedure. ## 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. ## Stop: procedure needs confirmation Do not execute or invent installation steps for this route. Ask for the specific missing procedure below, or offer the confirmed terminal/local alternative when it meets the user's intent. ### Confirm Codex desktop app local setup - Show how to open the controls for adding this custom marketplace in Codex (Desktop app). Record exact menu and button labels. - Confirm whether the interface selects a marketplace root or an individual plugin folder. Show the expected directory and registration result. - Show how to install one Faye plugin, identify its installed/enabled state, and find its skills in a new session. Record the application version. - If this interface needs a different supported workflow, provide that procedure instead; do not infer it from another interface. ### Screenshots for Codex desktop app - Capture the marketplace/source entry point before adding anything, with the relevant control visible. - Capture the local folder chooser or source field and the marketplace after successful registration. - Capture one Faye plugin's installation/details screen, its installed state, and the skill-discovery view. Keep the relevant labels readable. - Exclude account details, credentials, private projects, and unrelated windows. Use real captures, not simulated screens. ## Codex · terminal · Git repository Procedure status: ready. Verification: 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. [Verification evidence](https://learn.chatgpt.com/docs/developer-commands) ## 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. #### Add marketplace · PowerShell ```powershell codex plugin marketplace add https://github.com/Fayegram-AI/plugin-market.git ``` #### Add marketplace · Bash / zsh ```bash codex plugin marketplace add https://github.com/Fayegram-AI/plugin-market.git ``` What you should see: The source is registered. Its native marketplace identity is faye-plugin-market. ### Faye Coding Assistant 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 ```powershell codex plugin add faye-coding-assistant@faye-plugin-market ``` #### Install Faye Coding Assistant · Bash / zsh ```bash codex plugin add faye-coding-assistant@faye-plugin-market ``` What you should see: Faye Coding Assistant appears in the installed plugin list. Compare its version with 0.1.0-beta.7 shown by this marketplace. ### Faye Image Utility 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 ```powershell codex plugin add faye-image-utility@faye-plugin-market ``` #### Install Faye Image Utility · Bash / zsh ```bash codex plugin add faye-image-utility@faye-plugin-market ``` What you should see: Faye Image Utility appears in the installed plugin list. Compare its version with 0.1.0-beta.6 shown by this marketplace. ### Faye UI System Engineer 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 ```powershell codex plugin add faye-ui-system-engineer@faye-plugin-market ``` #### Install Faye UI System Engineer · Bash / zsh ```bash codex plugin add faye-ui-system-engineer@faye-plugin-market ``` What you should see: Faye UI System Engineer appears in the installed plugin list. Compare its version with 0.1.0-beta.6 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 ```powershell codex plugin list --marketplace faye-plugin-market ``` #### List installed plugins · Bash / zsh ```bash codex plugin list --marketplace faye-plugin-market ``` What you should see: Your selected plugins are installed and their applicable skills can be found or explicitly invoked in a fresh session. ### 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 ```powershell codex plugin marketplace upgrade faye-plugin-market ``` #### Refresh marketplace · Bash / zsh ```bash codex plugin marketplace upgrade faye-plugin-market ``` What you should see: 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 · Host request ``` /plugins ``` #### Inside Codex · Host request ``` /plugins ``` What you should see: 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 ```powershell codex plugin remove faye-coding-assistant@faye-plugin-market ``` #### Uninstall selected plugin · Bash / zsh ```bash codex plugin remove faye-coding-assistant@faye-plugin-market ``` What you should see: 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 ```powershell codex plugin remove faye-image-utility@faye-plugin-market ``` #### Uninstall selected plugin · Bash / zsh ```bash codex plugin remove faye-image-utility@faye-plugin-market ``` What you should see: 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 ```powershell codex plugin remove faye-ui-system-engineer@faye-plugin-market ``` #### Uninstall selected plugin · Bash / zsh ```bash codex plugin remove faye-ui-system-engineer@faye-plugin-market ``` What you should see: Faye UI System Engineer is no longer listed as installed. ### 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 ```powershell codex plugin list --marketplace faye-plugin-market ``` #### Installed plugins · Bash / zsh ```bash codex plugin list --marketplace faye-plugin-market ``` #### Registered marketplaces · PowerShell ```powershell codex plugin marketplace list ``` #### Registered marketplaces · Bash / zsh ```bash codex plugin marketplace list ``` What you should see: The intended source and installed package are identified without removing other registrations. ## Source procedure and agent guidance # 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.6`. 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.6 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. ## Codex · terminal · Local copy Procedure status: ready. Verification: tested. Recorded: 2026-09-27. Host version: 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. [Verification evidence](https://learn.chatgpt.com/docs/developer-commands) ## 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. ### 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 see: 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 ```powershell git clone https://github.com/Fayegram-AI/plugin-market.git faye-plugin-market ``` #### Clone into a new folder · Bash / zsh ```bash git clone https://github.com/Fayegram-AI/plugin-market.git faye-plugin-market ``` What you should see: 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. What you should see: The 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/ 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' ``` #### Open your local copy — replace the example path · Bash / zsh ```bash cd -- '/path/to/Faye Plugin Market' ``` What you should see: 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 ```powershell codex plugin marketplace add . ``` #### Add marketplace · Bash / zsh ```bash codex plugin marketplace add . ``` What you should see: The source is registered. Its native marketplace identity is faye-plugin-market. ### Faye Coding Assistant 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 ```powershell codex plugin add faye-coding-assistant@faye-plugin-market ``` #### Install Faye Coding Assistant · Bash / zsh ```bash codex plugin add faye-coding-assistant@faye-plugin-market ``` What you should see: Faye Coding Assistant appears in the installed plugin list. Compare its version with 0.1.0-beta.7 shown by this marketplace. ### Faye Image Utility 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 ```powershell codex plugin add faye-image-utility@faye-plugin-market ``` #### Install Faye Image Utility · Bash / zsh ```bash codex plugin add faye-image-utility@faye-plugin-market ``` What you should see: Faye Image Utility appears in the installed plugin list. Compare its version with 0.1.0-beta.6 shown by this marketplace. ### Faye UI System Engineer 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 ```powershell codex plugin add faye-ui-system-engineer@faye-plugin-market ``` #### Install Faye UI System Engineer · Bash / zsh ```bash codex plugin add faye-ui-system-engineer@faye-plugin-market ``` What you should see: Faye UI System Engineer appears in the installed plugin list. Compare its version with 0.1.0-beta.6 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 ```powershell codex plugin list --marketplace faye-plugin-market ``` #### List installed plugins · Bash / zsh ```bash codex plugin list --marketplace faye-plugin-market ``` What you should see: Your selected plugins are installed and their applicable skills can be found or explicitly invoked in a fresh session. ### 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 see: 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 · Host request ``` /plugins ``` #### Inside Codex · Host request ``` /plugins ``` What you should see: 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 ```powershell codex plugin remove faye-coding-assistant@faye-plugin-market ``` #### Uninstall selected plugin · Bash / zsh ```bash codex plugin remove faye-coding-assistant@faye-plugin-market ``` What you should see: 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 ```powershell codex plugin remove faye-image-utility@faye-plugin-market ``` #### Uninstall selected plugin · Bash / zsh ```bash codex plugin remove faye-image-utility@faye-plugin-market ``` What you should see: 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 ```powershell codex plugin remove faye-ui-system-engineer@faye-plugin-market ``` #### Uninstall selected plugin · Bash / zsh ```bash codex plugin remove faye-ui-system-engineer@faye-plugin-market ``` What you should see: Faye UI System Engineer is no longer listed as installed. ### 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 ```powershell codex plugin list --marketplace faye-plugin-market ``` #### Installed plugins · Bash / zsh ```bash codex plugin list --marketplace faye-plugin-market ``` #### Registered marketplaces · PowerShell ```powershell codex plugin marketplace list ``` #### Registered marketplaces · Bash / zsh ```bash codex plugin marketplace list ``` What you should see: The intended source and installed package are identified without removing other registrations. ## Source procedure and agent guidance # 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/ 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.6`. 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.6 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.