Skip to content

Proposal: Conversation API#59

Merged
yaron2 merged 10 commits into
dapr:mainfrom
daixiang0:conversation
Aug 29, 2024
Merged

Proposal: Conversation API#59
yaron2 merged 10 commits into
dapr:mainfrom
daixiang0:conversation

Conversation

@daixiang0

@daixiang0 daixiang0 commented Jun 18, 2024

Copy link
Copy Markdown
Member

It is the initial version to integrate.

The API token here is string for the first version, next we can store it by Crypto component.

Comment thread 20240618-RCBS-Conversation-building-block.md Outdated
Comment thread 20240618-RCBS-Conversation-building-block.md Outdated
@yaron2

yaron2 commented Jun 19, 2024

Copy link
Copy Markdown
Member

Eligible for binding votes: @daixiang0, @yaron2, @artursouza, @mukundansundar, @JoshVanL

Signed-off-by: Loong <[email protected]>
@yaron2

yaron2 commented Jun 28, 2024

Copy link
Copy Markdown
Member

Proposal looks good. Since a main benefit of this API lies in its abstraction layer, it would be good to have at least two components to begin with for the Alpha stage. Which components would be a good fit for the first stage in your opinion?

@daixiang0

Copy link
Copy Markdown
Member Author

OpenAI is good for start, most LLM support it.

Signed-off-by: Loong <[email protected]>
@yaron2

yaron2 commented Jul 1, 2024

Copy link
Copy Markdown
Member

It would also be good to investigate how we can integrate with LangChain and offer higher level integrations for it with existing APIs like state, pub/sub and workflows in addition to providing native Dapr features like authentication, authorization and resiliency policies.

@daixiang0

daixiang0 commented Jul 1, 2024

Copy link
Copy Markdown
Member Author

This article may help us think better to integrate Conversation API with existing APIs. Also, it shows an issue -- the existing LLM framework is not good for startups to quickly iterate, which is our chance.

The first step we can easily move is integrate Crypto API to use LLM API keys.

Signed-off-by: Loong <[email protected]>
Signed-off-by: Loong <[email protected]>
Comment thread 20240618-RCBS-Conversation-building-block.md
Signed-off-by: Loong <[email protected]>
Signed-off-by: Loong <[email protected]>
@yaron2

yaron2 commented Aug 8, 2024

Copy link
Copy Markdown
Member

+1 binding

Comment thread 20240618-RCBS-Conversation-building-block.md Outdated
Comment thread 20240618-RCBS-Conversation-building-block.md Outdated
Comment thread 20240618-RCBS-Conversation-building-block.md Outdated
Comment thread 20240618-RCBS-Conversation-building-block.md Outdated
Comment thread 20240618-RCBS-Conversation-building-block.md Outdated
Comment thread 20240618-RCBS-Conversation-building-block.md Outdated
Signed-off-by: Loong <[email protected]>
@daixiang0

Copy link
Copy Markdown
Member Author

@artursouza has moved those into metadata and update the HTTP example.

@artursouza

Copy link
Copy Markdown
Contributor

I changed the proposal to move the metadata to component. I also added conversationContext to allow tracking of the chat and recover a session.

@daixiang0

Copy link
Copy Markdown
Member Author

@artursouza thank you very much!

@daixiang0

Copy link
Copy Markdown
Member Author

+1 binding

1 similar comment
@artursouza

Copy link
Copy Markdown
Contributor

+1 binding

@yaron2
yaron2 merged commit 8257391 into dapr:main Aug 29, 2024
@mikeee mikeee mentioned this pull request Aug 29, 2024
38 tasks
@daixiang0
daixiang0 deleted the conversation branch August 30, 2024 05:17
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.

5 participants