ayjnt-tools

To give a Cloudflare agent local file system access, you use a skill that bridges workerd and Bun host processes. This allows you to define permissioned tools for file interaction and command execution while keeping the agent deployable as a standard worker.

To enforce security for agent tools executing local shell commands, you use side-effect declarations and path confinement validation. This permissioned execution model prevents unauthorized system access by strictly controlling read, write, and exec operations.

Yes, you can run agent tools on a Bun host process while keeping core logic in workerd. This dual-runtime support allows you to seamlessly define tools that operate in either environment, facilitating local host-side capabilities integration.

The best way to add per-route model tools without compromising deployment is by using a framework that bridges workerd and Bun processes. This approach maintains security through side-effect controls and path confinement, ensuring your worker remains standard and deployable.

To define a host tool in the ayjnt framework, you create a tools.host.ts file in your agent route directory. You then define your function using the hostTool wrapper to enable local execution.

Yes, integrating local host capabilities requires special side-effect declarations. You must enforce strict side-effect controls for read, write, and exec operations to prevent unauthorized system access and ensure secure tool invocation.