黑洞智能体BLACK HOLE AGENTS
Docs

Feature Differences

V2 adjusted the data structure and multiple feature entry points. Before upgrading, review the items that require reconfiguration; for specific steps, see Upgrade from V1 to V2.

V2 Migration Changes

ScenarioV2 HandlingNotes
First-time migration from V1You can install V2 directly from V1.9.13No intermediate V2 release is required.
Standard V2 upgradeUpgrade directly and continue using current V2 dataDo not click Re-migrate.
Re-migrate from V1Select Re-migrate in Settings → DataCurrent V2 data will be permanently deleted. This is only for cases where previous migration failed or data was missed.

Data Handling

Handling MethodData ScopeActions After Upgrade
Automatic MigrationSettings, model services and models, assistants and groups, sessions and messages, Agent and sessions, MCP, knowledge bases and valid indexes, files, drawing, translation, notes, prompts, usage recordsSpot-check that common items open correctly.
Requires ReviewAnthropic credentials, default web search service, Agent tool permissions and knowledge base bindings, prompt order, failed knowledge base items, custom CSS, sidebar favorites, missing filesRe-verify according to the table below.
Not InheritedAgent scheduled task history, legacy sitemap expansion results, some temporary image references, current note open state, configurations for removed featuresRecreate if needed.

Key Differences

FeatureV1V2Actions After Upgrade
Assistants and PromptsIndependent assistant library; quick phrases can be associated with assistantsAssistants are managed in Chat and Agent; quick phrases are merged into global promptsCheck assistant groups and prompt order.
AgentSome configurations and workspaces follow the session; old authorizations can auto-approve toolsIdentity, memory, and main configurations belong to the Agent; workspace is fixed after session creation; tools may request re-authorizationCheck models, workspaces, tools, and permissions.
Agent Knowledge BaseKnowledge tools may access the global knowledge baseOnly accesses explicitly bound knowledge basesRe-verify knowledge base bindings for each Agent.
Knowledge Base RetrievalCan manually select retrieval mode and sitemap sourceUses BM25 when no embedding model is present; uses hybrid retrieval when an embedding model is present; sitemaps are treated as regular URLsCheck embedding and reranking models; rebuild failed sources.
Web SearchService can be selected in assistant or input area; includes local search, RAG compression, and subscription blacklistConfigure keyword search and URL reading separately in Settings → Web Search; related legacy options removedRe-select the two default services and check credentials.
MCPAdded services and third-party discovery market coexistAdded services continue to migrate; legacy third-party discovery market is no longer providedCheck service status; add new services from the current market or via JSON.
Model ServicesAnthropic can save OAuth credentialsAnthropic OAuth is not migrated; AWS Bedrock region is retained; new services are disabled by defaultRe-enter API Key for Anthropic and enable services as needed.
FilesFile copies have weak reference relationships with business objectsManaged files are managed by reference; managed copies are cleaned up with a delay after the last reference is deletedPlace long-term retained files in Files or export them; user original files will not be deleted.
Drawing, Mini App, and SidebarParameters and entry points are in legacy areasDrawing parameters moved to the prompt toolbar; Mini App is in the top tab bar; sidebar favorites resetFamiliarize yourself with new entry points and reset favorites.
Custom CSSV1 selectors take effect directlyContent is retained, but disabled by default after migrationAdapt to V2 selectors before enabling.
Code CLICan select iFlowiFlow is replaced by QoderSwitch to Qoder if relevant workflows are needed.

Developer Compatibility

What are the changes to API and external integrations?
  • The model identifier in API Gateway has changed from provider::model to provider:model.
  • Knowledge API returned entries use V2 fields.
  • MCP-over-HTTP endpoints have been removed; this does not affect in-app MCP.
  • SSE startup failures may directly return standard HTTP errors; clients must handle both HTTP and SSE error paths.
  • Scheduled task interface parameters have changed; historical run records are not migrated.

References

On this page