It's currently possible to build things and then visit the build output directory to run software, but it's not really possible to do much else. There used to be functionality to do this, but because Bramble expects to allow people to trivially run software pulled from remote repositories it feels important to create an opinionated default way to run things that won't allow these programs to do dangerous things to the host machine.
Some open questions:
Is this something that is defined in the build files?
Is it a command you can run?
Are you allowed to run things outside of a project?
If we run things in a sandbox how do you define what folders the program should have access to?
It's currently possible to build things and then visit the build output directory to run software, but it's not really possible to do much else. There used to be functionality to do this, but because Bramble expects to allow people to trivially run software pulled from remote repositories it feels important to create an opinionated default way to run things that won't allow these programs to do dangerous things to the host machine.
Some open questions: