Running agency with -d causes agents not to startup

[maetl]

agency -d behaves differently to agency when starting agents—agents never make it past the initial startup phase.

Steps to reproduce:

1. Startup Smith using agency -d
2. Start an agent with smithctl start {AgentName}
3. The logs for that agent don’t go past Transition [state]: :checked -> :starting
4. Running smithctl list -la shows the agent as starting with pid 0 and a date of 1970/01/01 10:00:00
5. The starting agent remains in that state indefinitely and doesn’t time out.

When starting an agent with agency running in the foreground, this problem doesn’t happen.

[filterfish]

The agent tries to search the directory hierarchy from the current working directory for a config file but given that the agent has it's current working directory to / it can't find it.