> ## Documentation Index
> Fetch the complete documentation index at: https://docs.finkkle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Finkkle Spaces Plugins: Overview and How They Work

> Plugins give Spaces focused capabilities — web research, code analysis, terminal execution, and connected services — all inside your conversation.

Plugins are packaged tools that extend what a Finkkle Spaces conversation can do. They add focused capabilities — deep web research, code explanation, spreadsheet generation, terminal execution, or connected service actions — without requiring you to leave the conversation or switch tools.

## What a plugin is

A plugin is a capability with a declared scope: a name, description, category, execution sandbox, and permission boundary. When you install a plugin, Spaces adds it to the set of tools it can consider when planning a response. The model decides when a plugin is relevant; you review what it returns.

Plugins are not separate chatbots. They do not replace the conversation — the model plans, the plugin executes a specific operation, and the result comes back to the same thread where you can review, revise, and continue.

## Plugin lifecycle

<Steps>
  <Step title="Discover">
    Open the **Plugins** screen from the Spaces navigation. Browse featured plugins, explore categories, or search by name or capability.
  </Step>

  <Step title="Inspect">
    Open a plugin detail view to read its purpose, developer, version, execution sandbox type, run count, and rating. Understand what it can access before installing.
  </Step>

  <Step title="Install">
    Click **Install**. The plugin becomes available in all your conversations. For connected service plugins (GitHub, Notion, Slack, etc.), you will be prompted to authorize access via OAuth.
  </Step>

  <Step title="Use">
    Describe what you want in a conversation. Mention the plugin by name for deterministic routing, or let Spaces select it automatically based on your request. Provide the required inputs — files, links, account connections.
  </Step>

  <Step title="Review">
    Inspect the returned artifact, citations, file, message draft, or action log. Ask Spaces to revise the result before sharing or acting on it.
  </Step>

  <Step title="Manage">
    Use the plugin action menu (⋯) to uninstall, view terms, or disable automatic updates. Removing a plugin does not delete conversation records that referenced it.
  </Step>
</Steps>

## How plugin execution works

Every plugin invocation follows the same pattern:

1. **Input collection** — Spaces identifies the required text, files, URLs, settings, or credentials for the operation
2. **Permission check** — read, write, send, and account actions are distinguished; a draft stays a draft until you approve it
3. **Isolated execution** — the plugin runs in its declared sandbox (AI Sandbox, Web Browser, Command VM, or Document tool)
4. **Result validation** — output is checked for a usable response, supported format, and actionable errors
5. **Conversation hand-off** — the result and an audit log entry appear in the conversation thread

## Execution sandboxes

| Sandbox           | What runs here                                                     |
| ----------------- | ------------------------------------------------------------------ |
| **AI Sandbox**    | Text and reasoning operations, summaries, classification           |
| **Web Browser**   | JavaScript-rendered pages, DOM reading, web interactions           |
| **Command VM**    | Terminal commands, bash scripts, Python, Node, git                 |
| **Document tool** | File creation and editing — spreadsheets, presentations, documents |

<Warning>
  Installing a plugin makes a capability available — it does not make actions automatic. Always review context, permissions, and the result before an external change takes effect.
</Warning>

## Choosing the right plugin

Choose the narrowest tool that matches the job. For a one-off question, regular Chat is often faster and requires less setup. Add a plugin when you need a specific, repeatable capability that Chat alone cannot handle reliably.