Daemon
In Unix-like systems, a process that runs in the background over a long period and is not bound to any controlling terminal. It is typically started at system boot or at the beginning of a user session and exists independently of a terminal. Typical examples include sshd, cron, services managed by systemd, and LSP servers. Its persistent nature provides continuously available services but also entails ongoing resource consumption and behavior that is difficult to observe directly.
Core Facts
Timeline (last 90 days)
The architecture of resident agents typically requires a separate daemon, a credential vault, and an event bus, and these components themselves also constitute a new attack surface.
A live process does not mean work is normal: a stuck daemon retains its PID, memory and state, so you should test on the actual work path rather than merely checking the process table.
A daemon is a type of process in Unix-like systems that runs in the background for a long time and is not directly bound to any controlling terminal, typically launched at system startup or when a user session begins, after which it detaches from the terminal and exists independently, continuing to survive even if the terminal window that launched it is closed.
On Unix/Linux, daemons often exist as .service units or launchd plists, and their status can be checked via systemctl or launchctl.
Because the daemon runs for a long time, the attack window of the self-update mechanism far exceeds that of a one-off executed command.
A daemon is a process that detaches from terminal control and runs in the background for a long time, typically registered and started at system boot via an init system (such as systemd, launchd) or a service manager.
A daemon's lifecycle is independent of the user session, unlike ordinary command-line programs that exit once execution finishes.
BrowserSkill places a local daemon process between the AI and the browser, through which all operations pass and leave traceable, auditable records.
All Facts (8)
A daemon is a type of process in Unix-like systems that runs in the background for a long time and is not directly bound to any controlling terminal, typically launched at system startup or when a user session begins, after which it detaches from the terminal and exists independently, continuing to survive even if the terminal window that launched it is closed.
65%UnverifiedThe architecture of resident agents typically requires a separate daemon, a credential vault, and an event bus, and these components themselves also constitute a new attack surface.
50%UnverifiedA live process does not mean work is normal: a stuck daemon retains its PID, memory and state, so you should test on the actual work path rather than merely checking the process table.
50%UnverifiedOn Unix/Linux, daemons often exist as .service units or launchd plists, and their status can be checked via systemctl or launchctl.
50%UnverifiedBecause the daemon runs for a long time, the attack window of the self-update mechanism far exceeds that of a one-off executed command.
50%UnverifiedA daemon is a process that detaches from terminal control and runs in the background for a long time, typically registered and started at system boot via an init system (such as systemd, launchd) or a service manager.
50%UnverifiedA daemon's lifecycle is independent of the user session, unlike ordinary command-line programs that exit once execution finishes.
50%UnverifiedBrowserSkill places a local daemon process between the AI and the browser, through which all operations pass and leave traceable, auditable records.
50%