Workspace
On first launch, choose where NoruCore should keep settings, Books, models, caches, updates and legal acceptance.
Current Preview guide · Updated July 2026
NoruCore is a local-first role-playing application. You create a Book, describe its Room and Persona, then talk to a character whose Brain evaluates actions, goals, inventory, relationships and known world state before a local language model writes the final response.
Start here
Choose a NoruCore workspace and review the local-use agreement.
It selects packages for the detected operating system and architecture, downloads missing files and opens NoruCore.
Open Settings from Home, choose a detected model or select a folder containing .gguf files.
Add a Room description, structured objects and the Persona values you care about.
Talk naturally, request actions, inspect different chat sessions or return to Book configuration at any time.
Installation and launch
AppStarter is the entry point to NoruCore and an integral part of the application. Every launch starts there: it prepares the workspace, verifies the installed files, applies available updates and then opens the main NoruCore interface.
On first launch, choose where NoruCore should keep settings, Books, models, caches, updates and legal acceptance.
The current agreement and local privacy notice must be accepted before update checks or launch. A changed document may require a new acceptance.
AppStarter checks the manifest, downloads missing packages over HTTPS, verifies them and installs replacements with a backup.
AppStarter selects the correct Linux or Windows packages for the detected operating system and CPU architecture.
Your library
Home shows every saved Book in the active workspace. A Book contains one configured scenario, its Room, Persona and independent chat sessions.
Book names must be unique inside the workspace. Returning from Book configuration saves the current Book before Home is reopened.
Application preferences
Open Settings from Home. Changes are stored in the shared workspace and remain available when NoruCore is launched again through AppStarter.
| Control | What it does |
|---|---|
| Models | Lists local .gguf files recursively. Select a model or choose another models folder. |
| Show welcome screen | Choose whether AppStarter shows the optional Preview notice. |
| Font size | Resize interface text from 80% up to 140%. |
| Reduce motion | Reduces non-essential interface animation. |
| High contrast | Applies a stronger contrast palette and clearer keyboard focus. |
| Readable spacing | Increases semantic spacing and text rhythm across supported screens. |
| Privacy & Policy | Opens the current local agreement and privacy text. |
Scenario authoring
A Book is the boundary around a scenario. The top navigation switches between Room, Persona and Training. The adjacent button opens Extra in Room or Persona, and becomes the Training objective selector in Training.
Use Back when you finish. NoruCore validates the Book name, rebuilds the Room grounding registry and saves the Book before returning Home.
What exists in the scene
The Room combines a free description with structured object cards. The description gives atmosphere and broad context; cards give the Brain dependable information about what an object can do.
| Type | Examples of supported meaning |
|---|---|
| Generic object | Carry, place, support and examine. |
| Container | Open, close, contain, place inside and carry. |
| Door / Passage | Open, close and pass through. |
| Bed / Layable surface | Lie down, sit and rest. |
| Chair / Sittable surface | Sit, support and examine. |
| Table / Support surface | Place items on a surface. |
| Tool | Use, hold, carry and wield. |
| Device | Use, activate and deactivate. |
| Fragile container | Contain, carry, pour and break. |
| Food | Cut, mix, carry and place inside. |
When off, the object remains known and visible but the Brain rejects actions that require reaching or using it.
When off, the object is fixed. When on, the planner may consider movement actions such as push, pull, drag, lift or carry when its other capabilities allow them.
Object cards can be dragged into the Room description. Dropping one inserts a stable
token such as {{wooden chair}}, keeping the text connected to the authored object.
Who the character is
Set name, gender and age. Gender and age include presets, with the option to change the value manually.
Choose Short (~80 tokens), Medium (~180) or Verbose (~350) as the normal response budget.
Add topics the character cares about. Right-click an entry to remove it.
Add explicit character boundaries. Right-click an entry to remove it.
Decision influences
These controls influence Brain decisions. Use fewer, deliberate values when you want a character that is easier to understand and tune.
Repeatable behavior
Select Add to create a Habit card, then click the card to configure one action and one known target. Available actions come from the Persona's real action catalog; targets are limited to known people, the person interacting with the character, Room objects and inventory items that fit the selected action.
| Setting | Available behavior |
|---|---|
| Strength | Optional, Preferred or Strong. |
| Trigger | Exact time, Time window, Interval, World transition, Fact became true, Before goal, After goal or Manual test. |
| Recurrence | Once, Every occurrence, Daily, Specific days, or a number of times per day, week or month. |
| Missed occurrence | Skipped rather than automatically recovered. |
Time fields use the 24-hour HH:MM format: for example, enter
07:30 for half past seven in the morning or 19:45 for quarter to eight in the evening.
Intervals accept minutes, hours or days, and specific days can be selected individually. Right-click a Habit
card to delete it.
Goals with conditions
A Quest stores one or more structured objectives. Select an action and a compatible known target, then press Add objective to keep that pair and prepare another objective.
Prerequisite options are drawn from known Book data. Internal runtime identifiers are translated into readable labels in the menu. Click a prerequisite's value and choose Delete to remove it; right-click the Quest card to delete the whole Quest.
Carried and worn items
The character contains seven fixed cards: Head, Body, Legs, Feet, Hands, Accessory and Equipment. Click a card to edit one slot.
Book presentation
Extra controls the background and sound associated with the current Book. It uses only assets included with NoruCore; it does not import arbitrary media.
Enable or disable the background, browse the included images with the arrows and click an image to select it.
Enable music, click a player card to select a track, or use its play button to preview and stop it.
Enable typing feedback and select one of the included keyboard sounds.
Guided correction
Press and hold Persona to open its context menu, then select Training. The former Extra button becomes a selector for five focused modes. When you change mode, the visible Training conversation is cleared from the interface so the next session has one explicit objective. Corrections already applied to the character remain saved in their dedicated profiles.
The experimental Actions mode shows the action interpreted by the Brain, why it was considered and its real alternatives. Select Custom to correct Understanding, Decision or both through two closed menus with four fixed choices each. The corrections are saved separately in the Persona.
Actions uses the active Room, accepts unique partial object names such as
sofa for Purple Sofa, and follows the available GOAP action catalog. Its sandbox never
executes the action or changes the world. For now, its corrections are recorded and restored with the Persona,
but are not yet used by the Brain when making later decisions.
Role-playing runtime
Chat combines the configured and trained Persona, current Room, grounded objects, inventory, Habits, Quests, relationship and learned state. The Analyzer prepares your message for the Brain, which decides how the character should behave based on the configuration and Training you have applied. The selected local model then writes the final response around that decision.
After one successful action, send a separate English reaction such as Great!,
Awesome!, Bad! or Yuck! to make that action more or less preferred in similar
future decisions. In this experimental version, the Brain recognizes only a fixed built-in vocabulary: these
phrases cannot be added, removed or edited from the application. Matching ignores capitalization and
punctuation, but the reaction must correspond to one of the supported phrases and cannot contain a new
instruction. Each learned preference remains linked to its feedback message; deleting that message removes
only the associated learning and preserves feedback from other messages.
Continuity without an endless prompt
NoruCore stores structured character and gameplay information separately from the raw model prompt. This allows important learned facts, relationship state, inventory and Book configuration to persist without sending the entire history on every turn.
The prompt budget reserves output space and progressively compacts older conversation when necessary. If the configured model still cannot fit the required context, NoruCore blocks the request and asks you to start a new Chat or continue with less recent context.
Training conversations are temporary working sessions and are not added to normal Chat history. NoruCore saves only the changes you explicitly confirm: Voice, Delivery and Formatting update their dedicated communication settings, while Behavior corrections update the character's six core Traits. The complete Training conversation is cleared when its session is reset.
Honest Preview boundaries
Common setup problems
Select Choose models folder… and choose the folder that contains your model files. NoruCore scans nested folders for .gguf.
Return Home, open Settings and select a valid local model. Wait for its loading indicator to finish before sending another request.
Check that the target exists in Room or inventory, has the right functional type and is Interactable. Movement also requires Movable where appropriate.
The language model writes dialogue, but only the Brain can commit an action. Treat the visible Room, inventory, Quest and relationship state as authoritative. Retry with one short action, an explicit target name and a supported verb.
Write the request in English, name the target directly and avoid combining several dependent actions in one sentence. Ambiguous or unsupported wording is kept conversational so it cannot change state by mistake.
Like confirms the tested decision but does not change Traits. To correct future behavior, select Dislike, adjust the Behavior controls and choose Apply & Retry. The correction is then saved to the character's six core Traits.
Start a new Chat or reset the current Training session. NoruCore reserves space for the answer and stops the request when the selected model cannot safely fit the required context.
Add the relevant Room object or inventory item first. Target menus deliberately show only information known to the character and compatible with the selected action.
Use Font size, High contrast, Readable spacing and Reduce motion in Settings. NoruCore applies them across supported screens and remembers the selection.