mirror of
https://github.com/Heretek-AI/awesome-opencode.git
synced 2026-11-07 10:45:57 -10:00
* docs: add Veris Daytona, Veris E2B, and Veris Sim to plugins Claude-Session: https://claude.ai/code/session_01BL98DAnZJb8zJeyGGi9qzo * docs: expand Veris entries with official copy, tags, and install docs Rename files to match published product ids (productId is derived from the YAML filename), use official display names, and add npm/docs links inside the installation block since npmUrl is not part of the export mapping. Claude-Session: https://claude.ai/code/session_01BL98DAnZJb8zJeyGGi9qzo * docs: drop redundant -opencode suffix from Veris entry filenames Only four other entries carry the suffix, and in each the product name itself contains "opencode". docs/schema-design.md uses the short form (codegpt.yaml -> productId "codegpt"), so match that. Claude-Session: https://claude.ai/code/session_01BL98DAnZJb8zJeyGGi9qzo --------- Co-authored-by: alikhan126 <[email protected]>
This commit is contained in:
BillyOutlastandalikhan126 authored and GitHub committed
1 parent
5725847ecc
commit
ae10dd012d
3 files changed
+166
No files matched your search
@@ -0,0 +1,54 @@
|
||||
name: Veris for Daytona
|
||||
repo: https://github.com/veris-ai/veris-daytona
|
||||
tagline: OpenCode sessions run in a Daytona sandbox whose vendor API calls are answered by Veris twins
|
||||
description: >-
|
||||
Every OpenCode session runs in a Daytona sandbox whose calls to Stripe and the rest of your
|
||||
vendor stack are answered by stateful Veris twins, and the agent gets a receipt of what the
|
||||
vendor actually received. Unmodified code, real hostnames, no image to build.
|
||||
scope:
|
||||
- global
|
||||
- project
|
||||
tags:
|
||||
- veris
|
||||
- daytona
|
||||
- sandbox
|
||||
- integration-testing
|
||||
- api-mocking
|
||||
- testing
|
||||
homepage: https://github.com/veris-ai/veris-daytona/tree/main/daytona-opencode#readme
|
||||
installation: |
|
||||
## Links
|
||||
|
||||
- npm: https://www.npmjs.com/package/@veris-ai/daytona-opencode
|
||||
- Source: https://github.com/veris-ai/veris-daytona/tree/main/daytona-opencode
|
||||
- Docs: https://github.com/veris-ai/veris-daytona/tree/main/daytona-opencode#readme
|
||||
- Veris: https://veris.ai
|
||||
|
||||
## Installation
|
||||
|
||||
Add the plugin to `opencode.json`:
|
||||
|
||||
```jsonc
|
||||
{ "plugin": ["@veris-ai/daytona-opencode"] }
|
||||
```
|
||||
|
||||
Then export three keys:
|
||||
|
||||
```sh
|
||||
export DAYTONA_API_KEY=... # https://app.daytona.io/dashboard/keys
|
||||
export VERIS_API_KEY=... # https://studio.veris.ai
|
||||
export VERIS_ENVIRONMENT_ID=... # the Veris environment that decides which vendor twins you get
|
||||
```
|
||||
|
||||
Then run `opencode`. No image to build, no network configuration, nothing to start.
|
||||
|
||||
## What the agent gets
|
||||
|
||||
- The ten sandbox-backed tools from `@daytona/opencode`: bash, read, write, edit,
|
||||
multiedit, ls, glob, grep, getPreviewURL, gitSync.
|
||||
- `verisReceipt`, which reports what the twin *received*.
|
||||
- The Veris MCP server.
|
||||
|
||||
An empty receipt after a green run means the code never reached its dependency.
|
||||
Ask an agent to call the Stripe API and it will report success whether or not it
|
||||
made the call. The transcripts are identical; the receipts are not.
|
||||
@@ -0,0 +1,57 @@
|
||||
name: Veris for E2B
|
||||
repo: https://github.com/veris-ai/veris-e2b
|
||||
tagline: OpenCode sessions run in an E2B sandbox whose vendor API calls are answered by Veris twins
|
||||
description: >-
|
||||
Every OpenCode session runs in an E2B sandbox whose outbound vendor API calls are answered by
|
||||
stateful Veris twins, with a receipt of what the vendor actually received. One line in
|
||||
opencode.json - no template to register, no server to start.
|
||||
scope:
|
||||
- global
|
||||
- project
|
||||
tags:
|
||||
- veris
|
||||
- e2b
|
||||
- sandbox
|
||||
- integration-testing
|
||||
- api-mocking
|
||||
- testing
|
||||
homepage: https://github.com/veris-ai/veris-e2b/tree/main/e2b-opencode#readme
|
||||
installation: |
|
||||
## Links
|
||||
|
||||
- npm: https://www.npmjs.com/package/@veris-ai/e2b-opencode
|
||||
- Source: https://github.com/veris-ai/veris-e2b/tree/main/e2b-opencode
|
||||
- Docs: https://github.com/veris-ai/veris-e2b/tree/main/e2b-opencode#readme
|
||||
- Veris: https://veris.ai
|
||||
|
||||
## Installation
|
||||
|
||||
Add the plugin to `opencode.json`:
|
||||
|
||||
```jsonc
|
||||
{ "plugin": ["@veris-ai/e2b-opencode"] }
|
||||
```
|
||||
|
||||
Then export three keys:
|
||||
|
||||
```sh
|
||||
export E2B_API_KEY=... # https://e2b.dev/dashboard
|
||||
export VERIS_API_KEY=... # https://app.veris.ai
|
||||
export VERIS_ENVIRONMENT_ID=... # the Veris environment that decides which vendor twins you get
|
||||
```
|
||||
|
||||
Then run `opencode`. No image to build, no template to register, no server to start,
|
||||
no URL to copy.
|
||||
|
||||
## What the agent gets
|
||||
|
||||
Eight sandbox-backed replacements for OpenCode's built-in tools (bash, read, write,
|
||||
edit, multiedit, ls, glob, grep), plus three additions:
|
||||
|
||||
- `verisReceipt`: what the twin *received*, the tool that separates a real
|
||||
integration from a plausible-looking one.
|
||||
- `gitSync`: commit in the sandbox and pull into the local `opencode/N` branch,
|
||||
returning only once the changes are on your machine.
|
||||
- `getPreviewURL`: the public URL for a port inside the sandbox.
|
||||
|
||||
An empty receipt after a green run means the code never reached its dependency.
|
||||
@@ -0,0 +1,55 @@
|
||||
name: Veris Sim
|
||||
repo: https://github.com/veris-ai/plugins
|
||||
tagline: Three engineer-invoked commands that test an application against Veris twins of its services
|
||||
description: >-
|
||||
Three engineer-invoked commands that test an application against Veris twins of the services it
|
||||
calls. setup wires a repository once. build measures every vendor claim the task rests on before
|
||||
designing, then proves the change through veris-proxy. fix reproduces the failure before touching
|
||||
source and proves it closed. Ships the veris MCP server.
|
||||
scope:
|
||||
- global
|
||||
- project
|
||||
tags:
|
||||
- veris
|
||||
- integration-testing
|
||||
- sandbox
|
||||
- mcp
|
||||
- testing
|
||||
- commands
|
||||
homepage: https://github.com/veris-ai/plugins#readme
|
||||
installation: |
|
||||
## Links
|
||||
|
||||
- npm: https://www.npmjs.com/package/@veris-ai/veris-sim-opencode
|
||||
- Source: https://github.com/veris-ai/plugins/tree/main/veris-sim
|
||||
- Docs: https://github.com/veris-ai/plugins#readme
|
||||
- Veris: https://veris.ai
|
||||
|
||||
## Installation
|
||||
|
||||
```sh
|
||||
opencode plugin @veris-ai/veris-sim-opencode -g
|
||||
```
|
||||
|
||||
Equivalently, add `"@veris-ai/veris-sim-opencode"` to the `plugin` array in
|
||||
`~/.config/opencode/opencode.json`. Then export your credential and restart
|
||||
opencode:
|
||||
|
||||
```sh
|
||||
export VERIS_API_KEY=... # https://app.veris.ai
|
||||
```
|
||||
|
||||
`VERIS_API_BASE` overrides the control plane (it defaults to
|
||||
`https://svc.api.veris.ai`). Until the key is set, `opencode mcp list` shows the
|
||||
`veris` server as failed; the commands still run, and `setup` walks you through it.
|
||||
|
||||
## Commands
|
||||
|
||||
| command | what it does |
|
||||
|---|---|
|
||||
| `/veris-sim:setup` | wires the repository to a Veris environment, once: credential, environment, transport, one smoke run with proof of arrival |
|
||||
| `/veris-sim:build <issue link \| prompt>` | measures every vendor claim the task rests on against the twin before designing, proves the change through veris-proxy with a receipt |
|
||||
| `/veris-sim:fix <issue link \| prompt>` | reproduces the failure the issue describes before designing, proves the same failure closed with a receipt |
|
||||
|
||||
The three are plain OpenCode commands: only the engineer starts them, the model
|
||||
cannot invoke them on its own. The same three are also registered as skills.
|
||||
Reference in new issue
Block a user