Better flow for the ssh-agent

[leiserfg]

In order to work "seamlessly" as an ssh-agent I think this things should be done:
It should be possible to start the rbw-agent in an un-demonized mode, so one can run it in a user systemd service.
The ssh-agent interface should call unlock itself lazily (request credentials in ssh triggers it if locked).

[leiserfg]

Sorry If I sound like a PM. I really like rbw and wanna use it as an ssh agent 😄

[lotrfan]

The same thought crossed my mind, and it turns out there's already a --no-daemonize flag; using Home Manager:

  systemd.user.services.rbw-agent = {
    Unit = {
      Description = "Unofficial Bitwarden CLI Agent (Default Profile)";
      Documentation = "man:rbw-agent(1)";
    };
    Service = {
      Type = "exec";
      ExecStart = "${pkgs.rbw}/bin/rbw-agent --no-daemonize";
      Restart = "on-failure";
    };
    Install = {
      WantedBy = [ "graphical-session.target" ];
    };
  };

You can pass RBW_PROFILE=name to use a different profile - each profile uses a separate agent.

rbw/src/bin/rbw-agent/main.rs

Lines 69 to 71 in 77464d4

	let no_daemonize = std::env::args()
	.nth(1)
	.is_some_and(|arg| arg == "--no-daemonize");

[leiserfg]

I didn't know about that flag, I guess I can make a PR to home-manager to have the service there.