-
Notifications
You must be signed in to change notification settings - Fork 39k
Activity
Always looking forward to new updates
The organization/enterprise custom agents and instructions are a great feature
I would like to raise suggestion to consider more fine grained ability - one custom instruction per org is a stretch IMO and experience and it's more likely that a sub set of repos that are managed by a group might have common standards over and entire org or enterprise
Same goes for custom agents
Commented also on #276636 (comment)
I think .github-private is nice storage solution but then solution would benefit if it would be decoupled, exposed with an api and allow more ways to attach to granular groups by direct assignment or dynamic rules(repo associated to teams or by metadata tags)
Also would benefit by collecting stats on which sessions uses which instruction or ran with which custom agents by some ID to measure usage and effectiveness/ROI
I'm taking the liberty to add this comment here for better visibility, apologies if it's better suited somewhere else.
It seems for the last couple of releases, the latest release wasn't being set, so the latest release keeps showing "November 2025 Recovery" .
This is breaking any tooling that queries GitHub for the latest release (e.g. flatpak build systems) because the new releases aren't showing up.
I added this comment to the "December 2025 Recovery 1" release issue .
Have you considered using new build tools to refactor the build process (eg: esbuild, rolldown)? The current gulp speed is too slow
Los agentes personalizados de la organización/empresa y las instrucciones son una gran característica
Me gustaría sugerir que se considere una capacidad de grano más fino: una instrucción personalizada por organización es un tramo en mi opinión y experiencia y es más probable que un subconjunto de repositorios administrados por un grupo pueda tener estándares comunes sobre toda la organización o empresa
Lo mismo ocurre con los agentes de aduanas
Comentado también en #276636 (comment)
Creo que .github-private es una buena solución de almacenamiento, pero entonces la solución se beneficiaría si se desacoplara, se expusiera con una API y permitiera más formas de unirse a grupos granulares mediante asignación directa o reglas dinámicas (repositorio asociado a equipos o por etiquetas de metadatos)
También se beneficiaría de recopilar estadísticas sobre qué sesiones usa qué instrucción o se empetró con qué agentes de aduana por alguna identificación para medir el uso y la efectividad/ROI
This plan captures our work in January 2026. This is a 4-week iteration. We will ship in early February.
Endgame
The endgame details for this iteration are tracked here.
Plan Items
Below is a summary of the top level plan items.
Legend of annotations:
Accessibility
Workbench
Code Editor
Languages
Python
Terminal
API
Source Control
AI
Chat
MCP
Inline Chat
NES / Completions
ICompletionsFetchServicefor completions vscode#277830 @ulugbeknaAgents
Prompt/Instruction Files and Custom Agents
Code Review
Chat: Code Reviewcommand vscode#276977 @benvillalobosEngineering
Documentation
Deferred