Get settled.
Find your flow.

1. Open Downloads and check the build label. For this guide's features, use the 82177 release page and read its package notes.
2. If moving from an older NSIS installation, explicitly install the release's Velopack Setup package first. The old installation is not automatically converted.
3. Close viewers, Character Sessions and MCP clients before installing. Use the complete bundle from one release; do not swap individual host, viewer, MCP or helper executables between builds.
4. Launch the ordinary viewer or Character Sessions. First launch offers independent Desktop and Start menu shortcuts and optional crash reporting. Not now leaves those choices for later.
5. Log in yourself. Installation, the host and an assistant do not submit your credentials for you.

These Nightly packages are unsigned. Check the repository, release and package identity before deciding whether to run a download. Cross-platform source instructions are available, but this guide does not promise downloadable Linux or macOS packages for this release.

In the viewer, open Help > Check for updates.... Select Nightly, click Apply, then Check now. The dialog offers Download, What's new, Skip version and, for supported installations, Update app. Change shortcuts through Help > Desktop and Start menu shortcuts....

In the host, open Preferences > Updates > Releases. Select Nightly and apply the choice before Check now, or enable automatic checking. Results appear after Preferences closes.

For a Velopack installation, viewer Update app... or host Prepare update... downloads first; characters can stay logged in during download. Installation then requires closing every viewer, host, MCP client and helper using that installation. Host Quit all characters retains native logout confirmations. Cancelled logout or Keep logged in blocks installation; the updater does not force a disconnect. A final confirmation precedes installation and restart. Cancelling while waiting leaves the verified download unapplied. Older NSIS installations use the release download route.

A missing result is not proof that your build is current. Nightly 82177 fixes CRLF/mixed-line-ending release-metadata parsing, and older published release bodies were also normalized. Try Check now again first. If discovery still fails, use this guide's pinned release page and matching Setup package; do not mix individual helpers. Website download labels can lag behind GitHub releases.

1. Resize the viewer window so it spans the displays you want to use.
2. Open Preferences → Move & View → Layout and enable Use a custom world viewport.
3. Select a display and click Use this monitor. If display positions are unavailable, drag the white boundaries in the diagram or adjust the reserve percentages.
4. Move Inventory, chat and maps into the space beside the world. Choose where toolbars and top bars sit.
5. Click OK to keep the arrangement. Save a named Layout, or a Workspace if you want to restore your windows too.

Changes preview immediately; Cancel restores the previous arrangement. Fit the monitor again after moving or resizing the viewer window.

Side toolbars can sit inside or outside the world viewport; Smart placement uses the outside space when it fits. Bottom and top bars can follow the viewport. Layout profiles keep that placement for later.

Keep the custom viewport in Mouselook is a separate choice. Login and the two-factor prompt also use a saved world-view slice.

The viewer’s Snapshot tool uses the world viewport by default, keeping the panel margins out of your picture. Choose Full window when you want the whole window. Assistant snapshot tools have their own options; see assistant photos.

The published build also keeps Camera, Graphics, Volume and Media hover panels reachable in custom layouts.

Use this monitor fits only the part of that display covered by the viewer window. Different display sizes or scaling may need a manual adjustment. Percentage controls work when monitor detection is unavailable.

Under Move & View → Workspaces, use Recover windows now to bring supported utility windows back into view. Recover arrangement when displays change can do this automatically; it starts off.

Recovery fits the live arrangement without rewriting your saved workspaces. If you preview recovery in Preferences, Cancel restores the prior positions.

1. Launch the Character Sessions shortcut. If it is missing, open folderstorm-session-host.exe beside the matching Windows viewer.
2. Click the Login icon to open the next available profile. Its context menu lets you choose a particular profile. Older builds call this + Character or Open login.
3. On first open, choose to copy selected settings from your main profile or keep the existing settings/defaults. Then log in normally.
4. Open another profile and log in as a different character. The first ready character becomes active; the others stay in standby.
5. Choose a ready character in the selector to switch the active world. Repeat for up to five slots.

The regular viewer shortcut still opens a regular viewer. Starting the host or opening a session set does not submit login credentials for you.

Use the viewer, host and helpers from the same release bundle. This guide describes the published 82177 host; older installers may have different menus.

Use the host’s Preferences icon, then Layout & theme → Layout → Docked controls area. Automatic uses the right half for a broad two-display span or the middle third for a broad three-display span. You can choose Full window, either half, or any third manually, which helps with unequal displays.

In that Layout tab, enable Show viewer inside host to fit the active viewer into the host, or turn it off to keep separate viewer windows while retaining account switching.

This chooses where the host controls sit. Set the world viewport separately in the viewer’s Move & View → Layout.

The control strip groups the character selector, Login, Chat, Monitors and Preferences together; quick actions sit in the center, with pop-out and expand/condense controls at the right. Hover an icon for its label. Tight spaces put additional commands in More.

Pop out Chat or character controls independently and put them on another screen. Detached panels and monitors have independent Always on top pins. Expanded mode can show character cards; Condensed keeps the controls compact. Advanced Minimal has a Show controls strip.

Host Preferences Apply saves without closing; OK saves and closes. Cancel discards edits since the last Apply. Accepted choices and quick layout changes save automatically in recent builds.

Click Chat to show or hide shared Chat. Select the account and conversation, then check Send as before sending. Switching the active world keeps the chat sender and draft where they were. Account names remain identifiable even when you use friendly labels or colors.

Start a new IM:

1. Choose the sending character in shared Chat and check Send as.
2. Choose New IM or open Friends. Filter friends or use Search names to find a resident.
3. Select the resident, checking both display name and username, then choose Open IM.
4. Compose the message, recheck the sender and recipient, then explicitly choose Send.

Opening an IM sends nothing. Offline friends can receive IMs too. The same character-bound chooser is available from monitor Chat.

Enter sends; Shift+Enter adds a line. Scroll back to read older messages; Latest resumes following new messages. Closing a conversation in the host keeps its unsent draft for this session. A new incoming message can reopen it; closing does not leave a group or end a call.

In host Preferences → Chats & notifications, choose which conversation types appear, which enter Attention, and how reading works. Mark displayed chats read starts on and applies to a visible chat at its latest messages; scrolling back or hiding it pauses that behavior. Optional active-character auto-read starts off.

The Attention quick action shows eligible conversations and offers. Click it for the inbox; right-click for navigation and filters. Next/Previous browse pending items. Review in viewer opens the right account’s native controls; Dismiss only hides the host reminder. Review, Read and Dismiss do not accept offers or permissions.

Per-character labels, colors and optional background sounds live under Character settings. You can choose a short WAV sound for different characters. Chat visibility, attention and sound choices are independent; Do Not Disturb, explicit mute and restrictions still apply.

The Monitors icon opens a list of inactive characters. Toggle a fixed monitor to open or close it. You can open four fixed monitor windows plus a separate Monitors > Cycling monitor window. Preview images are read-only and do not forward movement or clicks.

Exchange activates that monitor’s character and, after a successful switch, shows the previously active character there. Other monitors keep their assignments. Right-click its image/footer for Show chat; this lets you reply as the displayed character without activating its world.

Monitor Options adjust size and update rate. Available targets are 0.5, 1, 2 or 5 FPS. Fixed and cycling views share one aggregate 10 FPS budget; duplicate views of a character share its stream. More previews can reduce the effective rate. Hiding/minimizing a window releases its unused capture policy.

The cycling window rotates through eligible inactive characters in card order without changing the active world. Its interval defaults to ten seconds, adjustable from 2 to 3,600 seconds. Use Play/Pause or Previous/Next to control it.

Pause to chat is the default: pause the cycling window before interacting with its Chat. If you relax Advanced > Require pause to chat, entering the composer still pauses rotation before typing. Choose Play explicitly to resume. Cycling does not automatically mark changing chats read, and drafts stay with their source character and conversation.

New IM and monitor behavior reference includes detailed limits and native acceptance notes.

Warm keeps initialized rendering buffers ready. Economy experimentally releases some background render targets. Both keep session maintenance running; actual memory and performance gains depend on your computer.

Host Audio & voice offers background world/media muting and optional Voice follows active character, which starts off. Only the active character can own managed voice input when it is enabled.

Switching & monitors also offers Instant, Fade and Bird’s-eye transitions. Escape skips an animation while completing the switch; camera restrictions may use an instant fallback.

Save and close your main viewer before copying so its latest settings are on disk. The first-open prompt offers selective copying; later select a closed destination under host Preferences → Character settings → Viewer settings and click Copy settings…. Older builds expose Copy from main profile… under Characters/Settings.

Choose only the groups you want: graphics, interface, colors, bindings, quick preferences, toolbar layout, movement, camera, avatar/LookAt, RLVa or reviewed account UI settings. A toolbar-only copy works too; select the source account when asked. Replaced files get backups, and a report explains skipped entries.

Copying does not bring passwords, Inventory/chat contents, caches or live restrictions across profiles. Workspaces and boards stay separate. Custom asset references are not a general asset migration.

Use Host Preferences → Advanced → Files & recovery → Manage session sets…. Session sets save a chosen group of profiles, background policies, host arrangement and optional fixed-monitor assignments. Open a set to review it and open ordinary login windows. Update, Rename, Duplicate and Delete manage the set; deleting a set does not delete accounts. Cancel opening stops remaining follow-up launches.

Configure up to twelve quick actions and their icon/text display under Controls → Quick actions. Use Controls → Keyboard shortcuts for host shortcuts. For keys used while the native world has focus, assign the Character actions in viewer Preferences → Controls. No default viewer keys are taken; switching shortcuts pause while you type.

Each character keeps its own account-local workspaces. Use the character’s workspace controls to apply its arrangement.

If controls disappear, use Show controls, the host’s Windows system menu, or the notification-area icon for Restore controls and Recover positions. Recovery brings panels back into reach and clears their topmost pins for this session.

For a disconnected or closed character, select its profile and use Character settings → Session → Restart character… (also available in the character controls). Restart waits for the old process to release that profile and opens a normal login screen. You can cancel a pending restart.

Show active viewer separately removes fitted hosting while keeping session management. Advanced → Files & recovery → Stop managing… leaves the workers logged in as separate viewers. Closing the host lets you choose native logout confirmation or keep logged-in viewers.

Hosted characters can use the assistant in this release, with separate per-character opt-in and native permissions. Follow hosted assistant setup; an ordinary viewer configuration alone may not discover managed characters.

1. Log in, let Inventory load and arrange your viewer.
2. Open World → Workspaces & Layouts…, expand Save current as a new workspace…, give it a name and choose the components to remember.
3. Click Save. Double-click a saved entry or select it and click Switch.
4. Mark entries as Favorite and order them with Favorite up/down. Enable Show workspace favorites strip for quick access beside landmark favorites.

You can also save in Preferences → Move & View → Workspaces. Its Preview is live; OK keeps it and Cancel rolls back. Finish Preferences with OK or Cancel before using the quick switcher.

Add the Workspaces toolbar button if you want the switcher close at hand. An asterisk marks a changed arrangement; Update current confirms replacing its saved setup. Previous returns to the arrangement before switching, including unsaved positions, for this session.

Save up to thirty-two workspaces. Choose viewport/bar placement, Inventory windows and Received Items, maps, compatible chat geometry, and optionally toolbar buttons/display mode. Additional Inventory windows are supported, up to sixteen extra windows.

Remember Inventory folders adds single-folder roots and presentation modes, or a selected folder and visible expanded All Items branches (up to 256 per window). Folder contents, search filters and selected items are not stored. Missing or restricted folders are skipped and reported.

Optional graphics and camera groups can capture current values or use a named preset. Selected attached Inventory-backed HUDs can be restored with review. Restore adds missing selected HUDs; it does not save their internal state or remove unrelated HUDs, clothing or body attachments.

Use Apply only… → Apply group to load one saved component without loading everything. Full Switch and double-click load all included groups. Open the restore report to see fitted positions, missing folders or skipped components.

Workspaces belong to the logged-in account. Tabbed Conversations restores geometry without replacing chats or changing the selected conversation. Saved workspaces contain no messages or Inventory contents.

Under Move & View → Workspaces, startup restore can be Off, a named workspace, or the last arrangement at orderly quit. It starts Off and waits for UI/Inventory readiness. A manual switch cancels a pending startup restore.

Select Use for shortcut in the switcher, then assign keys in Preferences → Controls. Actions include the assigned workspace/layout, next/previous favorite, and returning to the previous arrangement.

Enable Snap utility windows to align supported windows with the frame, viewport or nearby windows; hold Shift to bypass. Arrange windows / more… offers alignment/distribution, export/import and a read-only diagram preview. That diagram does not apply the arrangement until you choose Switch.

Portable exports omit account-specific folder references by default and omit HUD references. Import files are limited to 1 MiB. Review entries and name collisions before accepting; keeping existing names is the default. Import does not automatically apply an arrangement.

World → Quiet UI (this session) temporarily hides navigation/favorites/toolbars and suppresses routine tip popups while keeping menus, open utilities and interactive requests available. It does not mute sound or accept offers. Toggle it again to return.

1. Log in and wait for Inventory to load.
2. Open Preferences > Local assistant, enable Allow local assistant access and choose narrow permissions. Start with a read-only task.
3. Open Setup, select your client and use Copy configuration. Use the bundled fs-mcp sidecar from this installation.
4. Merge the copied server entry into your client's MCP configuration, keeping your other servers. Reload the client or its MCP server.
5. Use the viewer's Check connection, then ask the client to check viewer status. A successful viewer check does not prove the external client loaded the configuration.

Codex, Cursor and Claude clients have different configuration formats. Use the configuration generated for that client and installation. Advanced manual and historical examples are in the MCP reference; see the release corrections before using old examples.

• “List my outfits and tell me what I am wearing.”
• “Find the shirt named Dusk under Clothing. Show the matches first.”
• “Preview moving these items into Studio shots.”
• “Show my saved workspaces and preview the photography setup.”

Permissions can be Never, Ask or Allow. New private reads default to Never; new feature changes generally default to Ask. A read-only preset is not blanket permission to read private chat. Custom exposes individual choices rather than restoring an earlier set.

Use these settings for this session only makes access and permissions temporary. OK saves accepted choices; Cancel restores them. When an operation is Ask, approve it in the native viewer. Your client's automatic approval does not bypass that prompt.

Some operations have additional gates. Workspace changes involving camera or HUDs need those permissions too. Nonzero upload charges require native review. Shared posing retains the other avatar owner's consent. Read the privacy and change limits before enabling broader access.

Ask for portrait, full-body, front, back, left or right framing, then wait for the outfit to finish updating. Specify UI/HUD visibility and output size.

camera_snapshot returns a temporary JPEG without uploading it. It defaults to the full window; request viewport_only: true for the world area.

inventory_snapshot_upload captures the world viewport by default and sets an outfit, folder or item thumbnail. The default thumbnail is free. A real texture upload quotes the L$ cost; a nonzero price asks in the viewer even when creation is Allow.

In Character Sessions, camera changes and snapshots require the exact target to be the active character. Camera and snapshot reference.

• Check access is on for the intended viewer or hosted character. Check the host's pause state.
• Wait for login and Inventory readiness, then ask for status again.
• Recopy Setup configuration from the intended installation. Old paths can start another installation's sidecar.
• Use Folderstorm discovery rather than Firestorm discovery. Hosted characters need their generated host configuration.
• Reload the correct client's MCP server. Codex project configurations require a trusted project.
• For loading-related timeouts, use a client tool timeout above the sidecar's default 90 seconds. Check the operation's receipt before retrying a change.

Keep discovery files and tokens private. Client configuration and diagnostics.

1. Log in to the intended character. Open host Preferences > Character settings > Local Assistant and enable Local Assistant for that profile.
2. Use Open native permissions... to activate that exact character and choose permissions in its viewer. Opening the dialog grants nothing by itself.
3. Select the MCP client, then Copy MCP configuration. This uses the matching sidecar and the hosted discovery registry.
4. Apply the accepted settings, reload your client and use Check connection for the exact logged-in character.
5. Have the client call viewer_list, identify the account and pass its exact viewer_session on managed-account calls. Re-list after a relog or restart.

A process ID alone is insufficient. Changing the MCP target does not switch the visible character. Camera changes, snapshots, workspace application and other operations requiring active ownership need the target activated first.

Ask approvals appear in Attention. Review in viewer... activates the correct owner for native review. Pause all MCP access stops pending and further assistant work after Apply; it keeps saved per-profile choices and also applies to newly launched characters.

Hosted assistant setup and exact-session rules.

Enable these features individually after reviewing their native permission controls. Start with inspection, then review the exact proposed change.

• Chat and contacts: inspect permitted live-login conversations, search their available history, prepare assistant-only drafts and explicitly send messages. This does not scan disk chat logs. Check account, recipient and text before sending; an uncertain send must never be automatically repeated. Sends are bounded to 1,023 UTF-8 bytes, one per second and six per minute. Social tools and exact arguments.
• Nearby world: observe the loaded subset of nearby avatars, objects, parcel, audio or media state. Results are incomplete observations, and media URLs are omitted. Observation permission alone does not authorize building or movement and teleport; those changes have separate permissions. World observation reference.
• Existing notecards and scripts: inspect a complete source snapshot, review an edit and save against that source's hash. Supported owned Inventory items require COPY and MODIFY; source is limited to 64 KiB. Script saves use Mono compilation, and source may be saved even if compilation fails. Task/object inventory is excluded. Check both save and compile receipts. Content editing reference.
• Gestures and posing: inspect before playing a hash-bound gesture or proposing a rotation-only own-pose change. Shared posing still requires the native avatar owner's consent. These tools are separate from editing Gesture Board definitions. Gesture and posing tasks.
• Selected preferences: preview, accept or cancel supported settings with revision checks. Arbitrary debug settings, security controls, credential and path changes are excluded. Preference tools.

Open host Preferences > MCP controller > Host access. Controller MCP starts off. Profile/monitor metadata and each action have separate gates, plus explicit Allow controller access for each profile. Apply or OK accepts changes; Cancel discards them.

Choose Never, Ask or Allow for activating characters, background policy, monitor previews, opening login windows, restarting, logging out or stopping management. Enabling controller access does not enable worker assistance or log anyone in.

The client resolves the exact controller and profile with controller_list, sessions_list and session_status. Changes use the current revision, worker generation/session and a fresh request ID. Inspect receipts if an outcome is uncertain before issuing another action.

Opening login never supplies credentials. Restart and logout keep native confirmation/cancellation. A monitor preview does not grant chat access or input ownership. Use the full controller reference for configuration, tool arguments and recovery.

1. Use the matching viewer and bundled sidecar, then connect your client. Explicitly Allow Read nearby world and media observations; the read-only and Ask presets do not opt into World reads.
2. Keep Edit owned world objects at Ask. Inventory-backed textures/materials also need Read inventory and outfits.
3. Identify the exact login with viewer_list and retain its viewer_session. Every building tool requires it, including in an ordinary viewer. For managed world changes, activate that character first.
4. Identify the exact loaded root object and ask the assistant to inspect it with build_object_get. Review ownership, position, size and face numbers before requesting a change.
5. Request one explicit transform, legacy face edit or material assignment using that read's expected_revision. Review and approve the frozen proposal in the viewer.
6. Inspect the original operation receipt and the actual object before continuing. A submitted request is not simulator confirmation.

Try: “Inspect this root object and show its position, size and face numbers. Do not change it yet.” Then: “Move that owned object to these region coordinates, keeping rotation and size. Show the change for approval.”

Building positions use region coordinates. Rotations use normalized [x,y,z,w] quaternions. A read returns a viewer-owned revision valid for 120 seconds, bound to the login, region and exact object state. If the target changes or the revision expires, inspect it again. Do not substitute a content-edit hash.

Edits require an owned, modifiable, movable, nonphysical root in the current region. Native restrictions still apply. Attachments, child-prim targets and physical roots are refused. Linked roots can move and rotate together; linked-set resizing stays in native Build.

• build_object_transform changes explicit position, rotation or scale. Requested positions must stay in this region and within 64 metres of the avatar, with native height limits. Scale follows the region's primitive limits with a 64-metre cap. These are different limits; an object read or rotation alone is not a promise of a 64-metre proximity check.
• build_object_surface edits one existing legacy face's RGBA, glow, fullbright and UV settings, optionally using an owned full-permission Inventory diffuse texture. A face with a PBR material refuses this legacy edit.
• build_object_material assigns an owned full-permission Inventory PBR material to one face and clears its existing overrides. The simulator must support the material capability. Editing PBR overrides stays in native Build.

Object reads require a loaded, unattached root volume in the current region, with at most 64 faces and 255 children. Reading a root does not select it or authorize editing it. Linking/unlinking, mesh upload, arbitrary object-content edits and object deletion are outside these tools.

Building reference and released native eligibility checks.

1. Enable World read and keep Rez world objects at Ask. Inventory rez also needs Inventory read.
2. Choose an explicit position in the current buildable parcel where your avatar is, within 64 metres, and obey native height/region and rez restrictions.
3. For build_rez_primitive, specify cube, sphere, cylinder or cone, plus position, normalized rotation and scale. For build_rez_inventory, identify one owned copyable Inventory object.
4. Review the proposal, approve it in the viewer, then inspect the receipt and world before another rez.

A primitive uses simulator-default permissions. Inventory rez retains the copyable source item; no-copy rez stays in native Build. Neither operation changes native selection or guesses the newly rezzed object's UUID. A queued/submitted result can have object_id_confirmed: false; do not treat it as a confirmed object or automatically repeat it.

1. Allow Inventory read and keep Change inventory next-owner permissions at Ask.
2. Identify the exact finished, owned Inventory item and read inventory_permissions_get. These tools do not apply to folders, links, Library, Trash or object/task Inventory.
3. Review the proposed next-owner Copy, Modify and Transfer together. Submit inventory_next_owner_set with the returned revision and all three explicit choices.
4. Approve the frozen proposal, then inspect its receipt and the item's native Properties.

Requested rights cannot exceed the current base/owner rights, and native Properties eligibility still applies. Copy=false with Transfer=false is refused. Landmarks and calling cards cannot be restricted here; environment settings cannot change Copy. Other masks and sale information stay unchanged.

Setting next-owner Copy=false is different from rezzing a no-copy item. The former can be eligible with Transfer=true; the latter is not supported by assistant rez. Inventory next-owner changes do not require the managed character to be active, but still target its exact login and permission state.

1. Use the matching viewer and sidecar, advertising navigation_tools: 1. Allow Read nearby world and media observations, which starts at Never, and keep Move your avatar and change flight at Ask.
2. Identify the exact login through viewer_list. Every navigation call requires its viewer_session, even in an ordinary viewer; a PID alone is insufficient. Managed changes require the active ready character.
3. Read navigation_status. Stand manually, finish existing native autopilot/follow/teleport actions, and land before requesting a walk.
4. Propose navigation_move_to with an explicit global destination, walk or fly mode, stop distance and timeout. Review the native approval.
5. Retain the returned operation_id and poll status. If you need to stop, use that exact operation ID and the same login.

Try: “Check this character's location, then walk five metres east if that stays in this region. Stop within one metre, allow fifteen seconds, and report whether you arrived.”

Walk/fly destinations must stay in the current region and within 64 metres in 3D. Stop distance is 0.25–4 metres and movement timeout is 1–30 seconds. Use global coordinates from navigation_status.position or world_location.global_position; do not pass map-local region coordinates directly. Height is 0–4,096 metres and native restrictions still apply.

Native autopilot may adjust the target height and cannot guarantee a route or arrival. Status exposes its native target. Login, region, position, flight/pilot state and arguments are frozen for approval; a changed baseline requires a fresh proposal.

navigation_flying_set explicitly takes off or lands using flying: true or false. It does not stand a seated avatar, choose a destination or override native flight restrictions, and refuses existing movement.

navigation_status reports global position, flight, native autopilot/teleport state and the last assistant-owned operation's ID, state and reason. It does not switch characters.

navigation_stop needs the exact returned operation_id and same viewer_session. It checks World read and source/active ownership, and cannot stop a newer manual pilot, follow or teleport. It does not request a fresh movement approval.

Stop does not promise landing. It preserves the current flight state; request explicit landing afterward when appropriate and no move is in progress. Switching, pause/revocation, source/region changes, restrictions, timeout or manual replacement stop owned movement. A later manual action wins and is not restarted.

1. Allow World read and keep the separate Teleport your avatar permission at Ask. Movement permission does not grant teleport permission.
2. Verify the exact login, active ownership when managed, and current status. Finish other native navigation first.
3. Request one navigation_teleport with an explicit global-coordinate destination. This tool does not accept a region name, landmark UUID or SLURL.
4. Review the proposal, retain its operation ID and poll status. Inspect the original receipt after any uncertainty instead of replaying the teleport.

The 64-metre/current-region and 30-second movement bounds apply to walk/fly, not teleport. Teleport starts pending; delayed maturity checks retain authority and permit at most one submission. Its internal authority deadline is 60 seconds.

Submitted is not arrived. An arrived result requires native completion and an observed position within five metres of the requested destination. Cancellation after submission is best effort and cannot undo arrival. Exact-operation Stop is not a guarantee that a simulator teleport can be recalled.

Select 1–50 Inventory items and choose Review bulk changes…. Preview a rename pattern or a move to an existing folder. Check the before/after rows and skipped entries, then Execute.

Enable Review assistant rename/move operations affecting 10 or more objects if you want native review of large assistant batches too.

Assistant inventory history… shows tracked operations from this login session. It is memory-only, bounded to 100 operations, 5,000 rows and 4 MiB, with entries kept for up to two hours. Review plans expire after ten minutes. Stop prevents remaining submissions; changes already submitted may still finish. Clear history neither stops work nor reverses Inventory changes.

Review undo is available only for confirmed eligible changes that still match their recorded state. Ordinary renames and copyable-item moves have limited recovery. Folder moves, Trash moves, links, non-copyable moves and unconfirmed changes cannot be undone here.

Exact history, confirmation and recovery limits

Open Outfits → Gallery. The thumbnail slider changes photo width from 80 to 256 pixels; names keep a fixed-height row. Use the assistant to capture free thumbnails directly from the world viewport.

This release includes alphabetical or newest-first outfit sorting with an independent favorites-to-top choice. “Newest” is estimated from the newest direct item in an outfit; folders do not have a reliable creation date.

Use Inventory gear → Tabs & Views → Show Library, synchronized across full Inventory views. Hiding it changes the view without removing Library data.

The sorting and Library controls are ports of newer Firestorm improvements. They are useful additions to Folderstorm’s earlier base, rather than exclusive Folderstorm features.

The published Windows Nightly uses an AVX2 build. Check your hardware and the package notes. Texture loading depends on the build, connection and computer; no particular speed improvement is promised here.

1. Open Gesture board from World, its toolbar button or Move & View > Workspaces.
2. Use Add or drag Inventory gestures or sounds onto the board. Links are supported. Adding a tile does not play it.
3. Click a gesture tile to play; click a playing gesture to stop it. A sound tile plays once, like Inventory Play, and has a speaker badge.
4. Right-click to change a tile's label, color or size, replace its item, move it or remove it. Drag tiles to reorder.
5. Use board options to create, rename, duplicate or delete boards and choose compact tiles. Page controls appear when needed.

Definitions save per account, up to sixteen boards with sixty-four tiles each. Removing a tile or board leaves its Inventory items alone.

Choose Options > Open board in new window. Up to sixteen windows can be open, each with its own selected board, page and geometry. The editor and picker are shared and stay bound to their owning board.

Extra windows are not restored on login. Workspaces do not restore boards. Opening the same gesture in several places still uses its single native playing instance.

Gestures can emit sound, animation and chat. Playing an inactive gesture activates it normally; stopping does not automatically deactivate it. Stop cancels queued work and stops gestures started by that board. It cannot recall sound or chat already emitted.

Missing items, loading and restrictions appear in tile states/tooltips. Inventory sounds play once; this is not an arbitrary audio-file player or a voice-input source. This release has no board-specific MCP tools or new board keyboard shortcuts.

Original multiple-window Gesture Board release (82164). That feature remains included in this guide's newer Nightly.

1. Open the viewer’s Poser. Shared posing requires the compatible Folderstorm LSL bridge; use the bridge bundled with your viewer.
2. Enable Share my pose to publish your pose to nearby compatible viewers.
3. To help pose someone else, select their avatar and choose Request permission. They receive a named Allow / Decline request explaining that accepting also shares their pose.
4. After approval, adjust the permitted pose. Each adjustment temporarily reserves affected joints to avoid overlapping edits.
5. The owner can remove an editor or choose Stop shared posing.

Receiving shared poses starts enabled. Publishing begins only when you choose Share my pose or accept a sharing/edit request. Ordinary local posing remains available.

Shared poses are visual; they do not move the avatar’s actual location in the region. Nearby users need a compatible Folderstorm build and bridge. Other viewers are not promised the same pose.

Sharing covers effective joint rotations, positions, scales, priorities and enabled states, including mirror/world-lock metadata. The owner validates edits, and each editor’s undo/redo avoids replacing unrelated joint changes.

Permissions are session-only. Grants and joint reservations expire on disconnect, bridge loss, teleport or inactivity; there is no permanent editor trust list.

This first shared version does not support shared animesh or cross-region posing. Existing local and owned-animesh posing remain available.

Shared poser design and limitations

1. If you want to keep a custom toolbar arrangement, turn off the normal Skins option that resets toolbars before changing themes.
2. Select Skin: Folderstorm or AnsaStorm, then choose the theme (called Colour scheme in AnsaStorm).
3. Click OK and restart the viewer to apply it.

The themes change UI colors and chrome while retaining the skin's layout, icons and language. They do not change world rendering. The selector's small previews illustrate a palette; they are not screenshots of your world or Inventory.

Theme guide, native previews and known validation limits.

1. Run Squirty Notes 1.2 or later.
2. In Squirty Notes Settings, enable API + MCP, Apply and Copy token. Keep the app running.
3. Open Folderstorm’s Squirty Notes window, paste the token and use the app’s port (default 47831).
4. Click Check connection or Test squirt. Select Off, All or Custom separately for IMs and friend logins.
5. Click Apply in this window to save. Closing without Apply discards its edits; the main Preferences Cancel does not undo this window’s Apply.

Both modes start Off. The Squirty Notes app controls the overlay recipe and monitor selection.

Squirt again after silence defaults to 120 seconds per resident. Every accepted incoming IM resets that person’s timer. Their first IM, or the next IM after the gap, can request a notice. There is no delayed notice when the timer expires; zero requests one for every eligible incoming IM.

Group, object, system and saved offline messages are excluded. Friend notices require a real offline-to-online change; initial login state stays quiet. Do Not Disturb, mute and receive restrictions still apply.

The separate Windows app receives a short notice containing the person's name, not the IM body. A connection test or accepted request does not prove an overlay appeared; check whether Squirty Notes is paused or unavailable. Failed notices are not replayed later.

Detailed connection and behavior reference

The bridge connects locally on your computer. Your chosen assistant client or model provider may receive tool results, photos, Inventory metadata or any private information you allow it to read. Review that provider's settings before granting access; a local bridge is not a promise that all processing stays on your computer.

Do not share discovery-file contents, access tokens, passwords or raw MCP configuration containing secrets in a support ticket, or forward the bridge port. Programs under your OS user can read discovery secrets. Generated configurations are intended for your local client. Squirty Notes tokens also stay private.

Keep per-character settings, caches and logs separate. Do not manually point several running characters at the same writable cache. Friendly profile names do not change the underlying account identity; verify the target and Send as label.

Moving a no-copy item can remove it from its source. Trash and restore have their own permissions; permanent deletion and emptying Trash are blocked by the assistant bridge. Do not assume all writes always ask: an Allow setting permits supported operations within its gates.

Review destinations and batch previews. Native history has limited session-only undo, not a complete backup. Stop and revocation prevent later steps; changes already submitted to the simulator may still complete.

If a change times out, inspect status, Inventory and the receipt before retrying. An uncertain response is not evidence that nothing happened. Uploads with a nonzero L$ cost require native review.

Crash reporting starts off. Choose it at first launch or later in Help > Crash reporting.... Host controls are under Preferences > Support > Crash reports.

Consent applies across the viewer, host and characters for the Windows user. Reports go to Sentry and can include native minidumps containing process memory or personal information. Chat logs and screenshots are not automatically attached.

Turning reporting off stops future uploads after processes observe the change; it cannot recall reports already sent. You can still report a bug without enabling automatic crash reporting.

Windows installers and Linux’s installer offer migration. You can also run migrate-settings.exe on Windows or migrate-settings beside the Linux viewer. On macOS, after copying the app to Applications, run:

"/Applications/Folderstorm.app/Contents/Resources/migrate-settings"

Existing files are kept unless you confirm replacement. Account folders, including toolbars, are a separate choice. Saved passwords, cookies, assistant tokens, caches and logs are excluded.

Use --dry-run to inspect the plan without writing. --accounts includes account folders; --overwrite and --overwrite-accounts explicitly replace existing settings and account folders.

For host character profiles, use the separate selective profile-copy controls.

toolbars.xml lives in a per-account folder beside user_settings, rather than inside it. Account-folder migration includes that file. Linux directory overrides are FIRESTORM_X64_USER_DIR and FOLDERSTORM_X64_USER_DIR.

Checked on 21 October 2026 against published Nightly 7.2.5.82177, source 24ac124. This is a Windows x86_64 AVX2 OpenSim Nightly prerelease.

Published source determines availability. This Nightly includes the prior Gesture Board and host stack plus guarded building/next-owner permissions, bounded movement, one-shot teleport and the release-discovery line-ending repair from the verified stack through #78. A draft or unmerged PR can already be included in a published build.

Check your viewer's build information against the release page before following a missing control. The website's older Nightly 82135 and Beta 81958 download labels are separate from this guide's baseline. This page does not certify which files are currently deployed on the live host.

Keep the complete bundle matched. Published host protocol is 17; mixing helpers from another checkpoint is unsupported. Existing technical guides retain historical protocol examples.

These links are pinned to this guide's released source so their context stays reproducible. Some upstream prose lags the code: the host/MCP README summaries say protocol 16, while this release uses 17. Older assistant introductions exclude chat, gesture or content editing that the released permission UI now supports. Use the generated setup configuration, current permission UI and this page's release corrections.

• Viewer user guide: viewport, workspaces, migration and original assistant workflows.
• MCP client and tool reference: configuration formats, diagnostics, Inventory, camera and operation arguments.
• Inventory review and undo: confirmation, session history and recovery boundaries.
• Character Sessions guide: profiles, host panels, monitors, controllers and assisted characters.
• Squirty Notes guide: external app connection and notification eligibility.
• Themes guide: skin choices, previews and acceptance limits.
• Project overview, feature summary and MCP documentation pointer.
• Released assistant feature registry and permission definitions: evidence for the expanded capabilities and defaults.
• Build from source: developer setup; separate from installing a published package.
• Current releases: check newer release notes before applying newer guidance.

Use Folderstorm's Mantis bug tracker. GitHub Issues is also available.

Include the exact build, Windows version, ordinary viewer or host, steps to reproduce, expected result and actual result. For a layout issue, mention display sizes/scaling. For MCP, identify client and operation plus a redacted error or receipt. Remove credentials, discovery tokens, personal conversations and private account details.

This help hub is based on released code and documentation. It does not replace native Windows, live simulator or external-client acceptance testing. This Nightly includes Windows compiler fixes for the building/navigation listeners; successful compilation does not establish live mutations, navigation arrival or coordinated-update acceptance.