Panel by panel and button by button — what everything in the ouRGeo window does.
01 The window layout
One toolbar, four zones, every panel anywhere you want it.
ouRGeo is a single window. A thin toolbar runs across the top; below it the space is
divided into four zones — left, centre, right and bottom — and a zone
only exists while something is open in it. Every divider can be dragged, and
double-clicking one evens out the panels sharing it.
Any panel, any zone
Nothing is nailed down by which zone it started in. The map can go on
the left, the console on the right, the environment along the bottom. Defaults are
only defaults: the code editor and
console open in the centre and bottom, the
spatial editor, plots,
AI assistant and help on the right, and
Environment, Packages and
Databases on the left.
Split or tabbed
Panels sharing space either split it (both visible, a divider
between) or form a tab group (one at a time, a tab strip to switch). Splits
nest in either direction — an editor can stay full height on the left while
its neighbour on the right splits top and bottom. The bottom zone ships as one tab
group: the R console, the terminal
and Project Files.
Docking a pane
Switch on Settings → Workspace → Drag panels to rearrange
them, then drag a pane by the grip in its top-right corner, or by its
pane-group tab, over another pane. Its border highlights; release to choose
Vertical (left/right), Horizontal (top/bottom) or Tab group,
and for a split, click the half where the moved pane belongs. Nothing moves before
that last click — Esc, Cancel or clicking outside leaves the
arrangement alone. Empty zones are still direct drop targets.
Other ways to move
Settings → Workspace shows the whole arrangement at once;
right-click a grip for that panel’s menu; or ask the AI assistant, which can
dock one pane beside another without the drag grips switched on.
More than one editor
The code editor is the one panel you can have several of — up to
four. Add one from Settings → Workspace or the panel grip, then drag document
tabs between them, or use Move to in a tab’s own right-click menu.
Removing an editor hands its documents back rather than closing them.
Presets
Save an arrangement by name and apply it later, export it as an
.ourgeolayout.json file to share, or restore the default from
Settings → Workspace.
Panels are toggles, not tabs — you can have the environment, the map and the AI
assistant all visible at once, and the layout you leave behind, pane groups included,
is restored next time. Panel sizes deliberately are not: a zone opens with its
panels sharing it evenly, however you dragged them yesterday.
02 The top toolbar
Fourteen icon buttons run along the left, with Settings and the
project dropdown pinned to the right. Buttons that toggle a
panel turn blue while that panel is open; the rest open a dialog or perform an
action. Which of the fourteen you keep, and in what order, is yours to set in
Settings → Workspace.
Opens the Settings dialog. Pinned to the right
of the toolbar.
03 Project menu and R status
At the far right of the toolbar, next to Settings. It shows the current project’s
name and carries a small coloured dot reporting whether the R backend is connected.
A second dot means the project has unsaved changes, kept on this computer.
Save
Writes everything into the project file. Disabled in scratch
— scratch has nowhere to save to; use Save As.
Save As…
Creates a new .ourgeoproj from the current state. This is
how a scratch session becomes a real project.
Revert to Saved…
Discards working changes after listing what will be lost.
New
Returns to a clean scratch workspace.
Load…
Opens a .ourgeoproj and restores its environment, layers,
plots, documents, chats and databases.
Files dropped when you left scratch, ready to reopen.
A saved project’s working state is kept on this computer between saves, so
closing ouRGeo or switching projects never costs work. How saving, closing, crash
recovery and conflicts work is in Projects &
Files.
04 Code editor and tabs
The editor is Monaco — the same editor as VS Code — with R syntax
highlighting and autocomplete driven by your live R session, so it completes on
objects that actually exist and functions from packages you have actually loaded.
The tab bar
New blank .R file
Opens an empty script tab. Same as Ctrl+N.
Create data object
Opens the Create Data dialog for
building a data frame, matrix or vector by hand.
Tab types
Tabs are either code tabs (.R files and untitled
scratch) or object tabs — a data viewer or function editor bound to an
R object. Object tabs whose object no longer exists are pruned when a session is
restored.
Closing Ctrl+W
Closes the active tab. A document with unsaved edits asks
Save / Discard / Cancel first — from its ×, Close Others,
Close All or the assistant too — and closing several adds Apply to
all remaining.
Long tab strips
Only the tabs on screen are drawn, so dozens of open documents stay
responsive. Hover a tab to read its full name, file and unsaved state.
The editor toolbar
A hint strip on the left reminds you of the two run shortcuts; two buttons sit on the
right.
Line
Runs the line the cursor is on and moves to the next.
Same as Ctrl+Enter.
Run All
Runs the entire contents of the tab.
Keys
Action
Ctrl+Enter
Run the current line, advance the cursor
Shift+Enter
Run the selection, or the current line if nothing is selected
Ctrl+Space
Trigger autocomplete manually
Ctrl+S
Save the active tab
Ctrl+N
New tab
Ctrl+W
Close the active tab
05 The R console
Titled R Console, below the editor. This is a real R prompt: anything you can
type in R, you can type here, and everything the GUI does appears here too.
Input
Type and press Enter to run.
Shift+Enter inserts a newline instead, for multi-line
expressions.
History
Previous commands are recalled with the arrow keys.
Output
Standard output and errors are streamed live from R rather than
arriving in one block at the end, so a long-running command reports progress as it
goes. Errors and warnings are colour-coded.
Plots
A plotting command captures its output automatically and sends it to
the Plots panel.
Copy all console output
In the console header. Copies the complete history, including
entries scrolled out of view — long histories only draw what is on screen,
so they stay fast however long the session runs.
Clear console
Empties the scrollback. It does not touch your R session —
objects and loaded packages are untouched.
In a saved project the console history is kept with the project’s working state
and comes back when you reopen it. In scratch it is dropped when you leave — see
Scratch and saved projects.
06 The terminal
A Terminal tab beside the R console, running your own shell — bash, zsh,
fish, PowerShell, whatever you use. There is a real pseudo-terminal behind it, so
top, vim, git, job control and colour all behave
exactly as they do in a terminal window. Nothing starts until you click the tab.
More than one shell
Open as many as you like from +, rename them, and pick a
different shell from the arrow beside it. A tab shows a dot when a command finishes
in one you are not watching.
The directory bar
It opens in R’s working directory, and the path in the header is a
control: change directory, copy it, open it in your file manager, or reconcile the
two — send R to the shell’s directory, or type cd to
R’s.
Keyboard
Everything goes to the shell, including Ctrl+C,
Ctrl+R and Ctrl+D. The exceptions are
Ctrl+Shift+C/V for copy and paste,
Ctrl+Shift+F for search, and
Ctrl+=/- for text size.
Colours
The ANSI palette follows your code theme and the
surface follows your app theme, so ls looks like it belongs in the
window it is in.
Its own pane
Settings → Terminal puts it beside the console instead of in
a tab with it. After that you can drag it anywhere, and ouRGeo leaves it
there.
Reload the window and your shells are still running, with their scrollback. Close ouRGeo
and they are gone: terminal output is never written to disk — not into a
project bundle, and not into the session file.
The AI assistant can use the terminal, but only behind a third switch in the panel
footer that is off by default and AND-ed with Autopilot. It is not a sandbox: R’s
own system() reaches the same machine. What the switch means is that you
decided, once and deliberately, that running commands on your computer is part of what
the assistant does — and every command it runs is typed into a tab you are
watching and logged to the R console.
07 Environment panel
A live browser of the objects in your R session, grouped by environment. It updates
itself when R’s global environment changes — you never need to refresh it
manually after running code.
Search objects…
Filters the list by object name.
New Environment
Creates a named environment to organise objects into. A prompt asks
for the name.
Load .RData
Loads an .RData file into an environment.
Export
Writes environments to an .RData file on your computer,
and echoes the exact save() it ran. Objects can also be exported as
CSV, Excel, text or an .R file — and Export to Project
Files saves them into the project’s
library instead.
Refresh
Forces a re-read from R. Rarely needed — the panel is
event-driven — but useful if something modified the environment out of
band.
Close panel
Hides the panel; same as the toolbar toggle.
Object rows
Each object shows its name, type and size. Clicking a data frame,
matrix or vector opens it in the Data Viewer; clicking a
function opens it in an editor tab. Right-click for remove, rename, copy and move
between environments.
08 Packages panel
Your installed R packages, with attach state. Like the environment panel it is
event-driven: library() at the console updates the panel immediately, and
the editor’s autocomplete along with it.
Search packages…
Filters the installed list by name.
Checkbox per package
Attaches or detaches the package — the equivalent of
library() and detach(). A package installed in more than
one library lists each copy; ticking one loads that copy with
library(pkg, lib.loc = …), unloading the current one first. If
another loaded package imports it, the console explains what must be unloaded or
that R needs a restart.
Install package
Opens the install dialog. Searches CRAN and installs into your chosen
library.
Update packages
Checks for newer versions and offers to update. Reports
Already up to date when there is nothing to do.
Add library path
Registers an additional library directory, for packages kept outside
your default library.
Refresh packages
Re-reads the installed list from R.
Close panel
Hides the panel.
After a major R upgrade, packages must be rebuilt before ouRGeo can connect. The
health check finds packages built for an older R and
duplicate copies across libraries, and repairs them with your approval — or run
update.packages(ask = FALSE, checkBuilt = TRUE) yourself.
09 Databases panel
Manages .Rgeo datasets — DuckDB-backed containers for vector and
raster data too large to sit comfortably in memory. See
.Rgeo databases for what they are and when to use
one.
Search databases & objects…
Filters across connected databases and the tables inside them.
Workspace
The folder the panel browses for .Rgeo files.
Choose workspace folder
Points the workspace at a different directory.
Create database
Makes a new empty .Rgeo file.
Open .Rgeo file
Connects an existing database. Connected databases show their tables;
a disconnected one is marked closed.
Recent
Databases you have opened before.
R variable name
When connecting a table, the name its lazy reference takes in your R
environment.
Refresh
Re-reads the workspace folder and connection state.
Close panel
Hides the panel. Database connections stay open.
10 Data Viewer
Opens as a tab rather than a panel — alongside your scripts, not in a sidebar.
Toolbox runs open their result here automatically, and clicking an object in the
Environment panel opens it here too.
Data frames get a sortable, scrollable grid. An sf layer shows
its attributes with the geometry column alongside.
Matrices and vectors get their own views suited to their shape.
Add Column and the column type dropdown let you edit structure in place.
Data checks opens a read-only profile of the whole dataset — geometry
validity, CRS and units, field types, missing and repeated values — with the
affected rows. See Data checks.
Export layer…, on spatial data, saves a GeoPackage or GeoJSON that is
read back and verified before it is published. See
Checked vector export.
Add to Map sends a spatial table to the spatial editor.
Viewer tabs are remembered within a session and pruned on restore if the object
behind them is gone.
Tools that produce a raster skip the viewer — a SpatRaster is not tabular. Those
results appear in the Environment panel and can be added to the map.
11 Plots panel
Every plot your session produces, in order, with history. Any plotting command in the
console or editor lands here automatically.
Previous plot / Next plot
Step back and forward through the plot history.
Previous view / Next view
Step through active views — live previews distinct from
the static plot history.
Active View
Switches to the live view mode. Empty state reads
No active views yet.
Create chart
Opens the Chart Builder — build a ggplot2 chart from a dataset
through a form, with the generated R shown as usual.
Export plot
Re-renders the current plot at a size and format you choose, rather
than screenshotting the panel, so output is publication-resolution. Save to a
folder or into Project Files; either way
the console records the ourgeo_save_plot() call.
Open in separate window
Pops the plot out into its own window, which keeps updating as new
plots arrive. Useful on a second monitor.
With no plots yet the panel reads No plots yet. Run a plot command in the
console.
12 Project Files
The project’s document library, in a tab beside the R console and Terminal and
from the project menu. Reports, PDF standards, Word documents, spreadsheets, figures
and data live here — copied into the project, or in linked folders that stay on
disk.
Add files
Copies files into the project; you can also drop them onto the pane.
In scratch it reads Save project to add files.
Linked folders
Link, create, rescan, relink or forget folders whose originals stay
where they are.
Filters and search
By location, role (Reference, Standard, Example), logical folder,
status and assistant availability.
Preview / details
A read-only preview, the file’s name, folder, description and role,
and Attach to chat, Export original, Replace file and
Reindex file.
R reads and writes the library with ourgeo_project_file() and
ourgeo_project_path(). Everything about it is in
Projects & Files.
13 AI Assistant
A chat panel that knows about your R session — and, if you let it, can drive it.
The panel holds as many conversations as you like, a model selector, the
Thinking and Context controls, the Autopilot, Web and
Terminal switches, Attach context, and dictation. Its
Memory Library sits below the conversation.
Providers
OpenAI, Anthropic and Google with an API key; local models through
Ollama, LM Studio, llama.cpp and other compatible servers; or your Claude or ChatGPT
subscription.
Context
It retrieves what a request needs — layer schemas, console runs,
documents, project files — and the summary under each reply shows what it
used.
Memory
About you, Project and Conversation memories, added directly or by
saying “Remember that…”, with no model call.
Controls
Source and column privacy, estimated chat budgets, separate models for
documents and images.
The AI panel with Autopilot enabled — the agent writes and runs R, streaming its reasoning and code inline.
14 Help panel
R’s own documentation, in-app. No browser round trip, and it works offline.
Search functions & packages…
Searches help topics across your installed packages.
Back / Forward
Navigate your help history like a browser.
Home
Returns to the help index.
Package vignettes are available here too, rendered in the panel. Typing
?st_buffer at the console opens the topic here rather than in a browser.
15 Plugins and the plugin store
A plugin adds capability while the app is running — data connectors, toolbox
tools, AI actions, toolbar buttons, docs topics, R libraries and whole panels. Manage
them from Settings → Plugins.
Plugin Store…
Browse what other ouRGeo users have published, in the app or at
ourgeo.dev/plugins. Every listing has been installed and
run by a moderator before it appeared. Browsing is open to anyone; installing
needs your free ourgeo.dev account — the same one the forum uses —
because plugin downloads are not public.
Enabled
Each plugin is a switch. What you install arrives switched
off: turning it on is when code starts running, and that stays your decision.
If a plugin ever takes the app down, ouRGeo notices on the next launch, disables
that one and says so.
Install from file
Opens a .ourgeoplugin archive somebody sent you. Archives
are checked and bounded on the way in.
Updates
Checked once per session when you open this section or the store, with
the author’s note about what changed. They are offered, never applied for
you. A version withdrawn after you installed it is switched off, with the reason in
the console.
Publish…
On a plugin you wrote: ouRGeo builds it, uploads it and puts it in the
review queue. A moderator installs it, runs it, and either publishes it or sends it
back with a note you can read. What people download is a built, minified bundle
— your source is never published, and a plugin installed from the store cannot
be exported or read back out of ouRGeo.
Reviews
Rate and review from the plugin’s page on the website. It takes
having actually installed it — a rating from somebody who never ran the thing
is an opinion about the description.
The AI assistant can search the store, read a listing and install from it (installing
asks you to confirm, like any destructive action), and it will look there before
offering to write you a plugin from scratch. It cannot enable what it installs, submit
a plugin, or write a review — those publish under your name or change what runs.
From 1.16.0, plugins can declare a managed native JavaScript background
service with an explicit service permission. ouRGeo owns startup and
shutdown and supplies a private loopback connection. Disabling the plugin, losing
its renderer or quitting stops the service; persistent plugin data lives outside
the replaceable plugin folder. This grants native system access. Plugin panels
have their own error boundary so a failed panel does not crash the workspace.
Plugins can also contribute skills and Markdown context sources for the
assistant, behind a separate context-source permission, and memory
profiles behind a memory-provider permission. Enabling a plugin shares
nothing by itself, and an update that asks for new permissions switches the plugin
off until you review it. See AI Assistant.
16 Settings
Open Settings with the gear at the right of the toolbar. Categories are listed down
the left in four groups — Application, Maps & data,
Assistant and Extensions — or in a dropdown when the window is
narrow. Every change takes effect the moment you make it; there is no OK button. The
header shows the running version and a button for the
version history.
Application
Health check
Run health check… walks through R, its packages, the S2
engine, your computer and the AI assistant, with approval before any repair,
download or credit use. See The health
check.
Updates
Check for updates… runs a check on demand, Check for
updates when ouRGeo starts switches the startup check, and Show reminders
again clears a skipped version. See Application
updates.
Appearance
App, code and Markdown themes, background images and the Theme
Studio — below.
Projects
What closing a saved project does, whether a project save also
writes open documents, the R snapshot interval, and Stored unsaved
changes for clean-up. See Projects
& Files.
Prompts
Every question you have told ouRGeo not to ask again, each with a
switch to bring it back.
Workspace
The whole arrangement at once: which panel is
where, which toolbar buttons appear and in what order, a second code editor,
named presets, .ourgeolayout.json export and import, Drag panels to
rearrange them (off by default), and Restore default arrangement.
Terminal
Which shell new tabs start, font size, cursor style, and whether the
terminal gets its own pane beside the console.
R Backend
The R installations ouRGeo found; pick one and R restarts against it,
or Browse for Rscript…. A successful switch confirms with R
restarted successfully.
Documents
Which package the Chunk: current map and Chunk: export
current plot ribbon buttons write — tmap or
ggplot2.
Appearance
Theming has three independent axes, each with its own picker.
App theme
The whole interface — panels, buttons, borders, labels —
plus the editor’s background, the artwork behind the code, and the basemap
the Spatial Editor opens with.
Code theme
Syntax colours only: R in .R files and every embedded
language inside an .Rmd chunk.
Markdown theme
Prose colours only: headings, links, quotes and inline code, in both
Source and Visual mode.
A code or Markdown palette carries token colours and nothing else, so switching one
never moves the editor background or the artwork behind it. Each app theme names the
code and Markdown palettes it starts with, and switching the app theme resets both
— the two editor pickers are how you depart from the default.
App themes are arranged in four tabs:
Illustrated
Ten painted themes — Dark, Bespin, Neon Lights, Forest, Midnight
Dream, Candy Addiction, Heaven, Volcanic, Arctic and Retro Terminal.
Legacy
The same ten with their original artwork, for anyone who preferred
them.
Field collection
The thirteen palettes of this website — Dev, Slate, Basalt,
Forest, Trout, High Alpine, Wood and Sextant (dark); Glacier, Field Notes,
Rainproof, Albany and Linen (light) — each with six nature photographs and
matching code and Markdown palettes, marked · Field.
The Field collection — Dev, Forest, Albany and Linen, each with its own photograph and matching code and Markdown palettes.
Background images
Background images…, beneath the app themes, opens a gallery for the current
theme. Every painted theme has its original artwork, five more paintings and a looping
GIF; each Field theme has six photographs. Legacy and custom themes keep their own
artwork and offer the related gallery too.
Select one image for a fixed background, or several for a slideshow
in the order you picked them, and set Switch every from 5 to 3,600 seconds.
Restore default selection goes back to the original.
A GIF badge marks animation. Thumbnails stay still; Play GIF
preview shows the motion before you choose.
Link image folder… adds your own PNG, JPEG, WebP and GIF pictures (up
to 8 MiB and 24 megapixels each). Rescan, Locate… and
Forget manage the link; forgetting never touches the folder or its
images.
Background visibility sets how strongly the artwork shows, from 0% to 100%,
per theme; Theme default restores the authored look.
With your system’s reduced motion preference on, GIFs show a still frame
and slideshows hold one image. Animation also pauses while ouRGeo is hidden.
Background images for the Glacier theme — six photographs as a slideshow, with background visibility and linked folders.
Interface scale is separate from the theme and is changed with
Ctrl+Shift+= and
Ctrl+Shift+-.
Theme Studio
Settings → Appearance → Theme Studio… opens a full editor for
themes of your own, on all three axes. It has a tab per axis, the app themes grouped
as collapsible Illustrated, Legacy, Field collection and
Custom lists, and a live preview that updates as you type
without changing the running application — so you can look at a theme
you have not switched to.
Every theme starts as a copy. There is no blank theme, on purpose: an app
theme has sixteen colours, and starting from nothing produces something that clashes
with whichever ones you forgot. Press New, pick the closest existing theme
— one of ouRGeo’s or one of your own — name it, and change what you
like. The themes that ship are read-only, because an ouRGeo update would overwrite an
edit and leave nothing to reset to; Duplicate to edit is the way in.
Interface colours
Ten values: background, panel, border, accent, accent hover, muted
text, success, warning, error and foreground. Each is labelled with what it
actually paints, and carries a WCAG contrast warning when text would become hard
to read against its own background.
Editor surface
Six more, kept separate because the shipped themes give the editor a
slightly different surface from the panels around it: the editor background, the
current-line highlight, indent guides, the caret and selection, line numbers, and
editor text. Match the interface colours collapses the distinction in one
click.
Editor palettes
Which code and markdown palette this app theme starts with —
including palettes you made yourself.
Map
The basemap the Spatial Editor opens with under this theme. The
basemap picker still overrides it for the session.
Artwork
Two optional images — see below.
A code or markdown theme is simpler: a name, whether it is listed for dark or light
app themes, and its colours. A code palette has eleven (identifiers, comments,
keywords, constants, strings, numbers, operators, functions, tags, delimiters,
errors); a markdown palette has nine (body text, headings, emphasis, links, code,
quotes, meta, HTML, escapes). Contrast is measured against the editor background of
the app theme you are using, because that is the surface the palette will be read
on — a palette carries no background of its own.
Theme Studio: your own artwork
An app theme can carry two images, both optional and both embedded in the
theme rather than referenced by path — so an exported theme arrives on another
machine with its pictures intact.
Editor backdrop
Painted behind the code editor, replacing the generated scene. PNG,
JPEG, WebP, SVG, GIF or AVIF, up to 4 MB. Scaled to cover the panel, so a
wide 16:9 image around 1600 × 900 fills it without the middle being
cropped out. It has its own opacity and a grey-scale switch: the
shipped scenes are drawn to be greyed to 15%, while a photograph of your own
usually wants colour and a lower opacity. It sits under the text, so a calm,
low-contrast image reads far better here than a busy one.
Theme card
The theme’s tile in the App Theme picker, cropped to 16:9 —
320 × 180 is plenty. Same formats, up to 1 MB. Leave it empty
and the card uses the backdrop, or the scene ouRGeo generates from the
theme’s own colours.
Theme Studio: sharing themes
Any theme you have made exports to a .ourgeotheme.json file — plain
JSON, artwork and all — and imports back from one. The file declares which axis
it belongs to, so an app theme dropped into the Code Themes list is refused with a
sentence naming what the file actually is and which tab takes it, rather than a
cryptic parse error. Files written by a newer version of ouRGeo, and files that are
not themes at all, are turned away the same way.
The AI assistant can drive all of this: ask it for “a warm, low-contrast dark
theme” and it will copy the closest one, adjust the colours, check its own
contrast ratios, and switch you to it.
Maps & data
Spatial Editor
Initial Spatial Extent — the view new sessions open at.
Drawing — whether finishing a feature prompts for its attributes.
Coordinate Reference Systems — the default CRS for new geometry, and
the default calculation CRS that a tool means by Default (from Settings);
see Calculation CRS.
Project Files
Whether exports ask before replacing a file already in the
project library.
Basemaps
Access tokens for tile providers that need one (Mapbox, MapTiler,
Stadia). Providers that need none work without configuration.
Data API Keys
Keys for Data Connector sources
that need authentication — Kaggle, US Census, Statistics Canada, NOAA, FRED,
and an optional Socrata app token.
Assistant
AI Assistant
Eight pages: Memory Library, Provider & model,
File analysis models, Learning & context, Privacy &
sources, Budgets, Storage & recovery and Advanced. Each
is described in AI Assistant.
Voice input
The microphone and the transcription service. The default runs
on your machine: ouRGeo downloads a speech model on first use and never
sends the audio anywhere. Cloud services (OpenAI-compatible, Groq, Deepgram,
ElevenLabs, AssemblyAI) are available and each upload is logged to the R console.
Recorded audio is never written to disk.
Extensions
Plugins
The plugin list, the enable switches, Plugin Store…, install
from file, and the update check. See Plugins and the plugin
store.
17 Application updates
From 1.16.35, installed builds check ourgeo.dev for a newer installer shortly after
startup. If you are current, offline, or on a platform with no published installer,
nothing appears, and the check never holds up the workspace or R.
When an update is available, the dialog shows the installed and available versions,
with Release notes. Download update opens the official download in your
browser; Save project… and Close ouRGeo… help you finish
before installing, and the steps for your installer are shown:
Installed as
Update
Linux AppImage
Download the new AppImage, make it executable, replace
the previous file and update any launcher shortcut.
Debian / Ubuntu package
Open the .deb in your package
installer, or sudo apt install ./ouRGeo-X.Y.Z.deb.
Windows
Close ouRGeo and run the new .exe installer.
Source checkout
No startup check; update with your usual source
workflow.
ouRGeo never downloads or runs an installer itself, and never replaces its own files.
Remind me next time (or Esc) dismisses the prompt for this session;
Skip this version stops reminders for that version only. The check sends no
project files, chats or credentials, and your projects, settings and R installation
are untouched by updating.