fence not working under local-dev-server config

[rolandash]

Use fence to sandbox OpenCode in local-dev-server mode,

fence -m --fence-log-file /tmp/fence.log -t local-dev-server -- opencode      

This generates a blank screen and a strange line of characters,

and hangs here forever.
The log file generated is empty.

Are there additional setup needed to make it work?

My environment setup
MacOS (26.3)
OpenCode 1.14.48

[jy-tan]

Can you try it with the code template:

fence -m --fence-log-file /tmp/fence.log -t code -- opencode

The local-dev-server template is a very narrow subset of the code template, and doesn't have app-specific permissions to state/cache paths like ~/.opencode/** etc. You may also find Docs > Agents > Popular CLI coding agents helpful.

[rolandash]

thanks for the reply @jy-tan

the 'code' template can launch opencode properly. However it is "allow default" scheme and I think may be bit "loosy" for my application.

So is there anyway to make these CLIs to work with "deny default" scheme?