When applications are run on the local computer the data for each session is stored in local files. Depending on the application's configuration it may be anywhere on disk, but by default it will be underneath the local common application data folder (often C:\ProgramData\Gibraltar\Local Logs). The Loupe Agent automatically prunes session data out of the repository to ensure that it doesn't consume too much disk space. Because of this, any data that you want to keep for further analysis should be sent to a Loupe Server.
If you are working with an application locally that uses a non-default logging path and want to see its sessions in the local sessions view you need to add the path. To do this, select the Local Sessions node in the tree view and then the Open Log Folder option on the right hand command view.
The Local Session Repository is just a quick way of finding data about the applications that ran on the local computer. You should work out of a Server Repository in most cases - this is where you can see all the sessions available on a Loupe Server. Some features are only available in the Server Repository - like error analysis.
The most convenient way to transfer sessions between repositories in the Loupe Desktop is to drag them from the Sessions list on the Repository View to the Repository or Repository Folder that you want to store them in.
When working with an end-user that doesn't have access to the Loupe Desktop you should use the Packager Wizard to bundle up all of the sessions you want into a package to send it back to you for analysis.