BISHENG Files

This release consolidates everything from v2.5 and v2.6.

🧠 1. Linsight Upgraded to Task Mode Linsight has been re-architected and upgraded, adding task planning, sub-agent delegation, a virtual file system, human-in-the-loop (HITL) collaboration, and skill support — for more stable planning, more accurate tool calls, long processes that are less likely to go off track, faster execution, and better results.

1.1 📋 Plans Before It Acts: Task mode breaks your request into a visible to-do list and works it top to bottom, so you always see which step it's on and what's next.

1.2 🤝 Delegates the Deep Digging: Heavier investigation is handed to research sub-agents that work in an isolated context and fold a distilled summary back into the main task.

1.3 💬 Human-in-the-Loop (HITL): When your intent is ambiguous, the task pauses to ask a clarifying question — with interactive options — and resumes automatically once you answer.

1.4 🧩 Skills, On Your Terms: Administrators can create, upload (.md / .zip / .skill), or import skills from GitHub, and enable, disable, or delete them in the console.

1.5 ⏹️ Stop & Resume Across Turns: Halt a running task at any time and continue the same conversation later — subsequent turns can see and build on the files produced earlier.

🔐 2. Enterprise Permission System Upgraded

The permission system is upgraded to a combined RBAC + ReBAC model, letting large organizations model their real structure and share with precision. Full feature details >> https://dataelem.feishu.cn/wiki/BWSMwdc2Ciwif4kfe5HcyGHgn3b#share-QWTRdhvMiofvSex2h81c6IR6nBg

2.1 🌳 Model Your Org as It Really Is: Build a multi-level department tree in the admin console — create, rename, move under a new parent, and delete — with department administrators managing their own department's members and roles, and user groups to gather people from across departments.

2.2 🎚️ Share at Four Relationship Levels: Whether it's a knowledge space, document library, folder and file, workflow or assistant app, tool, dashboard, or channel, permission management lets you grant Owner / Can Manage / Can Edit / Can View to an individual, a department (optionally its whole subtree), or a user group.

2.3 🛡️ Permission Guardrails: A non-super-admin can never grant above the level they hold, every resource always keeps at least one owner, and anyone who gains or loses access is notified in-app. After upgrading from an earlier version, existing role-, group-, and space-member permissions migrate into the new model in one operation.

2.4 🎫 Roles, Menus & Quotas: Policy roles control which feature menus a user sees after login, with three per-role quotas — knowledge-base upload capacity (GB), channels that can be created, and knowledge-space subscriptions.

⚡ 3. A Smarter Workstation with Inline Citations In everyday chat, the model now judges when to call a tool (including knowledge-base retrieval) and uses citation badges to mark the source of every grounded answer.

3.1 🤖 Agentic Tool Calling: With one or more tools or knowledge bases enabled, the model decides whether and when to call them and can chain several calls within a single answer. Administrators can customize which tools are available in daily mode from the admin console.

3.2 🔎 Inline Source Citations: Across daily mode, workflows, and assistants, answers carry numbered citation badges — blue for knowledge sources, purple for web search. Click one to preview the source (PDFs box-highlight the exact cited passage), or open the References panel under an answer to see every source it drew on.

3.3 📤 Export & Reuse Conversations: Pick the answers you want and export them as Word (.docx), PDF, Markdown (.md), or TXT, or send them straight into a knowledge space — down to a specific folder.

📚 4. A More Powerful Knowledge Space

4.1 🔗 Use Knowledge Spaces in Apps: Assistants and workflow nodes (Knowledge Q&A, Knowledge Retrieval, and Assistant) can now retrieve from knowledge spaces, not just document knowledge bases. An optional switch filters retrieval and citations by the running user's file-level permissions, so a file a user can't see never reaches the answer.

4.2 🌐 Import Web Pages & Audio/Video: Paste a URL to fetch a page's main content as a knowledge file, or upload audio/video to have it transcribed to timestamped text and ingested. Transcription runs through a speech model configured in the console's system model settings.

4.3 🗂️ Document Version Management: Keep every revision of a document under one entry, with similarity hints when you upload a near-duplicate; knowledge-space search always returns only the primary version, and switching the primary takes effect with no re-indexing. Version management is off by default and can be enabled in the system YAML configuration.

4.4 🛡️ Content Security Review: Tenant administrators can turn on sensitive-word screening — independently for knowledge-space uploads and subscribed channel articles — using built-in or custom word lists. A flagged upload is blocked from the index; a flagged channel article is marked "under review" and hidden from ordinary users.

4.5 ✂️ Stronger Ingestion: Subscribed channel content can be filed into a chosen knowledge space automatically; a new "chunk by hierarchy" strategy segments Markdown and Word documents along their own heading outline; and PPT parsing has been tuned to resolve the image and text loss that could occur during PPT parsing.

🇨🇳 5. Ready for Domestic Deployment (Dameng DM8)

To meet the localization requirements of government and enterprise customers, BiSheng now runs its entire metadata layer on Dameng DM8, alongside MySQL with functionality on par.

5.1 🗄️ DM8 as a First-Class Database: Point the database connection at Dameng to deploy the whole platform on DM8 — passwords stay encrypted and the platform handles the dialect differences transparently.

5.2 🔁 Migration & Full-Stack Localization: A MySQL-to-Dameng migration tool moves existing data across and schema upgrades run automatically; in the commercial edition, the Java gateway and the OpenFGA permission engine also support Dameng for end-to-end localized deployment.

✨ 6. More Improvements

• Conversation history on shared app pages: Both login-required and no-login application pages keep a conversation list so users can resume an earlier chat — server-side per account when signed in, browser-local per device when not.
• Mobile-optimized Workstation: Core pages adapt to phones on their own, with no separate app.
• Workflow input-node file strategies: The input node accepts multiple files and lets builders choose how each file is used downstream.