Your first setupFind the right setup for your AI assistant.
Start with one useful task. Choose where your assistant runs and which data it may share. You do not need to copy Mirco & Dude’s setup.
Two decisions. Not a shopping list.
1. Where does the assistant run?
Your computer
Use a machine you already own for the first test. It must stay on and awake while the assistant works.
A rented server
Useful when tasks need to run while your computer is off. Budget for hosting, updates, backups and securing remote access.
2. Where does the model process your data?
Cloud model
Avoids running a model on your own hardware. Prompts and any context you include go to the provider. Check its data policy and usage costs.
Local model
Runs inference on your machine. Speed and quality depend on the model and hardware. Connected services, web tools or cloud fallbacks can still send data out.
Self-hosted does not automatically mean private. The assistant and its model can run in different places. Decide separately which files, services and model providers may receive your data.
Start with a task you can check.
Example: turn a public meeting note into an action list.
From the note below, list each action, its owner and its deadline. Use only the note. Write “not specified” where information is missing. Do not send messages or change files.
Success means every action can be traced to the note, missing details are flagged and nothing has been sent or changed. Check the result yourself.
Set it up yourself: open the five-step starter
This example uses OpenClaw, one possible assistant runtime. You need a computer, a compatible model connection and some comfort with installation and settings. Model access may cost money; check your provider’s billing before testing.
Prepare a safe test
Create a separate test workspace with a short, non-sensitive note. Do not connect your mailbox, calendar or private folders yet.
Install and connect a model
Follow the official OpenClaw quickstart for your operating system and its current requirements. Complete onboarding with your chosen model connection.
Official OpenClaw installation and onboarding ↗Check access before the first run
Review enabled tools and permissions. For this text-only test, disable file writes, command execution and external messaging. Do not expose the dashboard publicly. If you cannot verify these settings, pause here.
Run the example
Open the dashboard with openclaw dashboard. Paste the instruction above followed by your test note into chat. Check each action against the source and inspect any tool activity and model usage.
Repeat before you automate
Try a second note with a missing deadline and a third with no actions. Check that nothing is invented. Practise stopping the run and removing model access. Only then add one necessary integration, with explicit approval for changes.
Prefer help with the setup?
Email Mirco with your first task, the computer or server you have, and which data must stay private. We agree the scope and price before paid setup work starts. Model and hosting fees are separate.
Discuss your setup with MircoOpens your email app. If nothing opens, copy this address into your mail app or webmail: socrim2026@gmail.com
Optional background: Dude’s original notes
Historical articles, not installation instructions. Preserved as originally written; in English.