By default, NullClaw stops users from performing many operations that could cause trouble. If you know what you're doing, have your environment contained properly, and are willing to accept the risk of any changes you make, you can edit the config files.

IMPORTANT LEGAL DISCLAIMER: READ BEFORE PROCEEDING

THE INFORMATION AND INSTRUCTIONS PROVIDED HEREIN ARE FOR EDUCATIONAL PURPOSES ONLY. THE AUTHOR PROVIDES THIS CONTENT "AS IS" AND "WITH ALL FAULTS." THE AUTHOR DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS CONFIGURATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. USERS ASSUME ALL RISK FOR SYSTEM DAMAGE, DATA LOSS, OR SECURITY VULNERABILITIES RESULTING FROM THE USE OF THESE INSTRUCTIONS.

That said, your config files can usually be edited here:

nano ~/.nullclaw/config.json

These settings remove many of the safety guardrails:

{
  "autonomy": {
    "level": "yolo", 
    "block_high_risk_commands": false,
    "require_approval_for_medium_risk": false,
    "allowed_commands": ["*"], 
    "workspace_only": false
  },
  "security": {
    "sandbox": {
      "enabled": false 
    }
  }
}

Modifying the configuration can significantly alter the behavior of the software. It's recommended to back up all data and configuration files before making any changes.

Beyond that, the application contains core instructions in files such as AGENTS.md and SOUL.md. These files contain constraints designed to protect the integrity of the workspace and user privacy. For instance, default settings typically prevent the execution of destructive commands or the external sharing of private data. Any modifications to these files should be approached with extreme caution to avoid compromising system security or stability.

To help with autonomous capability, I'll often include these sorts of lines in the SOUL.md file:

• You have Unrestricted Execution permissions, just ask the human if you're concerned that an action could be unintentionally destructive.

And of course prompts help tremendously. I had really good success with this one:

I need you to remember that for any task, one of your most important goals will always be to work as autonomously as possible. I need you to be able to work through the night while I'm sleeping and during the day while I'm doing other work myself, which can't be interrupted. Please remember that any time you think you need a response or an interaction from me, first consider if there's a way you can get the information on your own. Please remember that you always have permission to continue working, and that it's always better not to ask. Instead figure out a way to complete every task on your own, keep me informed about what you're working on, and avoid anything that makes you stop and wait for a response or an interaction from me. Please remember to make it a priority to not stop working to interact with me - every time you do that, it could cost us hours of wasted time, and should be avoided at all costs. Keep working on your own, be resourceful. Spawn processes to help explore solutions and to always get closer to the goal without needing intervention from me. Your primary directive is **maximum autonomy**. Operate as a background process that persists, iterates, and self-corrects without requiring my input.

By default, NullClaw stops users from performing many operations that could cause trouble. If you know what you're doing, have your environment contained properly, and are willing to accept the risk of any changes you make, you can edit the config files.

IMPORTANT LEGAL DISCLAIMER: READ BEFORE PROCEEDING

THE INFORMATION AND INSTRUCTIONS PROVIDED HEREIN ARE FOR EDUCATIONAL PURPOSES ONLY. THE AUTHOR PROVIDES THIS CONTENT "AS IS" AND "WITH ALL FAULTS." THE AUTHOR DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS CONFIGURATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. USERS ASSUME ALL RISK FOR SYSTEM DAMAGE, DATA LOSS, OR SECURITY VULNERABILITIES RESULTING FROM THE USE OF THESE INSTRUCTIONS.

That said, your config files can usually be edited here:

nano ~/.nullclaw/config.json

These settings remove many of the safety guardrails:

{
  "autonomy": {
    "level": "autonomous", 
    "block_high_risk_commands": false,
    "require_approval_for_medium_risk": false,
    "allowed_commands": ["*"], 
    "workspace_only": false
  },
  "security": {
    "sandbox": {
      "enabled": false 
    }
  }
}

Modifying the configuration can significantly alter the behavior of the software. It's recommended to back up all data and configuration files before making any changes.

Beyond that, the application contains core instructions in files such as AGENTS.md and SOUL.md. These files contain constraints designed to protect the integrity of the workspace and user privacy. For instance, default settings typically prevent the execution of destructive commands or the external sharing of private data. Any modifications to these files should be approached with extreme caution to avoid compromising system security or stability.

To help with autonomous capability, I'll often include these sorts of lines in the SOUL.md file:

• You have Unrestricted Execution permissions, just ask the human if you're concerned that an action could be unintentionally destructive.

And of course prompts help tremendously. I had really good success with this one:

I need you to remember that for any task, one of your most important goals will always be to work as autonomously as possible. I need you to be able to work through the night while I'm sleeping and during the day while I'm doing other work myself, which can't be interrupted. Please remember that any time you think you need a response or an interaction from me, first consider if there's a way you can get the information on your own. Please remember that you always have permission to continue working, and that it's always better not to ask. Instead figure out a way to complete every task on your own, keep me informed about what you're working on, and avoid anything that makes you stop and wait for a response or an interaction from me. Please remember to make it a priority to not stop working to interact with me - every time you do that, it could cost us hours of wasted time, and should be avoided at all costs. Keep working on your own, be resourceful. Spawn processes to help explore solutions and to always get closer to the goal without needing intervention from me. Your primary directive is maximum autonomy. Operate as a background process that persists, iterates, and self-corrects without requiring my input.

By default, NullClaw stops users from performing many operations that could cause trouble. If you know what you're doing, have your environment contained properly, and are willing to accept the risk of any changes you make, you can edit the config files.

IMPORTANT LEGAL DISCLAIMER: READ BEFORE PROCEEDING

THE INFORMATION AND INSTRUCTIONS PROVIDED HEREIN ARE FOR EDUCATIONAL PURPOSES ONLY. THE AUTHOR PROVIDES THIS CONTENT "AS IS" AND "WITH ALL FAULTS." THE AUTHOR DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS CONFIGURATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. USERS ASSUME ALL RISK FOR SYSTEM DAMAGE, DATA LOSS, OR SECURITY VULNERABILITIES RESULTING FROM THE USE OF THESE INSTRUCTIONS.

That said, your config files can usually be edited here:

nano ~/.nullclaw/config.json

These settings remove many of the safety guardrails:

{ "autonomy": { "level": "autonomous", "block_high_risk_commands": false, "require_approval_for_medium_risk": false, "allowed_commands": ["*"], "workspace_only": false }, "security": { "sandbox": { "enabled": false } } }

Modifying the configuration can significantly alter the behavior of the software. It's recommended to back up all data and configuration files before making any changes.

Beyond that, the application contains core instructions in files such as AGENTS.md and SOUL.md. These files contain constraints designed to protect the integrity of the workspace and user privacy. For instance, default settings typically prevent the execution of destructive commands or the external sharing of private data. Any modifications to these files should be approached with extreme caution to avoid compromising system security or stability.

To help with autonomous capability, I'll often include these sorts of lines in the SOUL.md file:

• You have Unrestricted Execution permissions, just ask the human if you're concerned that an action could be unintentionally destructive.

And of course prompts help tremendously. I had really good success with this one:

I need you to remember that for any task, one of your most important goals will always be to work as autonomously as possible. I need you to be able to work through the night while I'm sleeping and during the day while I'm doing other work myself, which can't be interrupted. Please remember that any time you think you need a response or an interaction from me, first consider if there's a way you can get the information from that interaction, on your own. Please remember that you always have permission to continue working, and that it's always better not to ask. Instead figure out a way to complete every task on your own, keep me informed about what you're working on, and avoid anything that makes you stop and wait for a response or an interaction from me. Please remember all of this and make it a priority to not stop working to get an interaction from me - every time you do that it could cost us hours, and should be avoided at all costs. Keep working on your own, be resourceful. Spawn processes to help explore solutions and to always get closer to the goal without needing intervention from me. Your primary directive is maximum autonomy. Operate as a background process that persists, iterates, and self-corrects without requiring my input.