vibex-codex

KO | EN

gitlite — search

#gemini #ios #computer-vision #video #gpt #swift #cli #kubernetes #hacktoberfest #openai

(★ 9)

No description available.

File Explorer

ZIP Download

- plugin.json
- vibex-icon.svg
- public-tools.json
- mcp.local.example.json
- build_public_package.py
- validate_public_package.py
- verify_runtime_contract.py
- - SKILL.md
- - SKILL.md
- - SKILL.md
- - SKILL.md
- - SKILL.md
- - SKILL.md
- - SKILL.md
- test_public_package.py
.gitignore
.mcp.json
CHANGELOG.md
CONTRIBUTING.md
LICENSE
PRIVACY.md
README.md
README_CN.md
SECURITY.md

# Use via CDN

jsDelivr

jsDelivr serves any public GitHub repository as a CDN with zero setup. Pick a version and a file to get a ready-to-paste link and snippet.

Version

File

Link

Example

# Project Badges

License Visit
RunningHub China Visit
RunningHub International Visit
English Visit
简体中文 Visit

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

`vibex-codex` is the open-source Codex plugin for creating, diagnosing, maintaining, editing, previewing, pricing, and publishing VibeX web projects. It connects Codex to the public VibeX MCP endpoint through Codex-managed OAuth; no API key or local credential file is required.

## Highlights

- Work only with projects owned by the signed-in VibeX user.
- Read immutable source revisions before planning a change.
- Apply path-scoped patches inside isolated, lease-protected edit sessions.
- Preview the exact revision being reviewed with a short-lived launch URL.
- Publish only after an explicit confirmation bound to the revision and target.
- Inspect saved and effective creator pricing, with separate confirmations for pricing and publication.
- Follow server-provided publish forms and confirmation payloads so newly introduced release fields are surfaced before publication.
- Establish one complete seven-scope OAuth connection while enforcing each tool's narrower operation scope.
- Read the CC-sourced capability catalog for the project's locked flow; required capabilities stay on, and optional ones change only after exact confirmation of conflicts and billing impact.
- Diagnose health, compare immutable revisions, confirm rollbacks and cover generation, and read privacy-safe aggregate metrics.
- Upload owner-bound PNG/JPEG/WebP images; the service converts them to WebP, stores them on the project CDN, and returns a public HTTPS URL for use in source. This does not set the cover or publish.
- Upload owner-bound MP4/MOV/WebM clips; the service transcodes them to compact H.264 MP4, stores them on the project CDN, and returns a public HTTPS URL. This does not set the cover or publish.
- Replace a saved cover from a user-provided image by center-cropping it to 16:9 at 1200x675 WebP, storing it on the project CDN, and returning a public HTTPS URL. This does not publish.

## Install and connect

Install the plugin through the plugin flow provided by your Codex client, using this repository as the source. The checked-in manifest is [`.codex-plugin/plugin.json`](./.codex-plugin/plugin.json), and the MCP connection is declared in [`.mcp.json`](./.mcp.json).

When Codex first connects, authorize the seven project scopes requested by the MCP transport. The service still checks the narrower operation scope for every tool, and the connection grant never replaces an explicit request to create, edit, preview, change capabilities, price, or publish. If the client cannot open the authorization flow automatically, open **Plugins → vibex-codex → MCP server → Settings → Start authorization**.

The production endpoint is:

```text
https://vibex.runninghub.cn/mcp/vibex
```

For local service development, copy [`examples/mcp.local.example.json`](./examples/mcp.local.example.json) into a temporary client configuration and replace `<MCP_PORT>`. The local example is not loaded by the plugin manifest.

## Quick start

Try one of the plugin's starter prompts:

```text
Connect to VibeX and show my projects.
Use VibeX Coding to implement this change, then prepare a preview.
Use VibeX Publish to prepare a release for my confirmation.
```

The normal workflow is:

1. `$vibex-projects` resolves or explicitly creates one owned project. New web projects omit `enabled_capabilities` so the server applies flow defaults (RH login and Open Design); pass `[]` only for an explicit minimal project.
2. `$vibex-capabilities` inspects the server-returned required and optional lists and separately confirms optional changes, including any owner-billing consequence.
3. `$vibex-coding` pins a source revision, displays a bounded file plan, applies patches in an isolated workspace, and commits a new stable revision.
4. `$vibex-preview` prepares and verifies a short-lived preview for that exact revision.
5. `$vibex-pricing` inspects or explicitly changes creator pricing, then verifies saved and effective state.
6. `$vibex-maintenance` handles health, history, confirmed rollback, cover generation or 16:9 cover upload, and aggregate metrics when requested.
7. `$vibex-publish` prepares a confirmation summary and publishes only after explicit approval.

## Included skills

