Three things shipped this week — and together they change how you bring your own content into a project, how you talk to the agent, and how you investigate builds when something goes wrong.
Drop in your assets
Until recently, using your own images in a Primio app meant hosting them somewhere — an S3 bucket, Firebase Storage, a CDN — and feeding the agent a download URL.
That’s gone. Now you just drop them in.
Drag files straight onto the chat, or use the attachment button. Up to 10 files per message, and they work in two ways.
As context — images, PDFs, and text files the agent reads to understand what to build. Drop in a PDF spec, for example, and it becomes the blueprint.
As project assets — files embedded directly into your app:
- Photos & images — portraits, backgrounds, icons, UI mockups
- Fonts — your brand typeface, applied across the whole app
- Audio — sound effects, background music, button taps
- Video — onboarding backgrounds, demo loops
- Config & data files — JSON, YAML, Markdown, wired directly into the UI
Images work both ways — attach a mockup as a design reference and it gets stored in your project at the same time.
Learn more in the Attaching Context docs.
Discuss mode
Not every message should generate code. The chat input now has two modes: edit and discuss.
Edit is the default — send a message, Primio writes code. Discuss lets you ask questions or think through an approach without touching your project. Switch back to Edit when you’re ready to build.
The edit / discuss button sits at the bottom-right of the chat input. See the Chat Interface docs for details.
Clear Context
That same toggle has one more control: Clear Context. When armed, it resets the agent’s conversation context before your next message — your code and files are untouched, only the agent’s working memory clears.
Use it when you’re switching to an unrelated task, or when the agent has drifted and keeps repeating a mistake. The toggle fires once and resets automatically after send. Read more in the Clear Context docs.
Debug and Release builds
Every build now runs in Release or Debug mode, switchable per platform — including the web preview.
Release is the default: optimized, fast, and app store ready. Debug turns on verbose runtime error output, making it easier to catch crashes and UI issues that only surface at runtime.
The web preview runs in Debug by default so errors appear immediately during development. Switch it to Release if you need better performance — but keep in mind that error visibility will be reduced.
When a runtime error occurs, Primio captures it and shows an Analyze button. Clicking it decodes the raw error into readable source locations. A Try to fix button then lets the agent inspect the error and attempt a fix automatically.
Set build mode in Workspace → Build Mode. Web, Android, and iOS are configured independently. Switch back to Release before any store submission. Full details in the Build Modes docs.