Skip to content

feat: add Node.js Agentic Issue Resolver to agents#613

Closed
Impesud wants to merge 6 commits intogithub:mainfrom
Impesud:main
Closed

feat: add Node.js Agentic Issue Resolver to agents#613
Impesud wants to merge 6 commits intogithub:mainfrom
Impesud:main

Conversation

@Impesud
Copy link

@Impesud Impesud commented Jan 27, 2026

Hi team! I'm submitting a new agentic sample.

This project provides a resilient implementation of a developer agent using the GitHub Copilot SDK, specifically optimized to handle the current Technical Preview limitations regarding file modifications.

Compliance:

Follows the AGENTS.md guidelines.

Includes frontmatter and proper file naming (.agent.md).

Moved to a standalone repo as recommended by @friggeri in the copilot-sdk repo.

Looking forward to your feedback!

Erick and others added 2 commits January 27, 2026 10:37
Add documentation for Node.js Agentic Issue Resolver with key features and links.
Copy link
Contributor

@aaronpowell aaronpowell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not really sure that this makes sense as an agent, since it's a standalone sample. We are looking at the best way to support external samples in this repo, so I'll keep the PR open as we refine that

@Impesud
Copy link
Author

Impesud commented Jan 28, 2026

I'm not really sure that this makes sense as an agent, since it's a standalone sample. We are looking at the best way to support external samples in this repo, so I'll keep the PR open as we refine that

Thanks for the feedback, @aaronpowell ! I understand the distinction. I created this as a standalone repository to provide a complete, end-to-end example of a resilient agentic workflow.

I'm happy to wait while you refine the structure for external samples. If you decide to create a 'Community Samples' or 'External Projects' section, I'd be glad to see this included there. Let me know if you need me to move the metadata file or adjust the description in the meantime!

@aaronpowell
Copy link
Contributor

#632 is open to bring the cookbook across from the SDK repo, but I think we'll want a better way to list out external samples.

@Impesud what's your thought on some kind of YAML file that external samples, such as yours, could be listed in and then we'll have a script that automates surfacing them in the repo? Or do you have other thoughts on how to surface them in the repo?

@Impesud
Copy link
Author

Impesud commented Feb 4, 2026

#632 is open to bring the cookbook across from the SDK repo, but I think we'll want a better way to list out external samples.

@Impesud what's your thought on some kind of YAML file that external samples, such as yours, could be listed in and then we'll have a script that automates surfacing them in the repo? Or do you have other thoughts on how to surface them in the repo?

Hi @aaronpowell , I think the YAML approach is the most scalable path forward. It turns this repository into a structured registry, making it easier for scripts to generate tables, galleries, or even a searchable site in the future.

Here is a proposal for a schema that could live in a external-samples.yaml file:

# Proposed schema for external-samples.yaml
samples:
  - id: nodejs-agentic-issue-resolver
    name: "Node.js Agentic Issue Resolver"
    description: "A resilient agentic workflow for autonomous codebase exploration and fixing, optimized to handle Technical Preview limitations."
    url: "https://github.com/Impesud/nodejs-copilot-issue-resolver"
    author:
      name: "Impesud"
      url: "https://github.com/Impesud"
    sdk_version: "Technical Preview" # Useful for tracking breaking changes
    tags: [nodejs, copilot-sdk, agents, automation]
    resilience_features: true # Optional: highlighting samples that solve specific SDK hurdles

I am more than happy to be the first to adopt this format. If you decide to go this way, let me know if you'd like me to create the initial YAML file or if you have a specific location in mind for it.

@aaronpowell
Copy link
Contributor

We could probably leverage https://github.com/github/awesome-copilot/blob/main/cookbook/cookbook.yml

Let me have an experiment around with some structure

@Impesud
Copy link
Author

Impesud commented Feb 5, 2026

We could probably leverage https://github.com/github/awesome-copilot/blob/main/cookbook/cookbook.yml

Let me have an experiment around with some structure

That makes perfect sense, @aaronpowell . Leveraging cookbook.yml is a great way to maintain consistency across the repo. I'm ready to adapt my contribution once you’ve defined the new structure. Standing by for your updates!

@github-actions github-actions bot force-pushed the main branch 17 times, most recently from 14d7f66 to aaed079 Compare February 25, 2026 04:58
@github-actions github-actions bot force-pushed the main branch 12 times, most recently from ea85bbf to 4488150 Compare February 27, 2026 00:07
aaronpowell added a commit that referenced this pull request Feb 27, 2026
Add a Community Samples cookbook section to cookbook.yml with the
Node.js Agentic Issue Resolver as the first external recipe entry,
linking to https://github.com/Impesud/nodejs-copilot-issue-resolver.

Resolves the use case from PR #613 for supporting external samples.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@aaronpowell
Copy link
Contributor

@Impesud sorry it's taken so long to action on this, but I've finally got to it and #831 is the design.

It'll replace this PR, but wanted to get your input on the design

@aaronpowell aaronpowell closed this Mar 1, 2026
aaronpowell added a commit that referenced this pull request Mar 2, 2026
* feat(schema): add external recipe fields to cookbook schema

Add optional external, url, and author fields to the recipe schema
in cookbook.schema.json. When external is true, url is required via
conditional validation. Author supports name (required) and url
(optional) for attribution.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* feat(data): support external recipes in data generator

- External recipes (external: true) skip local file validation
- Validate URL format for external recipes
- Pass through external, url, and author fields to output JSON
- Add per-recipe languages array: derived from resolved variant keys
  for local recipes, and from tags matching known language IDs for
  external recipes
- Collect language IDs in a first pass before processing recipes

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* feat(website): render external recipe cards on cookbook page

- Extend Recipe interface with external, url, author, and languages
- Render external recipes with Community badge, author attribution,
  and View on GitHub link instead of View Recipe/View Example buttons
- Language filter uses per-recipe languages array uniformly
- Remove Nerd Font icons from select dropdown options (native selects
  cannot render custom web fonts)
- Add CSS for external recipe cards (dashed border, badge, author)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* feat(cookbook): add community samples section with first external recipe

Add a Community Samples cookbook section to cookbook.yml with the
Node.js Agentic Issue Resolver as the first external recipe entry,
linking to https://github.com/Impesud/nodejs-copilot-issue-resolver.

Resolves the use case from PR #613 for supporting external samples.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* feat(cookbook): add Copilot SDK Web App to community samples

Add aaronpowell/copilot-sdk-web-app — a full-stack chat app built with
the GitHub Copilot SDK, .NET Aspire, and React.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Apply suggestions from code review

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
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