Degoog — Documentation

Overview

Degoog can be customised with plugins, themes, search engines, transports, and aliases. Extensions live under data/ and can be installed from Store repositories (git repos you add in Settings → Store).

Default enabled/disabled engines

Search engines have two separate layers of “enabled” state: instance defaults and your browser’s saved selection.

Instance defaults (server-side): on startup, Degoog computes a default enabled/disabled value for every engine. Engines that are marked as disabled by default, or engines that have required settings that are not configured, start out disabled. You can override these defaults by saving a data/default-engines.json file (this is what the Settings → Engines “Save defaults” button writes).
Your selection (client-side): the Engines tab stores your toggles in your browser (IndexedDB). Those saved values take priority over the instance defaults for that browser/profile, so your choice persists even if the server defaults change later.

Example data/default-engines.json:

{
  "google": true,
  "duckduckgo": true,
  "bing": false,
  "engine-my-custom-engine": true
}

When you toggle engines on the Engines tab, the enabled/disabled state is sent along with each search request, so different users (or different browsers) can use different engine sets at the same time.

Where things live

Path	Purpose
`data/plugins/`	Plugins (bang commands, slots, tabs, search bar actions, routes)
`data/themes/`	Themes (CSS and optional HTML overrides)
`data/engines/`	Search engines (web, images, video, etc.)
`data/transports/`	Transports (custom HTTP fetch strategies)
`data/plugin-settings.json`	Extension settings and active theme
`data/aliases.json`	Custom `!alias` → `!command` mappings
`data/repos.json`	Store repos and installed items
`data/store/`	Cloned Store repo data

Quick start

Open Settings → Store.
Add a repo: paste https://github.com/fccview/fccview-degoog-extensions.git and add it.
Browse the Store tab and install a plugin (e.g. Weather) or theme (e.g. Zen).

Official extensions repo: fccview-degoog-extensions. This is automatically added to your instance when you start it for the first time.

Use as your browser's default search engine

Any browser that supports custom search engines can use degoog. Replace https://your-instance with your actual instance URL.

Field	Value
Search URL	`https://your-instance/search?q=%s`
Suggestions URL	`https://your-instance/api/suggest/opensearch?q=%s`

Browsers that support OpenSearch can detect degoog automatically — right-clicking the search bar on your instance will offer to add it.

Extension types

Plugins — Bang commands (!weather London), result slots, search result tabs, search bar actions, API routes, middleware.
Themes — Override CSS and optionally home/search HTML.
Search engines — Custom search backends (web, images, video).
Transports — Custom HTTP fetch strategies (e.g. fetch, curl and whatever you can come up with really).
Store — Add git repos and install extensions from them.
Aliases — Custom !alias → !command mappings.