The basic implementation has been done.

You can try like the followings.

$ yay -S tym-git --editmenu

and edit the line source=('tym::git+https://github.com/endaaman/tym#branch=master') from master to daemon.

Usage

When there is no tym instance, run below.

$ tym --daemon

The process will be daemon process. This execution is wrapped as systemd-unit.

$ systemctl --user start tym-daemon.service

However, this will also failed in your working tym instance. To start the daemon process, we need to stop all tym instances including the terminal just you are working on!

So the following may help you.

$ nohup sh -c 'killall tym; sleep 1; systemctl --user start tym-daemon.service; tym' >/dev/null 2>&1 &

sometimes when i try to run an instance, it exits with no error (with a log of just quit).
i see that this is intentional, but this happens with subsequent instances?

The application ID may be the cause.

tym instances unite by application ID such as me.endaaman.tym or me.endaaman.tym_dev. For debugging, the latter me.endaaman.tym_dev is used by specifying $ ./configure --endable-debug. If you are developing on tym and didn't specify --endable-debug option, the tym process that you are working on uses me.endaaman.tym and the newly developing execution will be united into it.

On the other hand., if you feel curious that when the daemon/primary process exists, all secondary tym executions will quit immediately, that is just the specification of tym. If you need logs also on the secondary executions, there is a means of receiving log messages from the primary/daemon process using D-Bus IPC.