Build and first startup
Build rsia, choose a dedicated data file and inspect the supported command entry points.
Build
git clone https://github.com/acosmi/RSIAgent.git
cd RSIAgent
cargo build --release -p rsia
./target/release/rsia --helpgit clone https://github.com/acosmi/RSIAgent.git
cd RSIAgent
cargo build --release -p rsia
./target/release/rsia --helpUse the repository's pinned toolchain, Rust 1.98.1 at this documentation review. A source build is not platform installer acceptance.
Select data and identity
The default file is rsia.sqlite3 in the current directory. Prefer an explicit dedicated absolute path. Keep one owner and do not start multiple writers against the same runtime data directory.
./target/release/rsia mcp --data /absolute/path/to/rsia.sqlite3 --namespace personal --actor my-assistant./target/release/rsia mcp --data /absolute/path/to/rsia.sqlite3 --namespace personal --actor my-assistantThis waits for MCP protocol messages on stdin; it is not an interactive chat prompt. Keep logs off protocol stdout.
HTTP startup
./target/release/rsia serve --data /absolute/path/to/rsia.sqlite3 --bind 127.0.0.1:7788 --namespace personal./target/release/rsia serve --data /absolute/path/to/rsia.sqlite3 --bind 127.0.0.1:7788 --namespace personalConfigure the required role credentials in the process environment first; see HTTP and identity. Sensitive routes return 503 without HTTP authentication configuration; this is not anonymous access.
Unsupported assumptions
The current CLI has no --shared or --auth-token option. Management clients read RSIA_MANAGEMENT_TOKEN. Do not copy parameters from another branch or a desktop preview.
Verify protocol initialization, tool discovery and a restricted read before attempting a complete host journey. Running the process does not establish useful improvement.