Skip to content

Conversation

@jpoz
Copy link
Contributor

@jpoz jpoz commented May 20, 2025

This PR allows users to override default keymaps:

{
  "data": {},
  "tui": {
    "theme": "opencode"
  },
  "shell": {},
  "keyMaps": {
    "chat": {
      "toggleTools": [
        "ctrl+b"
      ]
    }
  }
}

It also updates the help dialog:

image

And the bar above the message input:

image

@jpoz jpoz marked this pull request as ready for review May 21, 2025 18:05
@adamdotdevin
Copy link
Contributor

hey, sorry for being slow, on vacation this week. i'm hesitant to merge anything that touches config while #38 is in progress, we're rewriting all of the config stuff (and the backend) in typescript. let me discuss with dax and circle back. really appreciate the PR, we definitely want keymaps to be configurable!

@jpoz
Copy link
Contributor Author

jpoz commented May 23, 2025

@adamdottv oh wow. what's the motivation to move from go -> ts?

@adamdotdevin
Copy link
Contributor

to be clear, the TUI will continue as a go app (with bubbletea), there will just be a clearer separation of client/server. and there were a bunch of factors, but leveraging the AI SDK to reduce scope and eliminate all provider related bugs/changes was a big one.

@jpoz
Copy link
Contributor Author

jpoz commented Jun 3, 2025

Interesting, I was surprised ya'll are writing that yourself instead of using something like https://github.com/tmc/langchaingo/tree/main/llms

Lmk how I can help

@thdxr
Copy link
Contributor

thdxr commented Jun 14, 2025

closing as we rewrote the codebase - appreciate it though!

@thdxr thdxr closed this Jun 14, 2025
m-pa pushed a commit to m-pa/opencode that referenced this pull request Dec 4, 2025
# Description

- Updated JSX.Element type from React.ReactElement<any, any> to
React.ReactNode for broader compatibility
- Enhanced IntrinsicElements to extend React's built-in JSX elements
while adding OpenTUI components
- Fixed ElementClass interface to properly extend React's ComponentClass
randomm added a commit to randomm/opencode that referenced this pull request Jan 9, 2026
* fix(anomalyco#41): correct Perplexity tool names across configs and prompts

Replace incorrect tool references with actual MCP server tool names:
- mcp_perplexity_research → perplexity-ask_deep_research
- mcp_perplexity_ask → perplexity-ask_search, perplexity-ask_reason, perplexity-ask_deep_research

Files updated:
- opencode.work.json: 28 tool references across 14 agents
- opencode.personal.json: 28 tool references across 14 agents
- 18 prompt files with corrected Perplexity tool names

This fixes tool invocation errors when agents attempt to use Perplexity research capabilities.

* feat(anomalyco#40): add research-backed boundary definitions to agent prompts

Implement minimal, evidence-based prompt improvements to prevent
agents from attempting GitHub operations outside their scope:

PM prompt (4 lines):
- Explicit coordination-only boundary
- GitHub ops delegation to git-agent
- Issue verification requirement

Specialist prompts (6 lines each × 13):
- Standardized scope boundary section
- Do-not checklist (keyword format)
- Cross-domain escalation protocol
- Pre-work validation checklist

Research basis: Perplexity research on prompting best practices
found checklist/keyword format achieves 2-3x better compliance
than narrative prose with fewer tokens.

Files: 14 prompts updated, 97 lines total

* feat(anomalyco#44): expand PM tools and standardize on ripgrep over grep

Research-backed expansion of PM tool permissions to enable
effective context gathering for informed routing decisions.

PM tool additions (read-only):
- cat * (all files, not just .project-id)
- rg* (ripgrep for fast, gitignore-aware search)
- jq* (JSON parsing for GitHub API responses)
- wc* (counting and statistics)

New instruction file: instructions/tool-preferences.md
- System-wide mandate: Use rg over grep
- Rationale: faster, respects .gitignore, better defaults
- Usage examples and common patterns

Research basis: Industry best practice shows orchestrators
need read access for informed routing decisions (Perplexity
research on multi-agent systems 2024-2025).

Files: 2 configs, 1 new instruction, 1 prompt (4 total)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants