01 / Docs

Method stays subordinate to the work.

Servotab is a skills-only engineering method layer for Codex. It calibrates how much process a repository task receives without taking ownership away from the task, the repo, or the user.

Get started

Add the public plugin. Or inspect the tagged source release.

Servotab 0.6.4 is publicly available in the official OpenAI Plugins Directory. Open the Servotab listing to add the published plugin. The repository route below installs the separately receipted tagged 0.6.5 source release for inspection or maintainer testing. The directory and GitHub versions are recorded separately, and the public listing does not expose an archive digest.

01 / source checkout

git clone --branch v0.6.5 --depth 1 https://github.com/IndelibleVivi/servotab.git
cd servotab
codex plugin marketplace add .
codex plugin add servotab@personal

02 / ask

ordinary language

Fix the stale-cursor regression, identify the violated invariant, repair the canonical source, and run the focused suite.

precise control

$review inspect this diff and report only verified, actionable P0–P2 findings.

Confirm the current install.

Open a fresh Codex task or process after installation, then read back the configured marketplace package instead of assuming the active process refreshed:

codex plugin list --marketplace personal

The receipt should show servotab@personal as installed, enabled at version 0.6.5. On 2026-08-31 this source-checkout route and fresh-process router discovery were verified on macOS with codex-cli 0.147.0. That is an observed compatibility receipt, not a guessed minimum-version guarantee.

One implicit router. Twelve explicit shortcuts.

Describe ordinary repository work normally. Servotab may keep a clear change direct or load one relevant method when risk or uncertainty warrants it. Use names such as $review, $tdd, or $spec-chain when you want precise control; the twelve method leaves are not implicit workflows.

A skills-only product boundary.

Servotab adds no Servotab account, backend, database, telemetry service, or network endpoint, and the publisher does not receive repository contents through the plugin. Codex and any repositories, browsers, terminals, tools, or external services it uses remain governed by their own permissions and data practices.

Working model

One router. A bounded set of methods.

Ordinary work begins in natural language. Servotab first asks whether the task is already clear, local, and reversible. If it is, Codex should work directly. If the task carries material uncertainty or risk, Servotab selects the method that addresses that specific pressure.

clear / local

Stay direct

Inspect only what matters, make the coherent change, and verify the affected behavior.

uncertain / risky

Invoke method

Add design, planning, debugging, testing, review, isolation, delegation, or closure only where it protects the outcome.

Task shapes

Proportionate, in concrete terms.

The method depth changes with the pressure in the work—not with a fixed ritual. These three shapes mirror the public behavior cases maintained in the repository.

Change one empty-state string.

One file, the narrowest meaningful check, no plan, and no delegation overhead.

Repair a stale-cursor regression.

Reproduce the failure, locate the consistency-window invariant, repair canonical source, and run the focused regression suite.

Plan from an approved specification.

Retain every requirement and dependency boundary; a convenient first tranche does not redefine completion.

Inspect the public behavior-evidence contract.

Sequence

Tab first. Response second. Receipt. Stop.

The motion grammar describes product behavior: intervention is small, causal, and finite. Servotab does not add ambient “thinking” animation or keep a task inside a process after the evidence has settled.

The base already exists.

The requested task and repository remain the primary surface.

A method attaches locally.

A bounded technique appears where it can materially change confidence or direction.

The larger work responds.

The plan, implementation, diagnosis, or review changes in a way proportionate to the risk.

Fresh evidence settles the state.

A named check or observed result supports the claim, and then the method stops.

Boundaries

What Servotab does not claim.

It does not replace the user’s prompt, repository instructions, permissions, or Git decisions.
A log, review, plan, or generated artifact may inform the work; it does not authorize itself.
It does not make every task follow one mandatory end-to-end workflow.
It does not treat a green build as proof of deployment, runtime activation, or owner acceptance.
It does not turn an explicit complete request into a scaffold, placeholder, or unnamed partial result.
The public directory listing proves availability; it does not make Servotab an official OpenAI product or transfer repository authority to the directory surface.

Related projects

MCP Boundary

An MCP engineering skill, Guide, and executable Lab for designing, reviewing, and verifying MCP servers and apps.

Worker Routing

Delegate bounded responsibilities to native or optional ACP workers, with a local Dispatch dashboard for inspecting the work.

Status & evidence

Verified to the boundary we can prove.

The 0.6.5 source release is generated from canonical method and icon sources into an exact 70-file plugin package. Public checks cover source/generated sync, skill validation, manifest freshness, package self-tests, public-tree audit, Python compilation, website motion behavior, and the production build. Those gates establish source and package consistency plus the checked UI behavior; they do not prove behavior on every machine or publication of the same version in the directory. A separate public listing readback supplies that publication receipt.

The official Servotab listing reports version 0.6.4, developer Yifei Fang, and all thirteen Servotab skills, including Worktree. GitHub release 0.6.5 is the current source install target. It adds connected execution and shared-contract correction across a twenty-five-case source pack; its deterministic fixtures do not establish live model behavior. The listing does not expose package bytes, so directory publication does not prove byte identity with the GitHub asset. GitHub release availability is recorded on the repository Releases page. The same repository preserves earlier Softpowers commits, release records, licensing history, and provenance without relabelling those historical versions.

Official listing · Source · Changelog · Current state