---
title: "nexaedge"
description: "Front end for the nexaedge marketplace that works the same on Claude Code, Codex and Antigravity. Detects which agent is running, translates to that agent's native install path, and keeps everything at user scope so a pl"
canonical: https://agentpluginsdirectory.com/plugins/nexaedge
last-updated: 2026-09-22
---

# nexaedge
Front end for the nexaedge marketplace that works the same on Claude Code, Codex and Antigravity. Detects which agent is running, translates to that agent's native install path, and keeps everything at user scope so a plugin is installed once per machine rather than copied into each repository.
- Slug: nexaedge
- Publisher: Jaison Erick
- Repository: https://github.com/nexaedge/nexaedge-marketplace
- Manifest: plugins/nexaedge/plugin.json
- Version: v7
- Category (editorial): agent-tooling
- Skills: 1 (plugins)
- MCP servers: 0
- Stars: 1
- Repository created: 2026-03-05
- Repository last pushed: 2026-09-16
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/nexaedge
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What nexaedge does, in the publisher's words

One front end for the NexaEdge plugin catalog across Claude Code, Codex and Antigravity.

Ask for things in plain language: "what plugins are available?", "install the html report one", "update my plugins". The skill detects which agent is running and translates to that agent's native install path.

The three agents install plugins in three different ways, and one of them does not install plugins at all. Without a front end, using this catalog means remembering which commands your current agent understands.

- The agent's command is often absent from the PATH. The installer writes the user PATH, and every process started before it keeps the old one. The binary is resolved instead: PATH, then CLAUDE_CODE_EXECPATH, which Claude Code exports as the binary it is running, then ~/.local/bin and the npm global directory, then every directory the Windows user PATH names. status prints what it resolved.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/nexaedge/nexaedge-marketplace/HEAD/plugins/nexaedge/README.md

## Skills

- plugins: Install, find, update and remove NexaEdge plugins, on whichever agent is running. Use when someone asks to install a plugin or skill, wants to know what is available, asks to update their plugins, or says something like "what can I install", "what plugins do I have", "add the html report skill", "u…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.