A desk for your day
Come back to recent notes and ongoing threads. Browse your library, then settle into Reader when it’s time to focus.
Notes for every part of your day
The project brief. The research that changes your mind. The weekend you can’t wait for. Bring your notes, plans, and ideas together in a workspace that fits the way you think.
Write, plan, and connect. Choose what you share.
Project brief / Week 04
Help someone go from an empty workspace to their first useful note. Give them a clear next step, and room to make it their own.
| Next step | Owner | Status |
|---|---|---|
| Map the first session | Maya | Done |
| Test the welcome flow | Alex | In progress |
| Review the findings | Sam | Next up |
Success measure: a first note worth coming back to.
Explore fictional example notes in a Reader-style preview. The Sunday Garden includes an actual product capture.
One example, in detail
The Sunday Garden is the personal side of the picture. Explore actual captures of its tabs, trackers, and tasks—the same tools you can bring to research, meeting notes, and project plans.
Callouts & tabs
Keep the overview, the schedule, and the supporting details together. The same structure works for a project brief or a plan with friends.
Actual product captures from The Sunday Garden example note.
Meet your new editor
Start with a sentence. Add a checklist, tuck details into a foldaway section, or drop in something visual. Your note can become whatever the idea needs.
Little symbols. Lots of meaning.
The person you talked to. The project it belongs to. Where you found it. Tags give a note more than one way to be found, with eight handy prefixes to make each kind clear.
Start with a topic or two. The rest is there when you need it.
From scattered to connected
A useful workspace helps you return to ideas, see them from another angle, and do something with them.
Come back to recent notes and ongoing threads. Browse your library, then settle into Reader when it’s time to focus.
See a project on a board, plans on a calendar, or notes in a gallery. Save a favorite filter so it’s ready next time.
Link related notes, gather a collection, or ask the AI assistant to help explore, summarize, and build on your ideas.
Privacy is a choice you can see
Choose where a note is saved and how far it can be shared. Keep it on one device, connect your own Hub, or use cloud sync when you want it.
Meet your privacy controlsSet who may read a note, including whether outside AI services may receive it.
Keep a library on a computer you control and connect your Entaggle tools to it.
Cloud sync and AI access have different privacy choices. Review a note’s setting before inviting more in.
Right where the idea finds you
Settle into the app, save something from the web, or keep notes beside your work. Entaggle meets you there.
A dedicated space for writing, reading, and connecting your thoughts. Keep working with notes on your device, even offline.
Meet the appSave a page, a passage, or just the part that matters. Add tags and keep the source with your note.
Meet your web clipperKeep your notes close while you build. Search, capture, tag, and read without leaving your editor.
Keep your work connectedFind your setup
Start with what matters to you. Add the apps, storage, and tools you need, and follow the connections. A simple setup is a complete setup, too.
Select a piece to follow its connections.
Your selected tools fit within this boundary. Outside AI is optional and can be added separately.
Swipe or scroll the diagram sideways to explore all three columns.
Where you work
Connect, sync & serve
Store & process
Direct connections · bypass Entaggle services
Arrows show requests, results, and data flows for this view. Optional routes are labeled in the connection list. Cloud AI uses the hosted service; standalone MCP accesses the Cloud note library. The Tunnel Service is only a network bridge.
About this piece
Use the desktop client with a local Hub or a reachable remote Hub. Cloud notes and Cloud AI are optional connections.
The Desktop App and the Hub are separate components. A local Hub and a server Hub are deployments of the same note service.
Entaggle Cloud is the hosted service for notes, sync, and AI. Entaggle Hub is the self-hosted note service; “local Hub” and “server Hub” describe where the same software runs.
| Component | Role and connections |
|---|---|
| Entaggle Web AppNotes in your browser | The browser client can use Entaggle Cloud and one or more Hubs. A Hub can run on this computer, your home server, or another server you control. Using the Web App does not require Cloud note storage. To use Hub notes, allow access from the Web App in your Hub settings. |
| Entaggle Desktop AppNotes on your computer | Use the desktop client with a local Hub or a reachable remote Hub. Cloud notes and Cloud AI are optional connections. The Desktop App and the Hub are separate components. A local Hub and a server Hub are deployments of the same note service. |
| Entaggle Mobile AppNotes on your phone or tablet | Connect the mobile app to Cloud or a Hub on your computer or server. Use the Hub address and token; the Tunnel Service can make a home computer reachable. The Hub and local model run on their host computer, not on the phone. Remote Hub access does not require Cloud Sync. |
| Entaggle Browser ExtensionCapture web content | Save a page or passage to Cloud or a configured Hub. AI tag suggestions use Entaggle Cloud when requested. Saving a clip and requesting AI are separate flows. A write-only Hub token can capture notes without reading the library. |
| Entaggle VS Code ExtensionFiles, Hubs, Cloud & MCP | Work with local note files, one or more Hubs, or Cloud notes. The built-in MCP connection runs locally and accesses the Cloud library. AI tools use your active local note source first, then connected MCP or Entaggle Cloud. No Hub is required for local files. AI tools need a compatible assistant; sharing note context can send it to the assistant’s model. |
| Entaggle CloudHosted notes, sync & AI | The hosted service provides Cloud notes, sync, and AI requests. Requests using your own AI provider key and managed Cloud AI both pass through this service. Using Cloud AI does not automatically store the source note in the Cloud Database. It does send request context through the hosted service. |
| Entaggle HubSelf-hosted personal note server | The same Hub software runs on your computer or a server you control. Each Hub owns its note library and database, and can provide Vault, Mirror, and local text generation. Hub notes are excluded from Cloud Sync. Keeping the Hub reachable and running is necessary for its remote clients. |
| Entaggle Tunnel ServiceRemote access to your Hub | The Hub connects to the Tunnel Service. Its secure address and a Hub access token let phones, browsers, and other clients reach it without changing your router settings. The service is a network bridge, not note storage or synchronization. The relay can read the traffic it forwards. The library stays on the Hub. |
| Entaggle MCP ServerAI tools for your Cloud notes | The standalone MCP server gives assistants access to note tools. It can run on your computer or remotely; both connect to the Cloud note library. Running it locally does not connect it to a Hub. Tool results return to the calling AI client and may reach its model provider. Optional AI-powered search can also send content to an outside provider when configured and permitted. |
| AI clientAssistant connected to your notes | The assistant initiates tool calls to Entaggle MCP Server, then uses the returned note context with its own model. Its model connection is separate from Entaggle’s provider settings. Running MCP on your computer does not mean notes or AI processing stay there. The standalone server accesses the Cloud library. |
| VS Code AIAssistant invoking Entaggle tools | The assistant calls the extension’s registered search/fetch tools. The extension supplies context from its active note provider, local MCP connection, or Entaggle Cloud. Your assistant controls where its model runs. Local files can still leave the computer as tool results. |
| On-device storageSeparate storage for each client | Each app or browser maintains its own local note storage. This node represents those separate stores, not a database shared by all the apps. The per-note “Only this device” permission blocks Hub and AI. Use “My devices and my own AI” for notes intended for a Hub or trusted local runtime. |
| Hub DatabaseNote storage owned by this Hub | The Hub stores its note library in its own database. Each additional Hub has a separate database and separate access tokens. No Cloud Database is involved in Hub Sync. A tunnel only forwards the requests to the Hub. |
| Entaggle DatabaseShared by Cloud and MCP | Entaggle Cloud and the standalone Entaggle MCP Server both use this database for the Cloud note library. MCP connects to it even when running on your computer. Running MCP locally does not switch its note source to a Hub or local files. |
| Realtime Messaging ServiceConfigured note-update delivery | Changes made through Cloud and MCP can be sent to other connected clients. The database remains the source of stored notes. Updates can contain note content, not only notifications. Delivery depends on configuration and connectivity; this is not Hub Sync. |
| Local Note FilesNotes saved on your computer | The VS Code extension reads and edits local note files without a Hub. Notes explicitly chosen for Cloud sync can be uploaded through the extension’s Cloud connection. These files are separate from the Hub Vault and generated Mirror output. Local storage does not itself authorize sending file content to an AI client. |
| VaultEditable note folder ↔ Hub | The Hub synchronizes a note folder in both directions. Outside file edits are watched and indexed back into the Hub. The folder belongs on the Hub host. This is distinct from the VS Code extension’s independent local note files. |
| MirrorHub → generated exports | The Hub writes exports of notes matching a tag pattern to a chosen directory. One-way generated output. Edit source notes; regenerated output can replace file edits. |
| Local AI RuntimeAI running on your hardware | Clients can ask the Hub to use its local AI, or connect directly to local AI on a reachable computer. Processing happens on that computer, including when the client is a phone. Local-only requests must not fall through to outside providers. Choose a connection you trust and review each note’s permissions. |
| AI ProviderAI hosted by an outside provider | Outside model services receive requests through Entaggle Cloud, configured Hub fallback, or the AI client’s own model connection. MCP may separately use a provider for AI-powered search. These routes are distinct. The diagram labels each selected route; no generic MCP-to-chat-model or direct client-to-frontier-model path is assumed. |
Hub MCP status: Direct assistant-to-Hub MCP access is not available yet. Running the standalone MCP Server locally still connects it to the Cloud note library; adding a tunnel does not add MCP access to a Hub.
What this setup means
This is a planning guide. Apply storage destinations, note privacy, and connection settings in the app.
Open EntaggleYour next note starts here
The work that matters. The things you do for fun. A place to think, plan, and make something of both.
Start your first note