Expand parser support for additional harnesses

[aymenfurter]

Broaden harness coverage beyond what we support today. Attempts so far: pi harness (#93), Gemini CLI (#98), Kilo (#108).

Not a priority right now: limited bandwidth, and each harness adds ongoing maintenance. Holding off rather than half-supporting.

Branches jvanvelu/add-pi-harness, feat/gemini-cli-support, add-kilo-code-parser, plus src/core/parser-harnesses.ts, are the starting points when we revisit.

[github-actions]

🎯 Triage report

This is a valid feature request to expand parser coverage to additional harnesses, with concrete prior attempts called out (#93, #98) and a code starting point in src/core/parser-harnesses.ts. The issue is actionable at a backlog level, but it is not yet scoped tightly enough for direct implementation because it bundles multiple harness decisions and ongoing support expectations.

📊 Assessment

Dimension	Value	Reasoning
Type	unchanged	The content clearly reads as a feature request, but I left type metadata unchanged rather than risk overwriting any existing issue type.
Labels	enhancement, backlog	enhancement is already present; backlog fits the explicit "not a priority right now" note.
Severity	Low	This is a capability expansion request, not a reported regression or broken core workflow.
Coding agent	Not suitable	The issue needs product/maintenance scoping first: which harnesses are in scope, what support bar is acceptable, and whether to track each harness separately.

🔗 Similar issues

• feat: add Windsurf (Cascade) session parser #75 (related) — another parser-support request, but for a specific harness with concrete acceptance criteria; related domain, not the same ask.

💡 Notes and suggestions

A good next maintainer step would be to split this umbrella request into per-harness issues once prioritization changes, so each item has clear acceptance criteria, sample data requirements, parser integration tasks, and tests.

Suggested breakdown:

• Decide which additional harnesses are officially in scope first (for example, pi vs Gemini CLI).
• Create one issue per harness with acceptance criteria and sample session/log requirements.
• Reuse the exploratory work already referenced here (jvanvelu/add-pi-harness, feat/gemini-cli-support, and src/core/parser-harnesses.ts).
• Define the minimum maintenance bar per harness: parser implementation, fixture coverage, and regression tests.
• Update supported-tools docs only after a harness is fully supported.

Generated by Agentic Triage for issue #151 · 55.8 AIC · ⌖ 14.2 AIC · ⊞ 22.4K · ◷

Add this agentic workflows to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/issue-triage.md@df35cf29fb856d1c3b8f023ed46d19126e7813bf

[rCartoux]

@aymenfurter Would you consider adding Visual Studio as a supported harness under this tracking issue?

As an enterprise .NET user, GitHub Copilot in Visual Studio is my primary workflow, it would be very valuable to benefit from AI Engineer Coach analyses there as well.

(see initial POC PR in my fork Add support for Visual Studio POC )

Thanks!