-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
AI kit can only be used with the <AIConversation> component #8125
Comments
You're absolutely right, thanks for the feedback. This work in progress PR should cover what you're looking for. We expect to get it onto the docs site shortly. Specifically, this section addresses how to include images.
Conversation routes don't support sending documents. If that's something you'd like to see, please open a feature request in the https://github.com/aws-amplify/amplify-category-api repository. Thanks! |
If you are using React, you can also use the hooks by themselves and build your own UI. We can probably make that clearer in the docs. import { generateClient } from "aws-amplify/api";
import { Schema } from "../amplify/data/resource";
import { createAIHooks } from "@aws-amplify/ui-react-ai";
const client = generateClient<Schema>({ authMode: "userPool" });
const { useAIConversation, useAIGeneration } = createAIHooks(client);
export default function App() {
const [
{
data: { messages },
isLoading,
},
handleSendMessage,
] = useAIConversation('chat');
// render your own UI here with message, isLoading, and handleSendMessage
} |
Thanks this is helpful. I see that PDF is indeed not supported yet with Bedrock but coming soon: Supported platforms and models I will already make a request. |
Describe the content issue:
I miss clear examples / pages how to use the AI kit in my own UI instead of using only.
I have solved it partially, but face errors when attaching attachments like images of pdf's.
URL page where content issue is:
https://docs.amplify.aws/nextjs/ai/concepts/streaming/
@atierian are you able to share the docs here already?
The text was updated successfully, but these errors were encountered: