Introducing Opal, our new way to help you build and share AI mini-apps by linking together prompts, models, and tools— all while using simple, natural language (without a single line of code 🤯)
Now available in US-only public beta! Learn more ⬇️
🧵(1/7) We have been absolutely obsessed with your Flow creations— keep them coming! To help spark some inspo and ensure you're getting the most out of Flow and Veo, here's a quick refresher on all of the features. ⬇️
⚠️ Pro tip: bookmark this thread for easy referencing!
🧵(2/7) You can create Ingredients (characters, objects, locations, styles, etc) which become your film’s building blocks. Then, use your ingredients to tell a consistent story across clips. You can even try adding multiple ingredients, then generating a clip that combines them!
🧵(3/7) You can also add Frames - uploaded or AI-generated images - to define your clip’s start and end points.
Use Frames to Video and add a first and last frame with a brief visual prompt and Flow will generate a smooth, cinematic transition that connects the dots seamlessly.
When we were building @julesagent we wanted to make sure we were solving *real problems* for developers. So, that meant building more than just a code writing assistant, but an AI agent who can help support your entire codebase. Here's how we do that in Jules: 🧵 🧵 🧵
@julesagent 1️⃣ We built Jules as an async agent outside of the IDE because we saw the opportunity of an AI agent that can work alongside you. So, in Jules, you and the AI agent can work in parallel in the same codebase but on different tasks.
@julesagent 2️⃣ After that decision, we had a lot of debates over what features to build. Ex: if Jules is an async product, then why have an interactive chat? Ultimately, we decided that we needed to build trust with our users (through a sync experience) before we could fully go async.