Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

vendors: add a zed adapter

Open
  • Is something wrong?
#129 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
76/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
tooling

Research direction

First read Zed's row in src/agentseam/matrix.py and check the related upstream issue's state. Then compare the aider, replit, or junie adapters under src/chock/vendors/, along with src/chock/compile/surfaces.py and the pinning tests. Done means Zed is credited only for supported surfaces and chock check --only matrix and the pinning tests pass.

Written by the indexing model from the issue text.

Description

good first issue help wanted

agentseam carries a zed row in its capability matrix. chock supports 15 agents and
zed is not among them — so a policy authored here cannot be compiled for Zed at all, even
though we already know what Zed's surface looks like.

That makes this an unusually well-scoped adapter task: the research is already done upstream.

What to do:

  1. Read zed's row in agentseam's matrix (src/agentseam/matrix.py) for what its hooks can
    really do. Note its pre_tool grade before you plan the work — it is none, which means
    the honest surfaces here are ambient-rule, git-hook and ci-gate, not pre-tool-use.
  2. Add the vendor under src/chock/vendors/, following an existing adapter with the same
    surface set. aider, replit and junie are all three-surface adapters and are the closest
    models.
  3. Credit only the surfaces Zed actually reaches, in SURFACE_AGENTS.

The rule that governs this: never credit a surface the agent cannot really receive. chock's
whole pitch is that it does not overclaim, and the pinning tests exist to catch exactly that —
chock check --only matrix will tell you if the claim and the code disagree.

Related: agentseam has an open issue to witness Zed on a real run rather than trusting vendor
docs. If that lands first and contradicts the none grade, this adapter gets a fourth surface —
so it is worth checking that issue's state before you start.

Sized to an afternoon. Files: src/chock/vendors/, src/chock/compile/surfaces.py, and the
pinning tests that assert the supported-agent list.

Dominant language
Python
Stars
8
Forks
1
Avg merge
2h 48m
Merged PRs (30d)
121

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from open-coder-ai/chock

All issues in open-coder-ai/chock

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.