Break down supported ServiceNow scripts with platform-aware guidance and clearer logic flow.
Built for ServiceNow work that has to hold up in real delivery.
SN Assistant helps ServiceNow developers understand scripts, challenge weak patterns, launch slash commands, and document code or Update Sets without leaving the platform. It is designed to stay closer to ServiceNow reality and further away from polished nonsense.
Less guessing. More useful platform work.
Ask technical questions about the current script without switching context or losing the current record.
Improve structure and implementation quality while staying closer to valid ServiceNow patterns.
Add JSDoc and inline comments so inherited code becomes easier to review and maintain.
Generate Word documentation for scripts directly from the browser.
Capture visible Customer Updates and produce change documentation for sys_update_set records.
A command palette for the tasks that repeat every day.
Open one surface from anywhere in ServiceNow, run built-in slash commands, or define your own shortcuts for common tables and filtered views.
Open the palette from any ServiceNow page with a browser shortcut and keep moving without hunting through menus.
Run commands like /ask, /explain, /document, /docset, and /imp from one place.
Create your own aliases for incident lists, user lookups, favorite tables, or saved query patterns inside your current instance.
On supported records the assistant opens in full mode; on generic ServiceNow pages the palette becomes the lightweight entry point.
Only what is verified gets promised in public.
SN Assistant is intentionally specific about what counts as current public support.
sys_script
sys_script_include
sys_script_client
sys_script_fix
sys_ui_action
sys_ws_operation
sysauto_script
sys_update_set
You decide where requests go.
The public release keeps the model simple and explicit.
Anthropic, OpenAI, Gemini, OpenRouter, custom endpoints, and local LLM setups are supported.
Provider secrets such as API keys and custom auth headers stay in local browser storage on the current device.
Breaking Trail retrieval happens locally inside the extension and is enabled only where it improves quality.
The public release is intentionally simple: install the extension, configure a provider, and work.