AgenticSeek only have agent communication for planning task but it isn't really communication. Planning task are simply a json list of task and how they related with each other. During execution output from each agents will be saved and "added" to the prompt of the following agents that depends on the information from the previous agent. Really dead simple but work quite well.
For memory management, we store message as an array of {"role": "user", "content":...}. Where we take a more innovative approach if how we process message before adding to the history: We remove the <think>..reasoning..</think> pattern to keep only useful informations in the context (we don't really need the reasoning that was done on previous task for the current task). We also have memory summarization that is used when loading a previous session.
No it can't because we check the bash the AI try to execute against a list of pattern for dangerous command. Also all commands are executed within a folder specified in the configuration file, so that you can choose which files it has access to. However, we currently have no containerization meaning that code execution unlike bash could be harmful. I do think about improving the safety by running all code/commands within a docker and then having some kind of file transfer upon user validation once a task is done.