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

[FEATURE]: Allow rebinding the subagent active/inactive toggle

Open Beginner friendly
#56,002 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
cli

Research direction

The shortcut is hard-coded as bind: "ctrl+a" for composer.subagent.toggle-activity in packages/tui/src/routes/session/composer/subagents-tab.tsx. Start there, then add the same action to the configurable keybind definitions in packages/tui/src/config/keybind.ts, following how neighboring entries are declared. Done means Ctrl+A stays the default, a cli.json override such as Tab takes effect, the footer shows the configured key, and Tab does not change autocomplete outside the picker.

Written by the indexing model from the issue text.

Description

Feature hasn't been suggested before.
  • I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request

In OpenCode V2's TUI, I'd like to customize the shortcut for “show active / show inactive” in the Subagents picker—for example, use Tab instead of Ctrl+A.

In v2.0.30, composer.subagent.toggle-activity has an inline bind: "ctrl+a", but is missing from the configurable keybind definitions, so it cannot be overridden through cli.json.

Could this action be exposed as a configurable keybind, keeping Ctrl+A as the default? The footer should reflect the configured shortcut, and using Tab should not affect autocomplete outside the picker.

Related: #51903 concerns mouse interaction with the same footer, rather than rebinding.

Dominant language
TypeScript
Stars
213k
Forks
28.4k
Avg merge
8h 58m
Merged PRs (30d)
251

Getting set up

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 anomalyco/opencode

All issues in anomalyco/opencode

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.