The Outpost is operated in the application window on its machine. No command line is needed for day-to-day work.
No window, no console, nothing at all? → Outpost does not start
| Tab | What it is for |
|---|
| Status | Overall health and current action required |
| Shares | Folders, databases, MCP servers and HTTP APIs |
| Activity | Trends for load, storage, files, requests and data transfer |
| Connection | Pairing, automatic reconnect and network checks |
| Protocol | Durable operational events and current technical output |
| System | Diagnostics, support, version, hardware and storage locations |
| Settings | Startup, compute budget, storage limit, language and appearance |
The status bar at the bottom of the window remains visible everywhere. It shows whether the local Outpost service is running and whether meinGPT is connected. Start and Stop affect the service; they do not change the pairing or the stored shares.
The top row answers exactly four questions:
- Outpost: Is the local service running?
- Connection: Is meinGPT connected?
- Search: Is at least one document usable?
- Background preparation: Is everything current, is work running, or are there exceptions?
Below that are only the global facts: searchable documents, searches during the past 24 hours, latest successful folder update and Outpost storage used. CPU, memory and individual index stages belong under Activity or in the folder's Processing view.
A vector index still being built is not an outage. Once text has been extracted, the pool can already be used; the keyword and vector indexes improve search afterward. Individual skipped files appear as exceptions without making an otherwise usable pool look failed.
The list contains folders and, when the services preview is enabled, databases, MCP servers and HTTP APIs. Each row only shows the state that is useful for comparison: name or path, usability, size, exceptions and latest update. Read everything again starts another pass over every folder.
A folder has four detail areas:
| Area | Contents |
|---|
| Processing | File discovery, text extraction or OCR, keyword index and vector index with progress and exceptions |
| Source documents | File explorer, subfolders, file types and the concrete reason for files that could not be processed |
| Data access | Data retrieval by meinGPT and local access to the source folder |
| Folder activity | Searches, synchronizations, configuration changes and failed operations for this folder |
There are three search targets under Processing:
| Search target | Result |
|---|
| Automatic (recommended) | The Outpost adds the vector index when it fits the configured storage limit and the system disk reserve. |
| Keyword search (full-text index) | Fast, relevance-ranked word search without a vector index. |
| Meaning search (vector index) | Keyword search plus semantic search; uses additional time and storage. |
Two decisions remain separate under Data access:
- Data retrieval: extracted text only, or original files too.
- Source folder: read-only, or read and write. Read and write lets meinGPT create, edit, move, and recoverably delete text files in the released folder — details under A folder on this machine.
The release level is set on the Outpost and reported to meinGPT as a device setting. In meinGPT you then decide whether to adopt the reported folder as a data source and who may use it.
Services have Status, Data access and Activity. Status keeps four proofs separate: locally stored target, local check, report to meinGPT and reachability from meinGPT.
For PostgreSQL, schema inspection and SELECT are always allowed. INSERT, UPDATE and DELETE are enabled individually and checked against the effective database privileges. For MCP and HTTP, the Outpost fixes the local target; tool or API permissions are managed in meinGPT, and cloud requests cannot redirect the target to another address.
The global tab offers one-hour, 24-hour and seven-day ranges. It shows:
- requests per second and errors
- CPU and memory use
- Outpost storage used and configured storage limit
- observed, searchable and semantically indexed files
- inbound and outbound data transfer
- every share with a direct link to its details
This tab answers “How is operation developing?”. Individual operations and failure times live under Protocol.
Pairing connects this machine to the meinGPT organization. Replace pairing creates a new key; Disconnect pairing separates the machine after confirmation.
The Outpost reconnects automatically while it remains paired and the service is running. When a problem occurs, the connection check reports DNS, TCP, TLS, proxy, meinGPT reachability and system clock separately. A failed row names the cause and the next action.
The Outpost opens the connection outbound. There is no inbound port and no firewall rule for incoming traffic.
Events contains the durable history of searches, synchronizations, service requests and configuration changes. A failed event links to the affected folder or service and shows the recorded cause there.
Live output shows the current technical stream. For a support request, the sanitized diagnostics export under System is a better handoff than copied raw logs.
Support and recovery stay visible under System:
- support request and sanitized diagnostics export
- version, update state and signed installation
- operating system, CPU and memory
- metadata recovery when it is actually required
- configuration file and data folder
- compact support data with a copy action
The diagnostics export contains no document content and no secrets.
| Symptom | Next action |
|---|
| Connected, but nothing is found | Check the status bar and start the Outpost service. Then open Shares. |
| Folder is ready locally but not usable in meinGPT | Adopt the reported folder as a data source in meinGPT and grant access. |
| A file is missing | Open folder → Source documents for the file, reason and possible action. |
| Synchronization failed | Open folder → Folder activity and read the concrete error. |
| Vector index is still running | Use the pool through text or keyword search; follow progress under Processing. |
| Connection drops repeatedly | Open Connection and run the network check. |
| Support needs technical details | Open System, export diagnostics and copy the support data. |