what it is

eugene treats a Pi like a tiny operator you can leave behind. Boot it, hand it a scope, and it cycles through host-discovery, service fingerprinting, low-hanging credentials, persisting everything to a local SQLite so you can resume after a reboot or replay the run.

The agent loop is rig-core; the tools are whatever Kali already ships.

Warning — this is genuinely autonomous. eugene has very little in the way of guardrails. It decides its own next action and executes against live networks and infrastructure without asking. The only hard blocks are shell-injection patterns and Pi-destructive commands; the entire offensive surface is unrestricted, so it can and will do unpredictable things once it’s running. Only point it at networks you are explicitly authorised to attack, and expect to babysit it.

architecture

Eugene uses a planner/executor split. The orchestrator breaks work into parallel tasks, and specialist executor agents run each one independently via tokio + semaphore-bounded concurrency. Everything is tracked in SQLite with FTS5 full-text search.

control

You can control eugene from Telegram, the CLI, or let it run on a cron schedule. Every run, task, and finding is persisted locally. The TUI dashboard gives you a full-screen ratatui view with progress gauge, findings table, and activity log.