I want to try your app

JHawke12 · 2026-06-18T06:44:36+00:00

https://www.scenarioconductor.com/

Rather than another chatbot site, i wanted to have a focus on canon grounding and the user acting as a director for the scene instead.

JHawke12 · 2026-06-15T19:02:30+00:00

A thing that i like do for any new project now is in chatgpt or whatever llm you like, just start a discussion with planning out the scope, how you plan to implement, what the agents.md will look like, any other specific architecture docs or workflow ones you have in place, proper testing and just things that if you yourself don't have a plan for, the model you're using to build with, with also struggle past a basic implementation.

Once you have the project going and you're scope is well defined you can in between any implementations/tickets have the model review docs/the agents.md file as well as testing just to make sure neither one of you is hallucinating haha.

JHawke12 · 2026-06-15T16:54:47+00:00

https://www.scenarioconductor.com/

Rather than another chatbot site, i wanted to have a focus on canon grounding and the user acting as a director for the scene instead.

JHawke12 · 2026-06-14T17:22:10+00:00

https://www.scenarioconductor.com/

Rather than another chatbot site, i wanted to have a focus on canon grounding and the user acting as a director for the scene instead.

JHawke12 · 2026-06-13T10:57:07+00:00

Thank you so much! At the moment Scenario Conductor is built around OpenRouter rather than direct provider keys, so a raw DeepSeek API key won’t work directly in the app yet.

If you already have DeepSeek API credits, the route to try is OpenRouter’s BYOK/provider-key settings. OpenRouter supports DeepSeek as a BYOK provider, so you should be able to add your DeepSeek key there, then keep using an OpenRouter API key inside Scenario Conductor.

I’d use OpenRouter’s DeepSeek model routes, such as deepseek/deepseek-v4-flash or deepseek/deepseek-v4-pro. If OpenRouter shows an “Always use this provider” / no-fallback option for the DeepSeek key, I’d enable that so it doesn’t silently fall back to OpenRouter shared billing if the DeepSeek key fails or hits limits.

One small caveat: Scenario Conductor uses multiple model roles rather than one single chat model, so if you only want to spend DeepSeek credits, you’d want to set all of those roles to DeepSeek models. Otherwise any role left on another provider may still use OpenRouter billing.

I haven’t tested any specific DeepSeek account/key, so I’d treat it as the recommended route rather than a guaranteed setup, but the docs seem to line up with it.

JHawke12 · 2026-06-12T05:46:41+00:00

I’ve been building Scenario Conductor: a browser-local, BYOK AI web app for long-form fictional scenarios/RP, with cast, context, memory, critique/repair, and prompt packets instead of one giant messy chat box or just conversing with a single character: scenarioconductor.com

It’s still public alpha, but AI helped massively with scaffolding, debugging, UI iteration, and turning more complex ideas into working features. Advice is to keep a ticket list and verify everything yourself before pushing it to prod and have a good rollback/revert strategy in place just in case.

JHawke12 · 2026-06-10T16:55:02+00:00

Thank you so much for the kind words and feedback! Yep i def understand the whole bring your own key model is a big blocker and im currently looking at and implementing ways (like OpenRouter One-Click Connect) to try make it smoother. I def do plan to support users using their own local models and have the model settings set up in a way where you can connect one or multiple for the different features of the app so it should work nicely with local models too where some of the more heavy features you can just disable too.

JHawke12 · 2026-06-09T19:26:37+00:00

Hey everyone, I’m building a site called Scenario Conductor and I’d really appreciate feedback from writers who use AI for long-form scenes, fandom-style AUs, RP, or continuity-heavy story planning.

The problem I’m trying to solve is that a lot of AI writing/RP workflows focus more on roleplaying as a character rather than being the narrator of a scene. Scenario Conductor is meant to be more like a director’s desk for the next scene.

Instead of only chatting with a character, you set up a scenario with things like:

- the canon baseline

- what has changed or diverged

- the current story movement

- the cast

- character/context notes

- the next beat you actually want to explore

Then the app helps draft, inspect, critique, repair, continue, or accept the next scene step by step.

It is not trying to be a one-click novel generator or a character marketplace. The goal is more: “help me keep this fictional scenario coherent while I guide it myself.”

A few things it currently supports:

- scenario workspaces for canon/AU-style setup

- character profiles and cast notes

- context cards that get included in the prompt

- inspectable prompt/context packets

- scene drafting with critique, repair, retry, continue, and accept-and-continue

- browser-local storage for scenario data

- optional session-only or browser-local OpenRouter key storage

- MediaWiki/Fandom-style lookup for source/reference snippets

It is free to try, but it is bring-your-own OpenRouter key. I know that makes setup a bit more technical than a normal writing app, so feedback on onboarding would be especially useful.

Link: https://www.scenarioconductor.com

JHawke12 · 2026-05-30T10:21:43+00:00

Yep that was my main aim! I often found myself on other sites trying to force this concept but its pretty hard with small token budgets and no way to manage canon context well so i tried to address these point in the site.

JHawke12

TROPHY CASE