on deck

random features

• new data model

  • multiple response toggling
  • branching tree chats / multiple chat trees?
  • multiple chat like v0 - either columnar (v0) or with some kind of context flipping <-- --> kind of thing
    • can generate multiple paths; each branch can be named automatically with the auto-namer
    • creates mutliple chat grids
  • multiple text +/- text area section??
    • multiple system prompts?
    • notes section? (for copy/paste for example)

• design

  • position send area relative to bottom and float on top of everything; make the text output naturally flow with the document instead of a scroll area right now
  • notes area is nice in side bar
  • template for repeat phrasing (like the buttons/user prompts initially in chat gpt; but you can program them to push a button and it'll show at the bottom to click, like a quick way to enter stuff repeatedly)

medium features

• context preservation

  • summarizer: summarizes key things succinctly into system prompt
  • trailing: feed summarizer and k-latest prompts

• nicer upload area

  • add image upload
  • add file upload?
  • voice?
  • use the much nicer invoice one
  • add whisper transcription (from another val)

• self-writing summary/notes system

  • has own system prompt, model selector, etc

• long-term memory / offload memory?

  • durable object or valtown based link sharing?

• mcp support?

• support for "re-search" tool from before?

• different interfaces

  • text notes
  • jan-like "assistants"
    • templates w/ preset prompts, settings, and variable input forms you type in, for future generations, like parameters
  • spin-off / sub-bot / picture in picture; eg spin another one up as a temp to ask some questions; an untracked one?

big features

• multiplayer chats? i guess id-based consistent, resumable session chats
• copy the shit out of heynote design for "multiple-area" design on same page
• system settings
  • text size slider (four options)
  • system color
  • font choices

director system / [ cognitive load manager ]

• breaks down into "chapters"
• some kind of "controller / director" that overwatches conversations
  • can generate spec sheets (like a dm's world sheet) eg random encounters / monsters that makes things more interesting (like a real role play)
  • can add some randomness
  • can be given random tools like dice throws (like a dm system) to add some variety

rpg game concepts

• chaptered games w/ a baseline world
• day/night/cyclical games ([day: go hunt/forage/trade; night: rest, build], [day: rebuild; night: fend off zombies/attackes])
  • can do a game around trading / building / space travel, but you talk/trade w/ people

done

• [nah: lets do left side only for now] chat tabs across the top, like chrome or rest fox?!?!?!?!
• system message should NOT be auto generatlized across all; should be specific to chat
• copy entire page / thread / export entire thread data
• custom endpoints / switch out llm url, including localhost
• show model + preset name by response?
• [nah idk; seems to work] did custom endpoints get borked?
• switch to jobs mode: background running + tabs / multiple running instances
• switch out settings button with a Dropdown preset switcher and a settings button side by side for faster switching
• cmd shift up/down to switch previews quickly
• show the preset name and the model name for each chat (or custom if custom)
• dark mode + multiple mode support (scoped scss?)
• decouple system settings with each chat with templates; system template managements
• export / import presets
• chat settings should be tied to each chat; including linked presets (preset ids)
• sidebar desktop duplicated after refactor
• cmd option r for rerun lmao
• updated head title for chat titles
• duplicate button in left bar
• cmd-r for re-running latest ai chat
• preset settings
• each chat has its own settings
• also put a rerun on the output message so that output message is replaced (keep both buttons)
• move settings to a right slide bar
• system prompt templates
  • crud system
• alpine component refactor
• save / load / import to restore all data
• /new to go straight to new
• chats have ids / slugs, so you can do /?id=whatever-chat-id
• key mappings
  • cmd-option n for new
  • cmd/ctrl-b to toggle side bar
  • cmd/ctrl-shift-b for the settings area
• branching / forking into another chat instance
• edit button instead of double click to edit
  • editing the user thing changes the width; can it somehow edit in place without changing the width / flow?
• refactor research app
• make left settings folder/new/hide into icons
  • fix the hidden icon bug
• create a new chat in sidebar
• folders in sidebar
• resizable sidebar
• delete below
• delete individual messages
• re-run a user prompt / re-run an ai response
• [~] [nah] save/discard for editing, like lmstudio?
• "delete below" should delete anything below, but not the current message

other notes

• system prompts as modes / mods to messages; eg if a character role play, to try to be nice, or angry; eg personalities to switch on/off

• templated system prompt that’s modular like lmstudio notes

  • can show/hide them for fast switching

• tool calling

  • ability to call other systems

• each bundle of settings is an “agent” for convenience; can be separated from the ui and swapped out, like lmstudio kind of, but have a small mgmt system like chat management

• dynamic systems prompt, eg a system prompt for a system that summarizes the world knowledge, or notes, or logs all actions; these can all be several tools that automatically run and append to a system prompt

• simple data system vs immerjs time travel system (have this example elsewhere)

• reusable non system prompts

  • fill in the blank (like anthropic ui)
  • or just straight up text you can @notes any time
  • (eg messages you want to use to prime actions / stories; could be reusable messages or tag existing message logs
  • maybe each message log can get a uuid taggable, or even slug

• you have chats (intentional interactions) and runs (like temporal, can be non user runs); should be able to manage all of that

• email interface to manage all of of runs and chats

• maybe interface for automations in general like coverflow

• folders can have default modes/settings for chats started in them

• “cards” system from silly tavern

• professional role play situations (borrowing from silly tavern)

• bots: reusable settings/combos; can call others to create a more complex workflow

• json schema support for constrained responses?!

  • eg status, items, key settings and metadata, health/damage
  • for ui generation or card data gen

• *** look at anthropic reference mcp server for memory

Jan.ai “assistant” bot