Exactly, the team designed their own agent architecture tailored to slack and enterprise setting, that is not based on any popular agent architecture like OpenClaw, NanoClaw, IronClaw or any others that I checked against.
Reverse engineering means understanding how a system works internally. So it is reverse engineering of a kind, just very different (and admittedly simpler) than e.g. decompiling execs
Agree, anything that agent has access to is like giving it to malicious user. Especially when agent is exposed to different users that should have different permission levels
I could do the same thing but not publish it, still getting the value of their product without legal concerns. Now, what happens when it becomes even easier thanks to AI improving, and takes few hours instead of few days?
You could certainly do that in private but that doesn't mean it's not 'without legal concerns'. But, not shouting about it and not creating a repo called 'openviktor' would probably be a safer bet.
I certainly think the whole idea of IP ownership as related to software will become very interesting from a legal standpoint in the coming years. Personally I think that, over time, the legal challenges will become pretty overwhelming and a sort of legal bankruptcy will be declared at some point in one direction or another (as in, allowing this to happen or making it extremely easy to bring judgement and punishment, similar to spam laws). However, I would not want to be the first to find out, especially in Europe.