microsoft / microsoft/apm

[FEATURE] Add to OpenCode a custom agent with tools as list

Open
#3,009 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/multi-target status/deferred theme/portability triage/recommended type/feature
Dominant language
Python
Stars
3.8k
Forks
362
Avg merge
1d 17h
Merged PRs (30d)
132

Description

I tried to add a custom agent (arch-linux-expert.agent.md - https://github.com/github/awesome-copilot/blob/main/agents/arch-linux-expert.agent.md) for test; my targets are: copilot, antigravity, opencode.
For Antigravity there's another open issue about sub-agents (https://github.com/microsoft/apm/issues/2990), so this is for opencode.
I had this error:

[!] [awesome-copilot-arch-linux-expert] OpenCode agent 'awesome-copilot-arch-linux-expert/arch-linux-expert.agent.md' has tools as list; OpenCode requires a mapping of tool-name to boolean. OpenCode will reject this agent at load time. Fix: rewrite the frontmatter as 'tools: {Read: true, Grep: true}'.
[!] 1 dependency unpinned: github/awesome-copilot -- add #tag or #sha to prevent drift

I noticed lots of custom agents specify tools in list format, so this could be a problem with much of them.

Contributor guide

Open the contributing guide

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.

Research direction

Start by tracing how OpenCode custom-agent frontmatter is loaded and validated, then compare it with the tools list in arch-linux-expert.agent.md. Determine how the package should handle agents whose tools use list syntax, and verify that the affected agents load successfully without the reported warning.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown, yaml
Domain
ai-infra-agents, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.