Krea Agent Now Turns Plain-Language Prompts Into Custom Creative Apps
Krea just rolled out custom apps inside its creative agent, letting users spin up bespoke image and video tools with a single prompt.
- Krea launched custom apps in Krea Agent, letting users build creative tools by describing them in plain English.
- Demo apps include a grid-based image animator, a video motion-echo effect, and a kinetic typography generator.
- Each app exposes real controls like rotation, scale, and effect type instead of forcing repeated prompting.
- Sits alongside Krea Agent's existing Skills, Routines, and OAuth integrations to Slack, Figma, Notion, and more.
- Krea Agent orchestrates 60+ image and video models including Flux, Veo 3.1, Kling, Runway, and Krea 2.
- Still an invite-only beta; also reachable from Claude, Cursor, and Codex via Krea's hosted MCP server.
Krea Agent now builds custom creative apps
Krea has added custom apps to its creative agent platform. Users describe an interactive tool in plain language, and the agent generates a micro-app with controls, parameter fields, and a preview surface. The feature is available through Krea Agent, which remains in invite-only beta.
Custom apps turn recurring image, video, and typography tasks into reusable interfaces. A creator can adjust an effect through sliders and toggles instead of rewriting prompts or assembling the same workflow for every variation.
A prompt becomes a control panel
Krea uses the prompt as a specification for both the creative operation and its interface. The resulting app accepts media, exposes relevant parameters, runs the underlying generation or transformation, and displays the output for further adjustment.
Launch examples demonstrate three types of tool:
- Grid animation: Slices an image into tiles, animates each tile, and provides wave, elastic, and glitch modes with motion controls.
- Video echoes: Converts movement into floating windows and trailing copies, with controls for rotation, scale, and copy count.
- Kinetic typography: Morphs the Krea wordmark into changing letter patterns.
Krea previewed the underlying capability during its New York demo, where the agent built an 8-bit image converter as a web app inside the platform. Custom apps package that behavior as a product feature.
How the agent assembles the pieces
Krea Agent acts as a planning layer across the company’s creative suite. A language model interprets the request, selects the required tools, and coordinates the workflow, while Krea and third-party generation models produce the media. The platform reportedly supports more than 60 models, including Flux, Veo 3.1, Kling, Runway, Luma, and Krea 2.
| Component | Role |
|---|---|
| Skills | Save workflows that users can invoke again by name. |
| Routines | Schedule runs that open fresh sessions with the same context. |
| Integrations | Connect services such as Slack, Figma, Notion, Google Drive, Linear, and Airtable through OAuth. |
| Custom apps | Generate task-specific interfaces with controls and previews. |
External agents can also reach Krea through its hosted MCP server. Model Context Protocol gives clients such as Claude, Codex, OpenClaw, and Cursor a standard way to inspect tool schemas, submit image or video jobs, and poll for results.
Repeated effects are the clearest fit
Custom apps suit workflows where the operation stays consistent while a creator repeatedly changes inputs or parameters. Direct controls can shorten iteration cycles when visual judgment matters more than prompt variation.
- Character studios: Restage the same subject with different poses, lighting, or backgrounds.
- Product viewers: Rotate a render and test angles before selecting a hero image.
- Motion rigs: Tune trails, echoes, scale, and timing for batches of social clips.
- Brand animation: Refine typography and logo motion through small parameter changes.
A generated interface reduces the front-end work required for a specialized creative tool. That can make a campaign-specific control panel practical for a small team or a short production run.
Production details remain sparse
The available examples are compact visual-effect tools, and Krea has yet to publish detailed custom-app documentation. Several implementation questions will determine whether teams can rely on the feature beyond experimentation.
| Question | Current status |
|---|---|
| Who can use it? | Krea Agent remains in invite-only beta. |
| Do apps persist across sessions? | Persistence, versioning, and state storage are undocumented. |
| Can teams share or publish apps? | Sharing, permissions, and collaborative editing have not been explained. |
| Can apps be exported or embedded? | Code access, deployment, embedding, and API options remain unspecified. |
| How are complex workflows handled? | Krea has not detailed multi-model chains, intermediate review steps, or failure recovery. |
| How is usage billed? | Custom-app pricing, model charges, and execution limits have not been published. |
Creative agents gain an interface layer
Replit Agent, Claude Artifacts, and Cursor already generate small applications from natural-language requests. Krea applies that pattern to media production, using image and video models, visual previews, and effect controls as core building blocks. At its agent reveal, the company said it had spent three months adapting agents to creative workflows.
Custom apps extend Krea Agent from workflow planning into interface generation. Their production value will depend on persistence, sharing, governance, and predictable costs, while the current demos establish a focused use case: converting a repeated creative transformation into a reusable control panel.
Comments
