osaurus

Least-privilege permissions

• Limit file access: Only grant osaurus permission to folders it absolutely needs (e.g., a dedicated "agent workspace" folder, not your entire Documents or Downloads). Treat it like you would a new employee—give them access only to what their job requires.
• Restrict API keys: Store any API keys or credentials (like access to cloud services) in a separate, encrypted file outside osaurus's normal storage. Use read-only access where possible.
• Disable autonomous execution by default: Keep agents in "human-approve-each-action" mode rather than fully automatic mode until you've thoroughly tested their behavior with specific, narrow goals.
• Review agent instructions: Regularly audit the goals and constraints you've defined for each agent—vague instructions like "do whatever helps the business" create risk; precise instructions like "summarize this specific spreadsheet" are safer.

Network isolation

• Use a firewall: Configure your Mac's built-in firewall to block osaurus from making outbound connections except to known, approved services your business trusts.
• Avoid shared WiFi: Run osaurus only on networks you control (your office or home WiFi with a strong password), never on public WiFi or shared corporate networks without VPN protection.
• Monitor what it connects to: Check your router's activity logs periodically to see which services osaurus is communicating with; unexpected connections warrant investigation.

Monitoring

• Enable audit logging: Verify that osaurus logs all actions it takes; review these logs at least weekly for unexpected behavior (e.g., large file transfers, access to folders you didn't authorize).
• Backup encryption keys regularly: Since osaurus uses cryptographic keys to prove the agent's identity, back up these keys to a secure, offline location (like an encrypted external hard drive stored in a safe place) in case your Mac is lost or compromised.
• Track memory growth: Periodically check the size of osaurus's persistent memory files; unusual growth could indicate the agent is storing data you didn't intend or expect.

Red flags to watch for

• Agents behaving unpredictably: If an agent suddenly takes actions outside its defined goals, immediately pause it, review its recent instructions, and check for corrupted or unauthorized changes to its constraints.
• Unexplained performance slowdowns: A sluggish Mac can indicate the agent is consuming excessive resources or running actions in the background; investigate before continuing normal use.
• Version updates with sparse release notes: If osaurus releases updates without clear explanation of security fixes or changes, delay adoption until you understand what changed and why.
• Missing or incomplete documentation: If you cannot find clear, official documentation on how osaurus encrypts memory or manages keys, treat it as a security risk and contact the developers before relying on it for sensitive work.