Studio notes.

A useful AI conversation can move a project forward: a direction becomes clear, a problem gets solved, and the next step takes shape. Coming back later should not mean piecing it all together again.

PromptStudio 0.16.0 introduces Project Log and Waypoints, giving each workspace a place to keep that useful context and bring it into the next prompt.

A project log beside your prompt builder

Open a workspace and you will find a new Project log tab next to Prompt builder. Keep a dated record of the things that matter:

• Decisions: what you agreed and why.
• Bugs / problems: what needs attention and whether it has been resolved.
• Open questions: what is still uncertain.
• Next actions: what to work on next.
• Waypoints: useful summaries of where the project stands.

Add tags, search your entries, or filter by type, status, source and date. Open items brings unresolved problems, questions and actions together when you need to see what is still outstanding.

Save a waypoint before you leave

A waypoint captures the useful state of a project at a particular moment. Give it a title and paste in a summary from your AI conversation, or write one yourself.

The Add waypoint form includes a copyable helper prompt. Use it in the AI conversation you already have, then bring the summary back to PromptStudio. You can record its source, adjust the date and add tags to make it easier to find later.

The original summary stays as you saved it. If something needs correcting, add a separate correction note. When the project moves forward, a new waypoint can supersede an earlier one while keeping the earlier record available.

Bring the right context into your next prompt

In the builder, choose Project log from the Context source menu. Preview an entry, add it to the canvas or drag it into position. You can also select several entries from the log and add them together.

You choose what goes into the prompt. Each added entry becomes its own saved copy, so later changes to the log do not silently rewrite a prompt you have already assembled. Reorder, edit or remove those canvas copies as the next task requires, then copy the finished prompt into your AI tool.

Keep the history you need

Accidentally deleted an entry? It goes to Trash and can be restored within your chosen retention period. When duplicating a workspace, the new Include project log option lets you carry its history forward or start with an empty log.

To try it, open a workspace, choose Project log and click Add waypoint. Save a short summary of where your project stands today. Your next session will have somewhere useful to begin.

PromptStudio has changed shape. The earlier version was built around structured prompts and XML. That idea is still in the background, but the project is becoming something more useful: a private workspace for the context that makes recurring AI work feel consistent.

Creative direction, project rules, reference notes, reusable personas, tone, constraints, and the brief for today’s task can all live in one place instead of being rebuilt from old chats.

The visible pages have changed to match that. Workspaces, blocks, the working brief, and reusable packs are now the centre of the product. The goal is not to make people learn prompt engineering. It is to make it easier to keep the information that matters, choose what is relevant, and use it where it helps.

Why we moved to WordPress

There is vibe coding, and then there is building something people may trust with their own private material.

A quick standalone app can look convincing very quickly. The difficult parts arrive later: accounts, passwords, data access, permissions, database backups, user isolation, password resets, updates, support, and what happens when somebody finds a hole you did not expect.

WordPress is not being used here as a page builder or as a generic admin dashboard. It is the foundation underneath a custom PromptStudio application. It already has a mature account system, well-understood permission controls, a database, administration tools, a large maintenance ecosystem, and years of hard lessons built into it.

That does not make security automatic. No platform can do that. It does mean PromptStudio does not need to invent its own account and access-control system from scratch while pretending it is production ready. The user-facing experience remains a custom app. WordPress handles the durable machinery below it.

For a product that may eventually hold people’s project context, preferences, creative work, and reusable instructions, that is the more responsible place to start.

What is new

The current build is becoming more practical day by day:

• Reusable workspaces for different projects and creative worlds.
• Editable context blocks rather than one enormous master prompt.
• Working briefs assembled from the blocks relevant to a specific task.
• Importable packs, including specialist personas and presets.
• A private feedback and bug-report route from the user dashboard to the site administrator.
• In-app replies, notices, and update messages, so changes do not disappear into a changelog nobody sees.

The feedback route matters. Early users should be able to say what is confusing, what is broken, and what they wish the product did without needing to find an email address or leave the product. In return, PromptStudio can show when an issue has been seen, fixed, or needs more information.

PromptStudio is still being shaped in public view, but the direction is clearer now: less prompt theatre, more useful context; less fragile cleverness, more dependable foundations.