Finkkle Spaces

Features reference

A practical guide to the capabilities that make a Spaces conversation useful from first prompt to finished work.

Feature reference · Finkkle documentation

Conversations and context

Each conversation maintains its own message history. The active tab is the primary context; linked tabs are explicit references. Start a new conversation when the goal or audience changes.

Modes

Chat supports everyday questions and drafting. Research emphasizes sources and comparison. Study structures explanations for retention. Code and data focuses on implementation, calculations, tables, and clearly stated assumptions.

Files and media

Use the attachment control to add supported files, images, or links. Reference an attachment by name in your prompt and say whether Spaces should summarize, extract, transform, compare, or use it as background.

Artifacts

Long-form or structured results can be presented as artifacts for easier reading and iteration. Treat an artifact as a working output: review it, request changes, and keep the accepted version with the conversation.

Voice input

Use the microphone control to dictate a prompt. Review the transcription before sending when accuracy matters. Voice input follows the same conversation and context rules as typed input.

Plugins and tools

The plugins surface lets you discover and enable available integrations. A plugin may provide a focused action or source. Review what it can access and the result it returns before relying on it in a final deliverable.

Automations

Automations turn a plain-language instruction into a scheduled or manually triggered task. Configure its schedule, model and reasoning preferences, external-action policy, and run history. Use observe-only or draft-only policies when you want review before changes outside Spaces.

Models and response controls

Where the model selector is available, choose the model that fits the task. Give the model a concise objective, relevant context, and explicit constraints; then iterate rather than packing unrelated jobs into one prompt.

Boundaries and safe use

• Do not include passwords, private keys, or secrets in prompts or attachments.
• Verify high-impact decisions, facts, and generated code.
• Use explicit context instead of assuming Spaces can see an entire app, website, or file system.
• Review automation permissions and run history regularly.