Skip to content

✨🧑‍💻 - Dogfooding add bounded read only copilot history #463

Closed

Description

@efraespada

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

Activity

  1. added
    enhancementNew feature or request
    priority: lowNot urgent, can be addressed later.
    featureLabel to manage feature branches
    in-progressStart work on an admitted issue.
    on Oct 11, 2026
  2. added theissue type on Oct 11, 2026
  3. moved this to Todo in vypdevon Oct 11, 2026
  4. added
    SDDAn SDD update is required before branch work.
    on Oct 11, 2026
  5. vypbot commented on Oct 11, 2026

    @vypbot
    Contributor

    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: 10d5da4959f7607baf24b94ec005864345a429a4

    Links: SDD · Branch · Commit

  6. changed the title [-]Dogfooding add bounded read only copilot history[/-] [+]✨ - Dogfooding add bounded read only copilot history[/+] on Oct 11, 2026
  7. added
    state:specifyingThe issue contract is being clarified and specified.
    and removed on Oct 11, 2026
  8. vypbot commented on Oct 11, 2026

    @vypbot
    Contributor

    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 help to see the available commands, or mention @vypbot with your question.

  9. 68 remaining items

  10. vypbot commented on Oct 13, 2026

    @vypbot
    Contributor

    Branch synchronization needs attention. Open the current status.

  11. added a commit that references this issue on Oct 13, 2026
  12. vypbot commented on Oct 13, 2026

    @vypbot
    Contributor

    Branch synchronization needs attention. Open the current status.

  13. added
    100%Progress: 100%
    and removed
    in-progressStart work on an admitted issue.
    on Oct 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

100%Progress: 100%SDDAn SDD update is required before branch work.branchedIndicates that a branch has been created for this issue.enhancementNew feature or requestfeatureLabel to manage feature branchespriority: lowNot urgent, can be addressed later.size: XXLIndicates an extremely large task or issue that requires significant time and effort to complete.

Projects

  • Status
    Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions