Repository navigation
Description
开源之夏是由中国科学院软件研究所“开源软件供应链点亮计划”发起并长期支持的一项暑期开源活动,旨在鼓励在校学生积极参与开源软件的开发维护,培养和发掘更多优秀的开发者,促进优秀开源软件社区的蓬勃发展,助力开源软件供应链建设。
Nacos 将作为指导组织参加本次的“开源之夏 2026”。
项目信息
- 项目编号:26ab10082
- 开发周期:3 个月
- 报名语言:中文或英文
- 编程语言:Java、TypeScript
- 技术领域:Cloud Native、AI Registry
- 成果仓库:https://github.com/alibaba/nacos
- 开源协议:Apache-2.0
背景
Nacos AI Registry 已支持 MCP Server、Agent、Prompt、Skill、AgentSpec 等多类 Agentic Resource,并提供 Namespace 隔离、版本管理、生命周期管理和可见性控制等基础能力。
随着 Agentic Resource 数量不断增加,跨 Namespace 的共享和复用需求逐渐突出。现有可见性能力主要解决资源的访问范围问题,尚未形成统一的全局共享入口:资源所有者难以将经过验证的稳定版本便捷地分享给其他用户,资源使用者也缺少集中发现、查看和复用优质资源的方式。
本课题希望建设以共享为核心的 Nacos Agentic Resource Hub。资源所有者可以将已发布版本共享至全局目录,其他用户可以统一发现和使用这些资源,并将其导入自己的 Namespace;具备相应权限时,也可以在同一 Nacos 集群内直接完成 Namespace 之间的资源复制。整个过程需要妥善处理权限、版本、来源追溯、冲突检查和生命周期约束,同时为后续新增 Agentic Resource 类型保留扩展能力。
目标
- 建设 Nacos Agentic Resource Hub,为 MCP Server、Agent、Prompt、Skill、AgentSpec 提供统一的共享与发现入口。
- 支持用户将共享资源导入自己的 Namespace,并在具备相应权限时进行同集群跨 Namespace 复制。
- 完善共享过程中的权限控制、版本管理、来源追溯及生命周期约束。
- 保证能力可扩展且向后兼容,支持后续接入新的 Agentic Resource 类型。
难度
进阶 / Advanced
导师
产出要求
1. Agentic Resource Hub
- 支持 MCP Server、Agent、Prompt、Skill、AgentSpec 的统一共享与取消共享。
- 仅允许共享已发布的明确版本,并支持调整当前共享版本。
- 提供全局共享目录,支持资源浏览、搜索、筛选、详情查看和内容获取。
- 保证 Namespace 隔离和资源可见性边界,避免私有资源或无权访问的信息泄露。
- 正确处理源资源下线、删除、版本变化等场景,保证共享状态与资源生命周期一致。
2. 跨 Namespace 资源复用
- 支持将共享资源导入有写权限的目标 Namespace,并生成可独立编辑、评审和发布的资源草稿。
- 保留来源资源及版本信息,便于后续追溯;导入后的资源拥有独立生命周期,不与来源自动同步。
- 支持在具备源 Namespace 读取权限和目标 Namespace 写入权限时,直接进行同集群跨 Namespace 复制。
- 在执行导入或复制前完成权限、名称、版本及依赖冲突检查,并提供明确的处理结果。
3. 产品入口与扩展能力
- 在 Nacos Console 中提供 Agentic Resource Hub 入口,以及共享、取消共享、导入和复制等操作。
- 为 Java Maintainer Client 和 Nacos CLI 提供相应能力,满足自动化和批量使用场景。
- 形成统一、可扩展的资源接入方式,使新增 Agentic Resource 类型能够复用共享、发现和导入流程。
- 保持现有 AI Registry 管理和访问方式兼容,未启用共享能力时不影响原有行为。
4. 测试与文档
- 补充必要的单元测试、API 集成测试、客户端测试和端到端场景验证。
- 覆盖五类 Agentic Resource 的共享、发现、导入、复制、权限校验和异常场景。
- 提供用户文档、接口文档、扩展说明、示例资源及可重复执行的演示流程。
- 确保所有代码通过 Nacos 的代码检查、单元测试及相关集成测试。
能力要求
- 熟悉 Java、Spring Boot 及 REST API 开发。
- 了解持久化、事务和基本的数据一致性问题。
- 理解 Namespace、多租户、权限控制和资源可见性等概念。
- 了解版本管理及草稿、评审、发布、下线等资源生命周期。
- 具备单元测试、集成测试和端到端测试经验。
- 具备基础的 React、TypeScript 前端开发能力。
- 熟悉 Maven、Git 和 Markdown。
- 具有 SDK、CLI 或可扩展系统设计经验者优先。
Open Source Promotion Plan is a summer program initiated and continuously supported by the Institute of Software, Chinese Academy of Sciences. It encourages students to participate in the development and maintenance of open-source software, helps communities discover and cultivate new contributors, and promotes the sustainable development of the open-source software supply chain.
Nacos will participate in Open Source Promotion Plan 2026 as a mentoring organization.
Project Information
- Project ID: TBD
- Duration: 3 months
- Application Language: Chinese or English
- Programming Languages: Java, TypeScript
- Technical Fields: Cloud Native, AI Registry
- Repository: https://github.com/alibaba/nacos
- License: Apache-2.0
Background
Nacos AI Registry already supports multiple types of Agentic Resources, including MCP Server, Agent, Prompt, Skill, and AgentSpec. It also provides foundational capabilities such as Namespace isolation, version management, lifecycle management, and visibility control.
As the number of Agentic Resources grows, the need to share and reuse them across Namespaces becomes increasingly important. Existing visibility controls mainly define the access scope of a resource, but they do not provide a unified global sharing entry. Resource owners lack a convenient way to share verified, stable versions with others, while resource consumers lack a central place to discover, inspect, and reuse high-quality resources.
This project aims to build Nacos Agentic Resource Hub with sharing as its core capability. Resource owners can share published versions through a global catalog. Other users can discover and use these resources from one place and import them into their own Namespaces. With the required permissions, users can also copy resources directly between Namespaces in the same Nacos cluster. The complete flow must handle authorization, versions, provenance, conflict checks, and lifecycle constraints, while remaining extensible for future Agentic Resource types.
Target
- Build Nacos Agentic Resource Hub as a unified sharing and discovery entry for MCP Server, Agent, Prompt, Skill, and AgentSpec resources.
- Allow users to import shared resources into their own Namespaces and, with the required permissions, copy resources between Namespaces in the same cluster.
- Provide consistent authorization, version management, provenance, and lifecycle constraints throughout the sharing flow.
- Keep the capability extensible and backward compatible so that future Agentic Resource types can be integrated.
Difficulty
Advanced
Mentor
TBD
Output Requirements
1. Agentic Resource Hub
- Support unified sharing and unsharing for MCP Server, Agent, Prompt, Skill, and AgentSpec resources.
- Allow only explicit published versions to be shared, and support changing the currently shared version.
- Provide a global catalog for browsing, searching, filtering, inspecting, and retrieving shared resources.
- Preserve Namespace isolation and resource visibility boundaries to prevent private or unauthorized information from being exposed.
- Correctly handle source-resource unpublishing, deletion, and version changes so that sharing state remains consistent with the resource lifecycle.
2. Cross-Namespace Resource Reuse
- Allow a shared resource to be imported into a writable target Namespace as a draft that can be edited, reviewed, and published independently.
- Preserve source-resource and version information for provenance. Imported resources must have independent lifecycles and must not automatically synchronize with their sources.
- Allow direct resource copying between Namespaces in the same cluster when the user has read permission on the source Namespace and write permission on the target Namespace.
- Check permissions and detect name, version, and dependency conflicts before import or copy, with clear results for the user.
3. Product Entry and Extensibility
- Add an Agentic Resource Hub entry to Nacos Console, together with sharing, unsharing, import, and copy operations.
- Expose corresponding capabilities through the Java Maintainer Client and Nacos CLI for automation and batch workflows.
- Establish a unified and extensible resource onboarding approach so that future Agentic Resource types can reuse the sharing, discovery, and import flows.
- Remain compatible with existing AI Registry management and access patterns. Existing behavior must remain unchanged when sharing is not used.
4. Testing and Documentation
- Add the necessary unit tests, API integration tests, client tests, and end-to-end scenario verification.
- Cover sharing, discovery, import, copy, authorization, and error scenarios for all five Agentic Resource types.
- Provide user documentation, API documentation, extension guidance, sample resources, and a reproducible demonstration flow.
- Ensure that all changes pass Nacos code checks, unit tests, and related integration tests.
Technical Requirements
- Proficiency in Java, Spring Boot, and REST API development.
- Understanding of persistence, transactions, and basic data-consistency concerns.
- Understanding of Namespaces, multi-tenancy, authorization, and resource visibility.
- Familiarity with version management and resource lifecycles, including draft, review, publish, and unpublish stages.
- Experience with unit, integration, and end-to-end testing.
- Basic experience with React and TypeScript frontend development.
- Familiarity with Maven, Git, and Markdown.
- Experience with SDKs, CLIs, or extensible system design is a plus.
Activity
nacos-community commentedon Sep 3, 2026
Issue Evaluation
Category:
kind/notice| Status: EvaluatedThis is an official Open Source Promotion Plan 2026 (开源之夏) project announcement posted by the Nacos community, describing the "Agentic Resource Hub" project (cross-namespace sharing, discovery and reuse of Agentic Resources) for student applicants.
It is not a bug report or a user feature request, so no triage, code verification, or automated PR action is required. The
Summerlabel already tracks it.Automated evaluation by github-manager-bot
[ISSUE alibaba#15799] Align console assets and Hub checks with the pr…
[ISSUE #15799] Sync develop into summer-ospp#15799 (#15937)
[ISSUE alibaba#15799] Align console assets and Hub checks with the pr…
[ISSUE alibaba#15799] Reuse Skill APIs for Hub discovery and shared r…
[ISSUE alibaba#15799] Cover authenticated Header password dialog states
[ISSUE alibaba#15799] Fix Hub rollback, source errors and namespace g…
[ISSUE #15799] Add Skill support for Agentic Resource Hub (#15913)
[ISSUE alibaba#15799] Extend Agentic Resource Hub to four resource types
[ISSUE alibaba#15799] Warn before lifecycle changes revoke Hub sharing