Bring documents in, make them usable, and keep them organized.
Documents Hub owns source files from upload through extraction, indexing, organization, and sharing. Its folders, tags, and document smart collections organize source material here.
01
File intake and extraction
Upload supported source files and extract searchable text or structured content for workspace use.
PDF and common Office files: DOCX, PPTX, XLSX
Text, Markdown, CSV, TSV, JSON, XML, YAML, and notebooks
Image OCR for supported PNG, JPEG, TIFF, WEBP, BMP, and GIF files
Ask questions over sources you are allowed to use.
Query is AverQel’s retrieval-first answer experience. It searches permitted document context, streams the response, and keeps source evidence visible with the answer.
01
Scoped retrieval
Choose relevant sources and refine retrieval without crossing the access boundary of your workspace.
Filter by selected documents or an accessible Qel Connect space
Narrow by source type, date, and extraction coverage
Workspace permissions remain in force during retrieval
Qel Connect spaces are explicit membership areas for project documents and collaboration. They are separate from Documents Hub’s document smart collections.
Experimental beta01
Membership and source access
Keep project access scoped to the people and material approved for that Qel Connect space.
Qel Connect owners manage invites and membership
Join requests require owner approval
Shared sources are governed by Qel Connect and document access
DeepSpace is the durable AI work area. Its conversations, agent runs, Memory, working Library, artifacts, sandbox, and schedules all belong to this product area.
01
Agent conversations and runs
Work through longer tasks in DeepSpace conversations with run state that can survive interruptions.
Pause, resume, steer, retry, or cancel supported runs
Review queued work and approval requests
Attach relevant files to a task where supported
Conversation and run state stays separate from Query history
Choose and manage the models used by workspace features.
Provider configuration is its own shared platform area. Query and DeepSpace use assigned provider roles; provider setup does not itself connect an external app or grant MCP tool access.
01
Provider configuration
Connect supported cloud or local model services using the provider settings available to your workspace.
Configure supported local or hosted provider types and model endpoints
Use supported OAuth or secret-based setup for the selected provider
Secrets are returned in masked form in provider views
Provider availability depends on valid credentials and service health
Connect supported tools with explicit access and action controls.
MCP manages approved server connections and their tools. A catalog entry, supported authorization, connection policy, and any required action approval are part of the flow.
01
Curated marketplace
Discover reviewed catalog entries and inspect the available server and tool information.
Connections start from approved catalog entries
Inspect supported tools and connection requirements
Arbitrary endpoint registration is not part of this release