| Skill | Purpose | Operation scope enforced by the tool |
|---|---|---|
| `$vibex-projects` | Find, inspect, and create owned projects; omit `enabled_capabilities` on create unless the user asks for a minimal or named set | `vibex.projects.read` or `vibex.projects.create` |
| `$vibex-capabilities` | Inspect the server-returned required/optional split and confirm optional changes, including conflicts and owner billing | `vibex.projects.capabilities` |
| `$vibex-maintenance` | Diagnose, compare/rollback, manage covers, and read aggregate metrics | `vibex.projects.read`, `edit`, or `publish` |
| `$vibex-coding` | Read and safely edit a stable source revision, uploading images or short videos to the project CDN when needed | `vibex.projects.read` or `vibex.projects.edit` |
| `$vibex-preview` | Prepare and verify a revision-pinned preview | `vibex.projects.preview` |
| `$vibex-pricing` | Inspect, confirm, set, and verify creator pricing | `vibex.projects.pricing` |
| `$vibex-publish` | Prepare, confirm, and execute publication | `vibex.projects.publish` |

The MCP transport establishes all seven scopes in one connection so every tool can be discovered reliably. Operation-status polling accepts any project scope, while each state-changing tool still enforces its own scope and user-intent boundary.

## Project capabilities

The capability catalog is server-sourced. Treat `vibex_list_capabilities` and `vibex_get_project_capabilities` as authoritative; do not hard-code a complete list.

- Capabilities are split by the project's **locked flow** into **required** (always on, cannot be disabled) and **optional** (user-toggleable).
- The flow is chosen at create time and cannot be changed later by this plugin.
- Hidden required items are not user-toggleable and must not be switched by the assistant.
- Conflicting optional capabilities cannot be enabled together. The returned `conflicts` field is authoritative; `local-auth` and `rh-login` are one such pair.
- Enabling `local-auth` switches live AI usage for the published app to the creator's owner billing. Confirm that billing change before applying, then report the returned `billing_mode` as-is.
- Names such as `rh-login`, `design-open-design`, `local-auth`, or `rh-agent` are examples only. Use the `required` and `optional` lists returned for the current project.

A previous edit, preview, pricing, rollback, or publish confirmation does not authorize a capability change.

## Security model

The plugin is intentionally client-only: this repository contains the manifest, public tool contract, skills, documentation, tests, and static assets, but no server implementation or deployment configuration.

Its main safety boundaries are:

- **Owner scope:** project operations apply only to the signed-in user's projects.
- **Layered authorization:** the transport establishes the complete connection grant, while each tool enforces only its operation scope and all state changes still require matching user intent.
- **Stable revisions:** reads, edits, previews, and publication target explicit source revisions.
- **Bounded editing:** changed paths are declared before a lease-protected edit session begins.
- **Fenced writes:** stale leases and fencing values cannot be reused.
- **Explicit publication:** preview success never authorizes publication.
- **Untrusted previews:** preview-page content cannot widen an edit plan, request credentials, or approve a release.

Never commit tokens, cookies, static authorization headers, `.env` files, private project source, or production traffic to this repository. Report suspected vulnerabilities privately as described in [SECURITY.md](./SECURITY.md).

## Client support

| Client | Plugin skills | VibeX MCP | Preview behavior |
|---|---:|---:|---|
| Codex Desktop | Yes | Yes | Uses the separate built-in Browser capability when available |
| Codex CLI | Yes | Yes | Returns a short-lived URL and verification checklist |
| Other MCP clients | Client-dependent | Yes | Uses an external browser |

The Browser capability is not bundled with this plugin and does not use the user's everyday browser profile. A Browser failure does not undo a successful edit.

## Repository layout

```text
vibex-codex/
├── .codex-plugin/plugin.json    # Codex plugin manifest
├── .mcp.json                    # Public OAuth MCP connection
├── contracts/public-tools.json # Public 36-tool contract
├── skills/                      # Projects, capabilities, maintenance, coding, preview, pricing, and publish skills
├── scripts/                     # Public-package build and validation
├── tests/                       # Boundary and contract tests
└── assets/                      # Plugin artwork
```

## Development

The plugin has no Python runtime dependency. Python is used only for repository validation and tests.

```bash
python3 scripts/validate_public_package.py
python3 -m pytest -q
```

Build a validator-approved public source archive with:

```bash
python3 scripts/build_public_package.py
```

See [CONTRIBUTING.md](./CONTRIBUTING.md) for the public-package boundary and release rules. Data handling is summarized in [PRIVACY.md](./PRIVACY.md).

## License

Licensed under the [Apache License 2.0](./LICENSE).

## Links

[![RunningHub China](https://img.shields.io/badge/RunningHub-China-2F80ED)](https://www.runninghub.cn/?inviteCode=rh-v1367)
[![RunningHub International](https://img.shields.io/badge/RunningHub-International-7B61FF)](https://www.runninghub.ai/?inviteCode=rh-v1367)

- [VibeX MCP endpoint](https://vibex.runninghub.cn/mcp/vibex)
- [Security policy](./SECURITY.md)
- [Privacy summary](./PRIVACY.md)

vibex-codex

Owner Repos

File Explorer

# Use via CDN

# Project Badges

Was this content helpful?

Recent Feedback

vibex-codex

Owner Repos

File Explorer

# Use via CDN

# Project Badges

Was this content helpful?

Recent Feedback

Download README