Elyra
Elyra The coding agent eTerm The terminal that knows where each command ends Huskarl AI colleagues on your own Mac Starf An activity monitor for Apple silicon that never invents a number etrans An SSH and SFTP client for macOS Elyra VM Virtual machines for macOS, Linux and Windows on your Mac Litr A small, native web browser for macOS Notr A notebook for macOS e The native code editor Elyra Grove Native local development environment Askr The real server for Laravel & PHP Elyra Framework Rust + Svelte 5 framework for desktop apps Elyra Conductor Local project conductor Refr Local-first PDF workspace for macOS Elyra Workspace A desktop workspace for coding agents Elyra SQL Server MySQL-compatible SQL server in Rust Elyra Félagi Agents as teammates on one board Elyra SQL Client Native desktop SQL workbench Elyra SQL Anywhere Replication-ready SQL engine Elyra Sjá SEO & GEO workspace for macOS Elyra DataGrid Server-driven data grid for Laravel
Start here
Concepts
Release notes
What's new
Elyra
Working offline

Working offline

The app keeps a copy of what you've read, and keeps working without a connection.

When the connection drops

A bar at the top says Offline since time — showing what was read last.

  • You can still read the conversations, issues and pages you've opened before.
  • Messages you send wait and are sent when you're back online. They show in the conversation as Sends when you're back online.
  • Reactions, marking things read, following issues and saving doc pages wait the same way (Saved here — sends when you're online).
  • Things that need the server right away — searching, creating channels, signing in — tell you they can't reach Félagi.

When the connection comes back the waiting changes are sent in the order you made them, and the app reads again what changed meanwhile.

Changes waiting

The bar shows how many changes are waiting. If the server refused one when it was finally sent — the channel was archived meanwhile, or somebody else changed the same page — the bar says so; choose Review to see each one and Try again or Discard it.

Because waiting changes are yours and would be lost, the app won't let you sign out (or switch to another workspace's sign-in on the same server) until they're sent.

With several servers

Each server keeps its own copy and its own waiting changes. A change made on one server is only ever sent to that server; if you switch to another server before it's sent, it waits and goes when you switch back.

A message that failed

A message that couldn't be sent shows Try again and Discard under it.