INTRODUCING: Hoplight + Kit | A Frontend for Creators and Hoarders + A CLI for AIRP Creation. (IT'S NOT ANOTHER FRONTEND SLOPFEST I SWEAR JUST READ THE DAMN POST)
LADIES AND GENTLEMEN, SHE'S, HE'S, THEY'S AND FREAKS! INTRODUCING MY NEWEST PROJECT:
Hoplight and Kit
https://github.com/Coneja-Chibi/Hoplight
----
From the maker of TunnelVision, BunnyMo, VectHare and RoleCall.
Every platform has different formats, even the local ones. And every time you move between them, another copy is born.
One version in SillyTavern. Another in Risu. A lorebook stuck inside an old PNG. Three versions of the same character, all slightly different, and no clear answer about which one is the real one.
Hoplight starts with a different premise:
Your work should belong to you, not to whichever platform you want to use that week.
🎭 THE HOUSE LIGHTS ARE UP!
Hoplight is a local-first creative studio for AI roleplay content.
Characters, lorebooks, personas, presets, regex sets, and sprite packs live together in one studio folder as plain files. Hoplight reads the formats other platforms expect, gives you one place to edit them, and publishes them back out when you choose.
Your studio remains the source of truth.
| The usual way | The Hoplight way |
|---|---|
| One copy per platform | One master piece with multiple publish targets |
| Platform-specific editors | One editor with platform-aware lenses |
| Guess what survives conversion | See compatibility and losses before publishing |
| Embedded lorebooks stay buried inside cards | Lorebooks become real, linked, editable pieces |
| Your library lives inside somebody else's app | Your library is a folder on your own disk |
This is not a cloud library, a new card host, or another format trying to replace all the others.
🎪 ONE BUILDING, DIFFERENT ROOMS
Hoplight is arranged like a working studio because I'm neurodivergent and it made my brain itch right when I built it this way.
The Library is where everything comes in and where you find it again. Characters, lorebooks, personas, presets, regex sets, and packs each have their own deck.
The Workbench is where pieces are edited. Choose a platform lens and see that platforms specific editables. Write for Risu, switch to SillyTavern, then return to Hoplight's full view without maintaining three separate cards.
The Binder gives lorebooks a real home. Entries, keys, trigger modes, placement, activation, ordering, categories, and token budgets live in one focused book editor.
The Press is where finished work leaves the studio. Stage your pieces, choose a target, inspect what is ready, and receive an honest result for every item in the run.
The CSS Workshop This one was mild headache for me; I know different online platforms just... Hand you a pocket full of CSS and expect you to get something good out of that. So I tried to make a tool that makes that a little easier.
🐇 MEET KIT: I MADE THIS BITCH A CLI TOO!
Hoplight now has a second face.
The Studio is visual. Kit lives in the terminal.
Kit is a conversational shell connected to the same engine and the same studio folder. It is not screen-scraping the Web UI or pretending to click buttons. It works with Hoplight's actual content model through typed tools that you can connect your agent of choice to.
You can ask:
- "How many characters do I have?"
- "Show me Mira's alternate greetings."
- "Rename this lorebook."
- "Reorder these entries."
- "Add a hidden secret to this character."
- "Update this preset's sampler settings."
- "What does Hoplight support for Risu?"
- "Read the documentation around lorebook trigger placement."
HOW I HANDLE TOOLCALLING (FOR THOSE WHO CARE)
Giving a model more than one hundred tools at once is not power. It is a very expensive way to make the model confused. (And me, Angry!)
| One giant tool list | Kit's approach |
|---|---|
| Every schema rides in every prompt | Most operations stay collapsed |
| Similar tools fight for attention | Kit searches by intent and content type |
| The model guesses arguments | One selected operation reveals one strict schema |
| Every new tool makes every request heavier | New operations join the same catalogue automatically |
Kit currently has two dozen typed content operations across characters, lorebooks, personas, presets, regex sets, and media packs.
The catalogue can grow without turning every conversation into an API reference manual.
🎬 WHAT HAPPENS WHEN KIT CHANGES SOMETHING?
Kit does not jump directly from "I understand" to "your file has been rewritten."
A real edit moves through a visible lifecycle:
- Kit reads the current piece.
- It finds the operation designed for that kind of content.
- It prepares a draft with every proposed change, warning, and platform impact.
- The complete draft can be shown and validated without writing anything.
- Applying it crosses Hoplight's authorization Gate.
- Hoplight saves once, reads the piece back, and verifies the result.
If the piece changed underneath Kit, nothing is overwritten.
If verification fails, Kit does not call the job complete.
If you discard the draft, the original piece remains untouched.
LONG CARDS DO NOT FALL OFF A CLIFF
Cards, lorebooks, documentation, and change drafts can become much larger than one sensible model response.
Kit does not solve that by chopping the answer after a few thousand characters and hoping the missing part was unimportant.
Large results can be paged, searched, and continued through temporary result handles. Kit can also outline a piece and read one specific field instead of dragging the entire card into every request.
The model gets continuation instead of runaway context.
📚 KIT CAN READ!
Kit can query Hoplight's own documentation when it needs to understand a format, feature, editor, or engine rule.
It can:
- Browse documentation collections
- Open a collapsed page outline
- Search across page content and section summaries
- Read one relevant section
- Continue through the entire original document when context matters
This does not need a vector database, an embedding server, or another background service. Hoplight keeps a page-and-section index designed for traversal, while the full documentation remains the authority. (SOUND FAMILIAR BITCHES? >:D)
So if Kit is unsure how Hoplight handles something, it can go read how Hoplight actually works.
RAPID FIRE: What else is in here?
- One local studio for characters, lorebooks, personas, presets, regex sets, and packs
- Platform lenses that show how each target reads the same piece
- Linked content so characters and lorebooks can travel together
- Plain local storage you can back up, inspect, version, or move
- Import receipts that tell you what Hoplight actually found
- A staged Press with per-item export results
- Progressive Kit tools that appear only when they are relevant
- Complete change drafts you can inspect before saving
- Responsive terminal artwork with a real composer, Backstage activity, and slash-command menu
- BYOK model connections through Kit's
/modelflow - Open source under AGPL-3.0
🎟️ THE PLAYBILL: TL;DR
If you skipped to the bottom:
- Hoplight is a local creative studio for AI roleplay content.
- Your studio copy is the master; platforms are publish targets.
- Characters, lorebooks, personas, presets, regex sets, and packs share one engine.
- The Library brings work in, the Workbench edits it, the Binder handles lore, and the Press ships it out.
- Kit is Hoplight's conversational terminal shell.
- Kit discovers specialized tools progressively instead of loading everything into every prompt.
- Edits are drafted, inspected, authorized, saved, and verified.
- Kit can navigate long results and read Hoplight's documentation.
- Your studio stays on your own machine.
OPEN THE STUDIO
Hoplight (and Kit) are in active development.
Repository and releases:
github.com/Coneja-Chibi/Hoplight
The Studio works without an AI provider.
Kit needs a provider when you want it to reason or edit. Open /model, connect one, run /test, and then talk to your studio.
Kit's typed editing loop is built and connected. Conversational create, import, export, and deeper diagnostic workflows are the next major tool families being added.
The foundation is here: one catalogue, bounded context, inspectable drafts, explicit authorization, verified writes, and no arbitrary filesystem access.
I intend to keep adding to these two projects for months and months and months; because I just have SO many ideas. One love peepo! Feel free to contribute, File issues, bug reports, develop your own apps for it! I made this hyper modular so you can add/pick apart, and extend this however you want.
---
Where can you find me?
- AI Presets Channels (Only in my own chats, I don't really speak in the general spaces)
- RoleCall (Are you interested in my Frontend for AIRP? It's cloudbased so don't hatecrime me!~ But it's really good, can confirm. So much customization. Too much, some people say.)
- My Professional Portfolio (Interested in hiring me, or just knowing about the shit I make in a more professional sense?)
- My Personal Discord (These people hear about my projects, presets and more before anyone else!)
- My AIRP Works (Presets and Cards)
- My GitHub (Self Explanatory)
---
Back to work I go! (Pls try it I worked really hard on it and it'd mean a bunch to me. I'm literally a slave to the people i love making stuff for y'all so if it can't do something you want it to; just let me know!)
Posted Jul 25, 2026, 11:32 PM UTC