feat:12309 feat:16012 and others: Command and Agent Library Interface

[xman2000]

There are a few requests for UI's for the commands and agents such as

#12309
#16012

This PR introduces a markdown-based library workflow for reusable commands and agents, and applies it consistently across the Desktop app and TUI.

The core model is now file-based:

commands from .opencode/command//*.md
agents from .opencode/agent//*.md

Metadata for both objects is supported end-to-end (title, description, summary, category, icon, tags), with command-specific fields (agent, model, subtask) and existing agent configuration behavior preserved.

On Desktop, the Library panel now supports category browsing, command search, hover details, command/agent folder actions, and an agent pulldown for insertion context. Command selection inserts content into the composer without auto-send. Two root actions are available at the bottom of the list: Create a New Command and Create a New Agent which allow the user to create new commands and agents that are properly formatted and stored correctly.

On TUI, the sidebar flow has been updated to command/agent terminology and command insertion behavior.

Library content in this branch includes:

a full command set under .opencode/command/
AI commands grouped under .opencode/command/ai/
agent definitions under .opencode/agent/

Compatibility behavior is included:

nested command names remain valid; flat aliases are added when leaf names are unique
agent alias mapping resolves:
docs -> documentation
planning -> plan
triage -> troubleshooting

Documentation updates:

revised README.md fork section to describe current behavior
added .opencode/command/README.md and .opencode/agent/README.md
updated create-command and create-agent templates with explicit input placeholder:
<>

Validation:

bun run typecheck in packages/app
bun run typecheck in packages/opencode
targeted tests added/passing for:
command alias behavior (packages/opencode/test/config/config.test.ts)
agent alias behavior (packages/opencode/test/agent/agent.test.ts)

[github-actions]

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

• PR description is missing required template sections. Please use the PR template.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

Hey! Your PR title Feature 12309 16012 and others: Command and Agent Library Interface doesn't follow conventional commit format.

Please update it to start with one of:

• feat: or feat(scope): new feature
• fix: or fix(scope): bug fix
• docs: or docs(scope): documentation changes
• chore: or chore(scope): maintenance tasks
• refactor: or refactor(scope): code refactoring
• test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

[xman2000]

Issue for this PR

Closes #16012
Closes #12309

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

This PR introduces a markdown-based library workflow for reusable commands and agents.

On Desktop, the Library panel now supports category browsing, command search, hover details, command/agent folder actions, and an agent pulldown for insertion context. Command selection inserts content into the composer without auto-send. Two root actions are available at the bottom of the list: Create a New Command and Create a New Agent which allow the user to create new commands and agents that are properly formatted and stored correctly.

On TUI, the sidebar flow has been updated to command/agent terminology and command insertion behavior.

A library of commands and agents has also been added and the schemas and instructions for both have been expanded.

Everything works with existing keyboard commands and functionality. The goal was to integrate new behavior without disrupting existing workflow.

How did you verify your code works?

I built both TUI and GUI versions including packaging to exe. I then installed the exe on another machine and verified it installed.

Screenshots / recordings

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

If you do not follow this template your PR will be automatically rejected.

[github-actions]

This pull request has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new pull request that follows our guidelines.