Skip to content

About

Reusable Agentic AI plugins for context management, verified installation, testing, and publication workflows.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

1 Commit

Folders and files

Repository files navigation

Workbench Plugins

English · Deutsch · 한국어

This is the English source README. The German and Korean pages are complete AI-translated editions, maintained alongside this source. Technical names and executable identifiers retain their English forms. Linked protocol, evidence and legal documents marked as English are separately maintained sources.

Verification evidence: project migration/update contracts and evidence (English) · test contracts, inspector review and current logs (English) · earlier startup checks and limits (English).

Note

Testing stage

The project's current testing setup is GPT-6.1 Sol with Extra High (xhigh) reasoning effort. Profile recovery and saving before a conversation closes can involve lengthy reasoning and consume substantial time and usage allowance. The local connection guide starts no model turn. Optimization is planned after the package has stabilized, with preservation and reliable recovery of Profile information taking priority. See the optimization plan (English).

Project author and workflow direction: Gunwoo Park
AI-generated text
Documentation revision tool: OpenAI Codex; exact revision model unverified · 2026-11-13. Earlier recorded revision model: OpenAI gpt-6.1-sol.

English

Documentation roles: this README.md is the maintained public introduction; README.org is a navigation entry. Internal protocols prefer Org. Markdown agent entries explicitly require the relevant Org sources to be opened; links alone are not loaded automatically. See document ownership.

User-side communication is an assigned responsibility throughout the work. The integrator owns it by default: briefly explain actual changes and their meaning, then provide the relevant work, evidence and open items when asked. Read the Communication Agent protocol before applying the role and bind it explicitly in consumer instructions. This is collection guidance, not an installed upgrade, new plugin or automatic background agent.

Org files use the plain-text markup of Emacs org-mode. Like Markdown, .org files can be read directly in a text editor or by an AI reading file text; Emacs is optional for reading. The main notation changes are:

Meaning Markdown Org
Level 1 heading # Heading * Heading
Level 2 heading ## Heading ** Heading
Local file link [label](path) [[file:path][label]]
Document title metadata A heading is commonly used #+title: Title

Org source/example blocks are document content; reading them does not request execution.

This collection is part of Workbench (wb), the project author's independent project. Its plugin package IDs use the wb- prefix to identify their origin.

For the research motivation and how wb-plugins, wb-templates and wb-applications fit together, see the author's informal letter about Workbench (English).

Reusable protocols packaged as independently installable agent plugins. The workflow connects source review, explicit installation, actual use and corrective verification. The author's requirements shape explicit Profile selection, checked Profile handoff, reviewed installation and reusable protocol packaging. Native installation has been checked with Codex on Linux/POSIX. Private workbench records and Profiles stay with the consumer. This directory can become a standalone repository; these files alone do not establish that a GitHub repository or release has been published.

Shared terminology

Use Profile for a named group of records such as management; it persists across connections and conversations. Project is the work, Workspace its folder, and Docker sandbox the isolated environment running it. The current workflow uses a sandbox per project, but a folder and a sandbox are different objects. Connection session means entering through sbx run in this workflow; Conversation/Thread means an individual Codex chat, which can resume after reconnecting. The terminology guide owns these definitions and their English/German/Korean labels.

Earlier debugging used “session start” for both a connection opening and Profile selection/recovery. That ambiguity contributed to communication and acceptance criteria mismatches; it does not establish every technical failure's cause. The pre-input connection guide and the latest-record summary after confirmed Profile selection are separate checks. The technical hook event SessionStart keeps its exact name and does not itself prove pre-input display.

Packages

Plugin Source version Purpose
wb Session Protocols 0.5.0 Select or explicitly switch a Profile, preserve records and prepare checked conversation closure.
wb Security Intake 0.2.2 Review new packages, skills, prompts and instructions before adoption; recheck integration.
wb Plugin Installer 0.2.3 Plan and stage authorized installations, then verify native installation and installed use.
wb Protocol to Plugin 0.2.2 Extract a reusable contextual protocol into an independent package.
wb Publication Support 0.4.3 Prepare publication docs, provenance and licensing; combine requested AI reviews from user/reader, technical and legal/licensing perspectives.
wb Test Protocols 0.1.0 Design behavior-based tests, challenge weak oracles and link scoped verification claims to reproducible logs.
wb Project Knowledge 0.1.0 Inventoried project-knowledge migration and explicit baseline-aware updates; portable history, preserved provenance and destination conflict decisions.

These are source versions. An existing installation can retain an earlier edition until a reviewed update. The requested name publication_support is registered as wb-publication-support, following the collection's identifier convention.

Source 0.5.0 supports an explicitly requested Profile switch within the same Conversation/Thread: save, check and park the current Profile before changing the binding and recovering the selected Profile. The Conversation stays open. Read the switching contract; existing installations require a separate reviewed update to gain this capability.

Installation

Choose a plugin, then ask your agent: “Review the local candidate at ./candidate and its installer before execution; prepare an installation plan for this project, showing storage, settings and any optional hooks.” Review that concrete plan, install within the agreed scope and try the installed procedure. An independently copied child needs a destination catalog entry and its declared companion dependencies. Ordinary documentation work can use the procedure directly when native installation is outside scope.

Before presenting a prepared plan, verify its source hashes and current Workspace, native and entrypoint baselines, including AGENTS.md. Re-plan changed state while preserving later edits and earlier authorization.

At first setup, after showing the concrete combined list of settings, hooks and startup-entrypoint changes, the agent asks whether to approve all listed changes together. The default is No — ask individually. After 60 seconds without an answer, it switches to individual questions; that timeout grants no consent and starts no installation. An actual Yes covers only the displayed plan. Existing authorization remains valid, and native hook trust still uses supported individual review controls without a trust-all bypass.

  1. Prepare a reviewed distribution copy preserving required hidden .agents/ and package .codex-plugin/ metadata, LICENSE and resources. Omit .git, __pycache__, *.pyc, *.pyo and private consumer records; inspect the actual tree before sharing. .gitignore does not filter ordinary file copies. See copy boundaries. A single child travels with its included LICENSE, resources and declared dependencies.
  2. Before running candidate code, read the wb Security Intake procedure and review the candidate and installer. First use can bootstrap from reviewed inert source; the installer does not have to be installed already.
  3. Follow the installation guide and exact command/attestation reference. Prepare an edition-bound audit and concrete plan, retain actual authorization, stage, run the emitted native commands, then inspect a fresh runtime and use the installed entrypoint. Templates are not approval or completed audits.
  4. wb Session Protocols has its own setup: select Profile/startup-summary/parking features and any hooks explicitly. The generic declarative staging helper declines active hook/MCP packages. Review and verify each selected hook through supported controls. Package discovery alone does not complete setup: verify selected features, trusted events, the normal startup entrypoint and the visible summary after Profile selection or recovery.

The project's current environment is Codex CLI inside a Docker sandbox (Linux/POSIX). For selected startup_summary, source 0.4.7 defaults to reviewed normal-codex entrypoint registration in a recognized sandbox. The installation agent must run the emitted activation commands and verify the normal codex route with a PTY: guide before input, ready composer and retained scrollback. It must not finish by handing the user a separate launch.py command. A chat's plain shell runner may lack a terminal; the agent supplies the PTY for this check. See startup integration.

Project-only manual launch is an explicit opt-out. Unknown environments remain incomplete until their actual entrypoint is adapted and checked. Other environments can need different binary paths, terminal handling or reconnect integration. A local normal-codex check does not establish a host sbx run reconnect; verify that actual reopening route separately when required.

Example inventory from a reviewed local source copy:

cd /path/to/wb-plugins
python3 wb-plugin-installer/scripts/plugin_installer.py inventory \
  --source ./wb-publication-support

This command only inventories source. It does not install or trust it. Native registration/enablement uses the selected CODEX_HOME and can affect availability across workspaces. A local collection is not a guarantee of zero client networking.

Usage examples

After installation, ask the agent using the relevant skill:

$wb-security-intake:security-intake Review ./candidate before adopting its instructions.
$wb-plugin-installer:plugin-installer Install the reviewed ./candidate in this consumer; plan exact effects and add no optional hooks.
$wb-protocol-to-plugin:protocol-to-plugin Extract the reusable review method from the permitted context; keep private records outside the package.
$wb-publication-support:publication-support Prepare English, German and Korean docs for ./my-package with its actual author/model, chosen license and examples.
$wb-session-protocols:session-lifecycle Save this conversation to its confirmed Profile and close the conversation after the checks pass.

The final line is an example of a live closing request, not a request to close the conversation in which this README is being reviewed.

Requirements and limits

Native install/discovery was checked on Linux/POSIX with Codex 0.167.2; other clients/platforms need verification. Helpers use Python 3.10+ or 3.11+ as documented. Profile record locking requires POSIX. Conversation closure uses terminal text: a parking sign and car, then the recovery path and English plus the recent conversation language. English, German and Korean are presets; other languages are marked as AI-generated translations. English appears once. Text needs no image library. Its optional legacy PNG renderer additionally needs Pillow and fonts and has Linux font defaults. wb Security Intake and wb Publication Support are declarative guidance, not scanners or runtime access controls. Abrupt termination does not guarantee a final Profile handoff. See packaging conventions.

Attribution, disclaimer and license

The author credit above identifies project concept and workflow direction. The documentation text is AI-generated. This revision used OpenAI Codex on 2026-11-13; its exact model is unverified. The previously recorded model was gpt-6.1-sol. These notices do not establish human review. Earlier files' original models were not recorded per file; see the provenance inventory. AI text, translations and examples may contain errors or omissions; verify them against the actual package and environment. No security or loss-free-operation guarantee is made. No OpenAI affiliation or endorsement is implied. See the full disclaimer.

MIT applies to this collection root and all descendants, regardless of its directory name, including project-owned code, documentation, skills, scripts, templates, assets, tests and hidden metadata, unless an explicit narrower license states otherwise. A child LICENSE copying the same MIT grant preserves it for standalone transport. Third-party material and dependencies retain their own terms. See LICENSE and scope and exceptions. The software is provided AS IS.

About

Reusable Agentic AI plugins for context management, verified installation, testing, and publication workflows.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages