Skip to content

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

therealaditigupta
Copy link

Initial documentation for CoffeeAGNTCY including a:

  • Getting started guide
  • Identity in CoffeeAGNTCY
  • SLIM in CoffeeAGNTCY

@therealaditigupta therealaditigupta requested a review from a team as a code owner August 8, 2025 17:15
@therealaditigupta therealaditigupta requested review from jubarbot-cisco and removed request for a team August 8, 2025 17:15
@keraron keraron self-requested a review August 11, 2025 13:49
Copy link
Member

@keraron keraron left a 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
Copy link
Member

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.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
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
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
* 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
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
* 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
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
* 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.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
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

```

Copy link
Member

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.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
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
Copy link
Member

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
Copy link
Member

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.

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