Reticle/ Docs Get Desktop
Documentation/Build your map
On this page

Workspaces and files

A Desktop workspace is one YAML file. Reticle edits that file in place and uses your host's tools to work with the systems you configure. Team serves one file chosen by the daemon operator.

Open, create, or copy#

Use the Desktop workspace menu at the top left:

  • Open file… opens an existing YAML file without copying it.
  • New workspace… asks for a filename and creates an empty topology if needed.
  • Samples asks where to save a copy before opening it.
  • Recent lists previously opened files. Removing a recent entry keeps the actual file. A missing entry means the file has moved or been deleted.

Reticle starts with config.yaml in its application-data directory. Recent files are shortcuts, not a guarantee that the last-opened file will reopen after restarting. Check the file path in the bottom status bar before editing.

Understand saving#

Canvas changes autosave after roughly 800 ms without another edit. Node details in the Inspector are staged: choose Save details or Discard. Check and action forms have their own Save operations button. Notes save when the field's change is committed, such as when you leave the field.

Reticle writes YAML through a temporary file and replaces the existing file. It preserves top-level operational definitions when you save the visual map. Comments and hand formatting are not preserved by YAML serialization; unknown node fields are not a supported round-trip extension format.

Deleting a node also removes its connected edges and persisted checks/actions. Actions that require a removed collector are pruned too. Deleting a node with operations prompts for confirmation and clears visual undo history: restore a backup or Git revision if you need those definitions back.

Edit with another tool#

Reticle watches the active file and reloads external changes when there are no pending local edits. If an Inspector draft or unsaved change is open, it reports a conflict rather than silently replacing your work.

Team also checks a configuration revision on saves. A stale save is refused; there is no automatic merge. Record the local edits you need, then reload the current configuration and reapply them. A PDF can preserve a visual reference, but it is not a recoverable copy of command definitions.

Switch workspaces#

Save or discard Inspector drafts before switching. Reticle flushes pending visual saves, blocks a switch during a running named action, and closes open terminal sessions when the workspace changes.

Privileged trust is held in memory per canonical file path for the current app session. Switching away does not revoke a previously trusted file: switching back during that session can enable its commands again. Disable privileged mode to revoke trust, or restart the app. The RETICLE_ALLOW_CUSTOM_COMMANDS=1 process override trusts all workspaces and cannot be disabled through the UI.

Find application data#

Platform Default directory
macOS ~/Library/Application Support/com.matt.reticle/
Linux $XDG_DATA_HOME/com.matt.reticle/, or ~/.local/share/com.matt.reticle/ when no absolute XDG data path is set
Windows %APPDATA%\com.matt.reticle\ (normally under AppData\Roaming)

The directory contains the initial config.yaml, recents.json, and installed sample templates. Files you open elsewhere remain at their own paths.

Back up and use Git#

Back up every workspace YAML file you care about. Application data alone is not a backup of files elsewhere. Reticle does not provide cloud sync, automatic Git commits, or a version-history browser.

SSH credentials remain in your OpenSSH setup. Reticle is not a secrets manager: anything you put into notes, URLs, command definitions, or YAML is still file content. Graph-visible fields and published check output can be read by Team viewers and integrations.

View Markdown Report a docs issue
Reticle documentationDraw intentionally. Operate with context.

↑ ↓ to move · Enter to open · Esc to close