-
Notifications
You must be signed in to change notification settings - Fork 17
feat: CoffeeAGNTCY initial docs #176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
feat: CoffeeAGNTCY initial docs #176
Conversation
Signed-off-by: Aditi Gupta <[email protected]>
Signed-off-by: Aditi Gupta <[email protected]>
Signed-off-by: Aditi Gupta <[email protected]>
Signed-off-by: Aditi Gupta <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, I've left a few editorial notes and comments.
@@ -9,5 +9,6 @@ nav: | |||
- Messaging SDK: messaging | |||
- Agent Workflow Server: agws | |||
- CSIT: csit | |||
- CoffeeAGNTCY: coffee-agntcy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The ToC was reorganised in #140, I think in that structure CoffeeAGNTCY should have a more prominent space, right after CSIT maybe.
# Get Started with CoffeeAGNTCY | ||
|
||
|
||
CoffeeAgntcy is a reference implementation built around a fictitious coffee company to demonstrate how components in the AGNTCY Internet of Agents ecosystem work together. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CoffeeAgntcy is a reference implementation built around a fictitious coffee company to demonstrate how components in the AGNTCY Internet of Agents ecosystem work together. | |
CoffeeAGNTCY is a reference implementation built around a fictitious coffee company to demonstrate how components in the AGNTCY Internet of Agents ecosystem work together. |
This project is meant to exemplify how AGNTCY and open-source agentic standards interoperate through clean, reproducible example code. It is purposefully designed for developers across experience levels, from those taking their first steps in building agentic systems to those with more experience curious about AGNTCY's offerings. | ||
|
||
With CoffeeAgntcy, you can: | ||
* How to leverage the AGNTCY App SDK Factory to write transport and agentic protocol-agnostic clients and server code |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* How to leverage the AGNTCY App SDK Factory to write transport and agentic protocol-agnostic clients and server code | |
* Learn how to leverage the AGNTCY App SDK Factory to write transport and agentic protocol-agnostic clients and server code. |
|
||
* Enable observability with the AGNTCY Observe SDK. | ||
|
||
* Learn how to write simple A2A client and server agents |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* Learn how to write simple A2A client and server agents | |
* Learn how to write simple A2A client and server agents. |
|
||
* Learn how to write simple A2A client and server agents | ||
|
||
* Orchestrate agents using LangGraph via the supervisor-worker agent architecture |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* Orchestrate agents using LangGraph via the supervisor-worker agent architecture | |
* Orchestrate agents using LangGraph via the supervisor-worker agent architecture. |
|
||
### Lungo | ||
|
||
Lungo is our evolving demo application. As AGNTCY expands, Lungo grows alongside it, adding new features and capabilities, and demonstrating how they work together in an interoperable ecosystem. Like the Corto demo, it includes a LangGraph-orchestrated supervisor agent, but instead of connecting to a single farm, Lungo integrates with three. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lungo is our evolving demo application. As AGNTCY expands, Lungo grows alongside it, adding new features and capabilities, and demonstrating how they work together in an interoperable ecosystem. Like the Corto demo, it includes a LangGraph-orchestrated supervisor agent, but instead of connecting to a single farm, Lungo integrates with three. | |
Lungo is our ever-evolving demo application. As AGNTCY expands, Lungo grows alongside it. It adds new features and capabilities, demonstrating how they work together in an interoperable ecosystem. Like the Corto demo, it includes a LangGraph-orchestrated supervisor agent, but instead of connecting to a single farm, Lungo integrates with three. |
S-->>U: Unable to proceed with this prompt | ||
|
||
``` | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could add a link here to the Identity docs. Something along the lines of:
"For more information on Identity in AGNTCY, see the Identity documentation."
|
||
## SLIM in CoffeeAGNTCY | ||
|
||
CoffeeAGNTCY uses **SLIM** (Secure Low-Latency Interactive Messaging) as its default transport layer for all inter-agent communication. SLIM supports both **unicast** (1-to-1) and **broadcast** (1-to-many) messaging patterns, making it well-suited for CoffeeAGNTCY’s dynamic multi-agent workflows. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CoffeeAGNTCY uses **SLIM** (Secure Low-Latency Interactive Messaging) as its default transport layer for all inter-agent communication. SLIM supports both **unicast** (1-to-1) and **broadcast** (1-to-many) messaging patterns, making it well-suited for CoffeeAGNTCY’s dynamic multi-agent workflows. | |
CoffeeAGNTCY uses [SLIM](../messaging/slim-core.md) as its default transport layer for all inter-agent communication. SLIM supports both **unicast** (1-to-1) and **broadcast** (1-to-many) messaging patterns, making it well-suited for CoffeeAGNTCY’s dynamic multi-agent workflows. |
@@ -0,0 +1,55 @@ | |||
#SLIM in CoffeeAGNTCY | |||
|
|||
## SLIM in CoffeeAGNTCY |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this header is unnecessary, without it we could move each header under it up one.
|
||
SLIM accommodates both targeted and broadcast messaging within the same API: | ||
|
||
#### 1-to-1 Message |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These could be made into a bullet list instead of headers.
Initial documentation for CoffeeAGNTCY including a: