admin/openhuman
1
0
Fork 0
mirror of https://github.com/tinyhumansai/openhuman.git synced 2026-07-27 21:08:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: clarify managed backend defaults (#2426)

Browse Source
This commit is contained in:
g.sunilkumar
2026-05-22 17:52:10 -07:00
committed by GitHub
parent 33dc4ec412
commit 1a852cdc7c
5 changed files with 39 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files
gitbooks/overview/getting-started.md
+4
View File
@@ -35,6 +35,10 @@ The first screen is **"Sign in! Let's Cook"**. Multiple sign-in options are avai
**No permanent lock-in.** Signing in does not grant OpenHuman ongoing access to anything. All third-party access requires explicit OAuth approval per integration in the steps below.
{% endhint %}
{% hint style="warning" %}
**Know what is local and what is managed.** Your Memory Tree database, Markdown vault, workspace config, and local runtime state live on your machine. The default setup still uses OpenHuman-hosted services for sign-in, model routing, managed integration OAuth/tool calls, and web search proxying. Use the custom setup paths if you want to bring your own model, search, or Composio credentials. Some hosted features and real-time integration triggers still require the managed backend.
{% endhint %}
## 3. Run your first request
Once Gmail has been ingested (the first auto-fetch tick happens within twenty minutes), try prompts like: