meinKontextDocs
Navigation & search

Plugins

Context explorer

Read context files, review drafts and download files.

The context explorer presents the context you can access as files. Read existing text files, edit supported content, review changes and download files. Enabling the plugin does not grant additional access to any content.

Workspaces in the browser

Use the page header to select one of your personal Workspaces. All content shows everything you may access, including content without a workspace assignment. An empty workspace stays empty. Manage assignments under Workspaces. The selection also applies when navigating, searching and exporting within the plugin. Save unfinished changes before switching workspaces; switching closes the previous editors.

A workspace says where content lives and where an agent works; a bucket says who else may use it. The workspace selection in the browser is not a grant: it widens neither access rights nor MCP credentials. More about workspaces.

Open the explorer and find files

  1. Enable Context explorer under Plugins. This requires your organization's plugin administration rights.
  2. Open Context explorer from the navigation.
  3. Expand a folder on the left and choose a file. Find files searches names and paths within the selected area.

Large folders show 100 entries per page. Use Previous and Next below the folder entries to browse further; search can find files across all pages.

Source displays the saved text. Preview renders text as Markdown; source is usually more useful for structured files such as JSON. Binary files can be downloaded but cannot be edited here. Folders contain skills, context objects, wikis, facts and accessible plugin records.

Within a wiki, open Files to use the same view, for example at /account/wikis/<wiki>?view=files. The explorer plugin does not need to be enabled for this wiki view. It remains limited to the selected wiki and your current access.

What you can edit

ContentBehavior
Your context objects and wiki filesEdit existing text files with write access; publishing also requires publish access.
Shared context objects and wiki filesRead and download; this view does not let you edit someone else's content.
Current facts under memory/Edit the body and allowed metadata; saving applies immediately.
Plugin records under plugins/Read and download only, even when you can edit them in their owning plugin.
Binary attachmentsDownload only.

A contact created with the plugin builder may appear as record.json. Change its status in the contacts view using the intended workflow. Editing its file in the explorer cannot replace that workflow or its permission checks. Installing a plugin or using a public plugin definition does not expose other users' private records.

Save a draft, then publish separately

For context objects and wiki files, saving and publishing are separate steps:

  1. Edit Source and select Save draft. The published version (stable) remains unchanged. Ctrl+Enter or Cmd+Enter also saves.
  2. Select Review publication. Save any unsaved edits first.
  3. Review All changes in this object. This covers the whole object version, including other file changes already saved in its draft.
  4. Select Publish this version when the displayed version is correct.

Unsaved means the text has not been saved yet. Draft marks saved changes that have not been published. Missing edit or publication controls mean you lack the required rights or that the source is read only. A disabled explorer still allows reading; saving and publishing are blocked.

Facts are saved immediately

Files under memory/ contain a fact's body and YAML metadata. You can edit the body, description, type and origin (origin). Identity, timestamps, history and links remain protected.

The button here is Save: changes become current immediately and the previous version remains in history. There is no separate publication step. Review your changes before saving. Do not put credentials in these files; use the Secrets plugin for those.

When someone has changed the file meanwhile

The explorer does not silently overwrite a newer version. On a revision conflict, your entered text remains in the form. Keep a copy, reload the current version for comparison and apply your changes deliberately. There is no automatic merge.

Other refusals can result from invalid content, protected metadata or revoked access. Check the feedback and your current access before saving again. Downloading a file or enabling the plugin again does not replace missing write permission.

Download a file or export a folder

Download file downloads the saved version of the opened file, including a saved draft. Unsaved text in the form is not included.

Export folder creates a ZIP archive. For context objects and wikis, it contains published files, not unpublished drafts. Facts and readable plugin records are included at their current versions. Paths and file contents are preserved. Protected secret values are excluded; use the Secrets plugin's separate encrypted export for those.

Downloads check access and versions again. A changed version or revoked access can interrupt an export. Reload the view and check the current state before exporting again.

The explorer cannot create, rename, move or delete files. It does not set up local file synchronization or add MCP tools. Use the relevant wiki, context or plugin feature for changes that belong to those workflows.

Your organization's storage limits still apply.