Repository navigation
✨🧑💻 - Dogfooding add bounded read only copilot history #463
Description
Is there an existing issue or feature request for this?
- I have searched the existing issues and feature requests.
What area does this improvement affect?
None
What actions does this improvement affect?
No response
Description of the idea or improvement
Add /copilot history with no arguments, no model and no mutation. Publish one localized correlated reply containing at most ten recent supported command operations in the exact issue or PR conversation, ordered by source comment identity, excluding the current request and history-query replies. Reuse trusted bot-owned correlated semantic receipts and existing command parsing. Show operation, honest outcome, source request and receipt links, and only validated structured commit evidence when available. Never infer success from a human command, raw Result.steps or untrusted prose. Deduplicate replayed operations by exact target plus correlation identity. Preserve unavailable/partial states when comment pagination or reads are incomplete; do not claim a global audit log. Do not echo arbitrary arguments, prompts, secrets or raw errors. No new persistence store or configuration flag; deterministic English/Spanish rendering and existing publication reconciler.
Current limitations or challenges
Long dogfooding conversations accumulate commands, retries, receipts and branch effects. A developer currently has to reconstruct them manually. The feature should summarize evidence already retained by the Action without duplicating notifications or overstating old, incomplete or forged records.
Expected impact
After several real operations, a developer can inspect the last ten evidenced operations and follow each request/receipt safely. Replays reuse one history reply; new queries receive their own response. Distinct issue/PR targets, malformed/foreign markers, unsupported commands, incomplete reads, duplicate receipts, pending/failure/success and unsafe content are covered. Plan at least 28 distinct risk-derived cases plus documentation, catalog and executable acceptance. Existing operational and authorization behavior stays intact.
Alternatives considered
No response
Version of copilot
master
Additional context or comments
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
vypbot commentedon Oct 11, 2026
SDD work status
Current status: The SDD is published; implementation can begin after branch verification.
SDD:
specs/copilot-history.md· Branch:feature/463-dogfooding-add-bounded-read-only-copilot-history· First commit:10d5da4959f7607baf24b94ec005864345a429a4Links: SDD · Branch · Commit
[-]Dogfooding add bounded read only copilot history[/-][+]✨ - Dogfooding add bounded read only copilot history[/+]vypbot commentedon Oct 11, 2026
Hi! I’m @vypbot, the Copilot assistant for this repository.
I can answer questions, explain the codebase, propose implementation and test plans, review issues and pull requests for potential bugs or security problems, and help authorized maintainers apply changes.
Try
/copilot helpto see the available commands, or mention @vypbot with your question.68 remaining items
vypbot commentedon Oct 13, 2026
Branch synchronization needs attention. Open the current status.
Merge pull request #468 from vypdev/feature/463-dogfooding-add-bounde…
vypbot commentedon Oct 13, 2026
Branch synchronization needs attention. Open the current status.