feat(mcp): ask the user mid-call when no index exists (elicitation)

未关闭
#121 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
22/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
go

调研方向

The payload names no source files, so start with the requirement MRTR-01 in the linked planning file and the open question about #74 (serve --mcp outside an indexed repo). Settle how the server negotiates client capability before any prompt is sent. Done means wire-oracle transcripts exist for a client that supports the prompt and one that does not, and both behave as specified.

由索引模型根据 Issue 内容生成。

描述

area:mcp feature priority:low spec-needed
What problem does this solve?

In an unindexed repo, the MCP server returns an empty tool set or an error, and the agent has to work out that codegraph init is the remedy.

What should it do?

Use resultType: "input_required" to ask "no index found here, initialize now?" and proceed on yes.

Which surface does this affect?

MCP (agent-facing tools)

Is this covered by an existing command or tool today?

No. Note the interaction with #74 (serve --mcp outside an indexed repo).

Acceptance criteria
  • Behavior behind client capability negotiation; wire-oracle transcripts for a client that supports it and one that does not.

Source (GSD planning files, archived at d384473e): .planning/milestones/v0.3.0-REQUIREMENTS.md:62 (MRTR-01); .planning/ROADMAP.md (Later)


🤖 Generated with Claude Code

https://claude.ai/code/session_01UNqdnC3q6U362BvyfxuKCF

主要语言
Go
星标
0
派生
0
平均合并
7 小时 42 分钟
30 天内合并 PR
111

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

seanb4t/codegraph-go 的其他 Issue

查看 seanb4t/codegraph-go 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。