Coding agent

Wakil

Container-first terminal agent with bounded subagents and gated durable memory.

Status
Active
License
Apache-2.0
Evidence
Documented + code-verifiable, 6 sources
Product record checked
2026-08-02

At a glance

An early-stage, model-agnostic terminal coding agent that defaults to a hardened Docker container, supports direct host execution, coordinates bounded subagents, offers configurable multi-model counsel and two-round debate panels, connects MCP and optional browser tools, and separates session state from a provenance-aware durable memory store.

Good choice if

  • Developers who want container isolation to be the default rather than an add-on
  • Local-model and OpenAI-compatible workflows with explicit endpoint control
  • Research-heavy coding tasks that benefit from bounded parallel subagents, multi-model counsel, and durable memory

Check before choosing

  • The project is young and source-oriented; setup requires building its Docker image and managing configuration rather than installing a mature signed desktop product
  • Direct mode executes tools on the host, while opting into the Docker socket gives the container control of the host Docker daemon and materially weakens isolation
  • Durable memory is intentionally an injection channel: subagents can propose entries and some TTL-scoped writes become active without main-agent review, so untrusted work still requires the gate and memory auditing
See 3 more considerations
  • Browser tools are optional and disabled by default; opening a URL in the host browser is explicitly outside the sandbox
  • Mashūra debate can multiply external-model calls and shares successful first-round responses across providers for round-two critique; automatic approval can bypass the otherwise disclosed panel gate
  • Repository tests are project-owned engineering evidence, not independent product-performance measurements

Capability support

Documented first-class product support, checked against the sources below.

External tools (MCP)
DocumentedProduct-supported MCP integrationSource · checked 2026-08-02The source establishes the mechanism, not its quality or availability in every mode.
Reusable skills
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Local models
DocumentedLocal or self-hosted model pathSource · checked 2026-08-02The source establishes the mechanism, not its quality or availability in every mode.
Agent parallelism
DocumentedDelegated or parallel agent workflowSource · checked 2026-08-02The source establishes the mechanism, not its quality or availability in every mode.
Runs without an open UI
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Browser control
OptionalOptional headless-browser tools; host URL opening remains outside the containerSource · checked 2026-08-02The source establishes the mechanism, not its quality or availability in every mode.
Isolated execution
Available by defaultHardened persistent Docker container by default; direct host mode is availableSource · checked 2026-08-02Isolation weakens materially when direct mode or host Docker-socket access is enabled.
Undo file changes
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.

Getting started

Build the wakil-dev image, build or install the Go binary, point an endpoint at an OpenAI-compatible service, and keep the default Docker execution mode and confirmation gate enabled for untrusted work.

Open official documentation

Classification and operating model

Category fit and technical mechanisms are evidence records, not product-quality scores.

Category fit
Qualifies, 4/4 criteria
Operating model
7/7 layers documented
Inspect category criteria and operating mechanismsFirst-party records

Why it qualifies as a coding harness

This confirms category fit, not product quality. Every required criterion links back to first-party evidence.

Qualifies4 of 4 required criteria evidenced
  • Adaptive agent loop

    Documented

    The system repeatedly observes results and chooses the next action instead of following a fixed one-pass graph.

  • Repository tool execution

    Documented

    The system can use tools to inspect and change a repository or its execution environment.

  • Task-aware context management

    Documented

    The runtime assembles, updates, compacts, retrieves, or persists task-relevant context while work proceeds.

  • Model-independent runtime control

    Documented

    Permissions, budgets, interruption, policy, or stop controls operate outside the model's own text generation.

Membership establishes category fit only. It does not score quality, safety, autonomy, model capability, or benchmark performance. · Read the membership rule.

How it works under the hood

Seven mechanisms mapped from first-party records. These labels describe what the harness provides, not how intelligent its model is.

7/7layers documented
  • Execution & isolationSandbox availableDocumented mechanism, not a performance score.
  • Tooling & integrationsExtensible + browserDocumented mechanism, not a performance score.
  • Context & statePersistent stateDocumented mechanism, not a performance score.
  • Lifecycle & recoverySession resumeDocumented mechanism, not a performance score.
  • ObservabilityStructured tracesDocumented mechanism, not a performance score.
  • VerificationTool-assistedDocumented mechanism, not a performance score.
  • Governance & permissionsApproval promptsDocumented mechanism, not a performance score.

Measured and public context

Configuration-specific measurements and source-native activity stay separate from general product capability.

Inspect code audit, measured configurations, and ecosystem signalsContext, not a product score

Public code audit

4/5public artifacts present
Security policy
Present at inspected commit
CI workflow
Present at inspected commit
Automated tests
Present at inspected commit
Evaluation assets
Not found
Contributor documentation
Present at inspected commit

The inspected early-stage tree contains 300 tracked files, one workflow, 168 test-like paths, and security and contributor policies, but no dedicated evaluation assets or immutable model × harness × environment × budget × attempts result. Engineering tests do not establish product performance, so no score is imported.

Inspect commit 25ff56085007d8e8bdbc4d2f8c74ee4f994a0ed9, checked 2026-08-02

Measured configurations

No benchmark run passes the full metadata admission policy for this harness yet. Missing data is not scored as zero.

Benchmark policy and all runs
Context, not quality

Public ecosystem signals

Source-native observations for exact mapped artifacts and reviewed stable release trains. Different units and populations stay separate, and missing coverage is never treated as zero.

View this harness in Usage
  • OpenRouter 30d tokens20.96B#45 coding app; 2026-08-09 to 2026-09-07Open app page
  • GitHub stars1Full-source repository; 0 forksOpen artifact

Routing, package retrievals, release downloads, editor installs, and repository interest observe different populations. They are never added together and never affect capability evidence, classification, or measured results.

Interpretation rulesSignals checked

First-party evidence

Each capability claim links to the first-party record that supports it.

6 first-party sourcesProduct record checked

Ecosystem context

OpenRouter coding CLI agent directory Used to discover Wakil; OpenRouter is not evidence for capability claims. Observed 2026-07-28.