You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ee72a72
Browse filesBrowse the repository at this point in the historyBrowse files
* refactor: decouple ARGI runtime from model SDKs
Introduce JDK-only argi-api contracts and four optional ChatClient adapters with Spring Boot auto-configuration. Migrate Graph, ReAct, built-in nodes and Studio to neutral model and tool contracts without legacy builder aliases.
Group adapters and starters, verify independent API consumers and enforce SDK isolation across production sources, bytecode and runtime dependency trees. Add gated real-model integration tests and release dependency auditing.
* feat
Signed-off-by: yuluo-yx <[email protected]>
* updated
Signed-off-by: yuluo-yx <[email protected]>
---------
Signed-off-by: yuluo-yx <[email protected]>
Copy file name to clipboardExpand all lines: AGENTS.md
+27-9Lines changed: 27 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ This file provides guidance for AI assistants working with the ARGI codebase.
4
4
5
5
## Project Overview
6
6
7
-
ARGI (Agent Runtime and Graph Intelligence, pronounced "AR-jee") is a production-ready framework for building agents, workflows, and multi-agent applications. It is forked from Spring AI Alibaba and focuses on stateful agent runtime capabilities: graph orchestration, persistence, context engineering, and human-in-the-loop support. It also supports the multi-model integration capabilities provided by Spring AI.
7
+
ARGI (Agent Runtime and Graph Intelligence, pronounced "AR-jee") is a production-ready framework for building agents, workflows, and multi-agent applications. It is forked from Spring AI Alibaba and focuses on stateful agent runtime capabilities: graph orchestration, persistence, context engineering, and human-in-the-loop support. Its runtime consumes framework-neutral `argi-api` contracts. Spring AI, LangChain4j, Google ADK Java, and AgentScope Java are isolated in optional adapters.
8
8
9
9
> **Naming:** the product display name is *ARGI*. Published Maven coordinates use `io.github.agentic-ai-java:argi-*`, Java packages use `io.github.agentic.ai`, configuration prefixes use `argi.*`, and framework-specific public class names use the `Argi*` prefix.
10
10
@@ -14,23 +14,39 @@ ARGI (Agent Runtime and Graph Intelligence, pronounced "AR-jee") is a production
14
14
- Context Engineering with human-in-the-loop, context compaction, editing, model call limits
15
15
- Graph-based workflow with conditional routing, nested graphs, parallel execution
16
16
- A2A (Agent-to-Agent) client support (Nacos service discovery lives in the Extensions repository)
17
-
- Multi-model integration through Spring AI, plus MCP (Model Context Protocol)
17
+
- Multi-model integration through four optional ChatClient adapters, plus MCP (Model Context Protocol)
18
18
- Embedded visual debugging studio
19
19
20
20
## Repository Structure
21
21
22
22
```
23
23
argi/
24
+
├── argi-api/ # ChatClient contracts and framework adapters (directory group)
25
+
│ ├── argi-api-base/ # Publishes argi-api; JDK-only public contracts
The directory groups are not additional Maven artifacts. The root `pom.xml` lists
45
+
their child modules directly; every child inherits the root parent using
46
+
`../../pom.xml`. The public API artifact remains `argi-api`, and its Java packages
47
+
remain `io.github.agentic.ai.api.*`. Use artifact selectors such as `-pl :argi-api`
48
+
or the complete child directory path when selecting a module for a build.
49
+
34
50
This repository holds the core only. Optional integrations live in separate repositories:
35
51
36
52
-[Extensions](https://github.com/agentic-ai-java/argi-extensions) - model and document contracts, A2A Nacos, config Nacos, AgentScope, JDBC/Redis/MongoDB graph persistence, the Docker code executor, and the tool-call sandbox.
@@ -77,9 +93,11 @@ make licenses-check
77
93
78
94
### Technology Stack
79
95
80
-
-**Framework**: Spring Boot 4.1.x, Spring AI 2.0.x
81
-
-**Model and Integration Layer**: Spring AI multi-model integrations, model starters, MCP, A2A, and Nacos
82
-
-**Observability**: Spring Cloud Observation (Micrometer/OpenTelemetry)
96
+
-**Framework**: Java 17; Spring Boot 4.1.x for optional starters and Studio
97
+
-**Model and Integration Layer**: `argi-api` contracts and four isolated provider adapters; MCP and A2A integrations
98
+
-**Observability**: Lightweight Micrometer observation; no required OpenTelemetry deployment
99
+
100
+
Core production sources, bytecode, and runtime dependency trees must remain free of provider SDKs. Native SDKs in core test fixtures must use test scope. This is a breaking replacement, not a deprecated compatibility bridge.
83
101
84
102
## Code Style & Conventions
85
103
@@ -139,10 +157,10 @@ The project uses `make` for linting tasks:
139
157
## Tips for AI Assistants
140
158
141
159
1.**JDK Version**: Project targets JDK 17. Use appropriate language features.
142
-
2.**Spring Boot**: Uses Spring Boot 4.1.1 with Spring AI 2.0.1. The `jakarta.*` namespace applies throughout; there is no `javax.*` code.
160
+
2.**Spring Boot**: Uses Spring Boot 4.1.1. Spring AI 2.0.1 belongs only to its adapter and native test fixtures. The `jakarta.*` namespace applies throughout; there is no `javax.*` code.
143
161
3.**Dependencies**: Check `argi-bom` or parent pom for version management.
144
162
4.**Makefile**: Use the Makefile in the root for project maintenance tasks (linting, license checks).
145
-
5.**Structure**: When adding new features, prefer creating or updating modules within `argi-agent-framework` or `spring-boot-starters` depending on the scope.
163
+
5.**Structure**: Keep neutral contracts and framework adapters in `argi-api`, Spring Boot auto-configuration in `argi-spring-boot-starter`, and agent runtime features in `argi-agent-framework`.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+14-4Lines changed: 14 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
5
5
## Thank you for contributing to ARGI!
6
6
7
-
Since its open-source inception, ARGI has received attention from many community members. Every Issue and PR from the community helps the entire project and contributes to building a better Spring AI.
7
+
Since its open-source inception, ARGI has received attention from many community members. Every Issue and PR from the community helps the entire project and contributes to building a better ARGI.
8
8
9
9
We sincerely thank the developers who have submitted Issues and PRs for this project. We hope more community developers will join us to make this project even better.
10
10
@@ -67,9 +67,19 @@ To ensure code cleanliness, please remove any unused imports in your Java files.
67
67
68
68
Use the `type(scope): description` format for commit messages and PR titles; `scope` is optional. Common types are `fix`, `feat`, `refactor`, `docs`, `chore`, `perf`, `infra`, `revert`, `release`, `test`, and `style`.
69
69
70
-
GitHub Actions checks do not run when a pull request is opened or updated, and no welcome message or label is added automatically. Once a pull request is reviewed and merged into `main`, CI runs the build, test, lint, license, and secret checks on the `push` event; pushing directly to `main` triggers the same checks. Review requirements are managed by repository branch protection or rulesets.
71
-
72
-
Because nothing runs at pull-request time, run the local checks yourself before submitting.
70
+
The build-and-test workflow runs on pull requests targeting `main` and pushes to
71
+
`main`; feature-branch pushes do not trigger a second full pipeline. Job repository
72
+
guards restrict runs to `agentic-ai-java/argi`, but do **not** exclude fork-origin
73
+
pull requests opened against that upstream repository. Those runs execute the PR
74
+
checkout's local actions and scripts with read-only repository permissions and
75
+
without repository secrets. GitHub's fork-workflow approval settings still apply;
76
+
maintainers should review untrusted workflow/script changes before approving runs.
77
+
No welcome message or label is added automatically. Review requirements are
78
+
managed by repository branch protection or rulesets.
79
+
80
+
Run local checks before submitting even when upstream CI is available. The CI
81
+
test job installs the tested artifacts once, then uses
82
+
`verify-api-contract.sh --skip-install` to compile the independent consumer.
-**Open integrations**: support for multi-model integration capabilities provided by Spring AI, plus tool calling, MCP, A2A, and Nacos.
31
+
-**Open integrations**: a neutral ChatClient with Spring AI, LangChain4j, Google ADK, and AgentScope adapters, plus tool calling, MCP, A2A, and Nacos.
32
32
-**Visual debugging**: an embeddable Agent Chat UI for Spring Boot applications.
33
33
34
34
## Quick Start
@@ -49,19 +49,20 @@ cd argi-examples
49
49
mvn -f examples/chatbot/pom.xml spring-boot:run
50
50
```
51
51
52
-
The examples also require the matching Extensions BOM and provider starters. See the [example setup](https://github.com/agentic-ai-java/argi-examples/tree/main/examples#环境与依赖).
52
+
The examples also require the matching Extensions BOM and provider starters. See the [example setup](https://github.com/agentic-ai-java/argi-examples/tree/main/examples#环境与依赖). Examples using older Spring AI agent builders require the direct-replacement migration described in [API and Adapters](argi-api/README.md); that external repository is not migrated by this change.
53
53
54
54
Open [http://localhost:8080/chatui/index.html](http://localhost:8080/chatui/index.html). See the [Quick Start](https://agentic-ai-java.github.io/argi-website/en/docs/quick-start) for other model providers.
55
55
56
56
## Modules
57
57
58
58
| Module | Description |
59
59
| --- | --- |
60
+
|[API and Adapters](argi-api)| Framework-neutral ChatClient contracts and Spring AI, LangChain4j, Google ADK, and AgentScope adapters |
60
61
|[Agent Framework](argi-agent-framework)| Agent development and multi-agent orchestration |
61
62
|[Graph Core](argi-graph-core)| State management, persistence, and workflow runtime |
62
63
|[Studio](argi-studio)| Visual debugging UI for agents |
63
64
|[Sandbox](https://github.com/agentic-ai-java/argi-extensions/tree/main/sandbox/argi-sandbox)| Optional isolated execution environment for tool calls, maintained in Extensions |
64
-
|[Spring Boot Starters](spring-boot-starters)| Built-in graph nodes and graph observability |
65
+
|[Spring Boot Starters](argi-spring-boot-starter)| Built-in graph nodes, graph observability, and four adapter auto-configurations|
65
66
|[Extensions](https://github.com/agentic-ai-java/argi-extensions)| Model and document contracts, A2A, Nacos, AgentScope, storage, and other optional integrations |
66
67
|[Examples](https://github.com/agentic-ai-java/argi-examples/tree/main/examples)| Chatbot, multi-agent, graph engineering, and documentation examples |
0 commit comments