stilldeskKnow the path.
Know the limits.
StillDesk is a collection of concrete app interfaces. A configured interface, an exported client configuration, a fixture test, and a live application test are different kinds of evidence.
Chrome and Edge
Both browsers are exercised through the extension and Native Messaging. Each passed 37 live local-fixture workflow checks, including uploads, downloads with SHA-256 verification, and before/after checks of the Windows foreground window and cursor position.
| Available path | Explicit boundary |
|---|---|
| Background tabs, navigation, DOM snapshots, form controls, scroll, DOM drag, waits | DOM-derived snapshots are not the complete browser accessibility tree. |
| File inputs, hidden inputs, multiple files, iframe and shadow-root inputs | 32 MiB per upload; no native file chooser or directory upload. |
| Browser downloads and verified local file readback | Browser Downloads settings choose the destination; an explicit permitted root controls local readback and hashing. |
| Visible active-tab screenshot | An inactive tab is not activated to take its picture. |
Programmatic events do not grant real user activation. Browser-native dialogs and operations requiring trusted human gestures remain unsupported. Real websites can impose additional constraints. No remote debugging port, CDP client, or extension debugger permission is used.
The adapter inherits the repaired local history/search pagination, single-message context, compact output, account-session diagnosis and verified cached-attachment reads. It distinguishes a hidden or tray client from a logged-out client.
Native writes for the current client and uncached network attachment retrieval are still under investigation. The public background-only package does not ship the old foreground/UIA sender. A preview is a plan, not a sent message or a delivery receipt.
Account-scoped local QQNT history, stable cursors and local image access. The public adapter includes improved read ergonomics and reports source freshness. It is a read-only personal-client adapter, not a QQ bot API presented as control over a personal account.
Feishu / Lark
Fixed operations through the official native CLI and service APIs. Real access depends on your app's scopes and account authorization. Unconfigured credentials are reported as unconfigured. Mutation paths use previews and explicit authorization; release tests do not send real messages.
Tencent Meeting
Separate local-session/transcription and cloud-recording interfaces. The cloud interface is limited to authorized read operations. Local capture starts only after an explicit request targeting the selected meeting process, and does not happen during setup or status checks. Model files, account sessions and vendor binaries are not bundled.
Agent clients and plugins
MCP stdio and the CLI form the common interface. Client examples are generated and checked against each documented format. Claude Code compatibility is static only and no Claude Code executable is used. DeepSeek as a model provider is separate from an independently specified harness; model choice alone does not imply MCP host support.
ChatGPT desktop plugin examples and the remote MCP transport are integration artifacts. The project does not imply marketplace approval, a public HTTPS deployment, or live validation in every client.
Look at the evidence
Browser results, platform fixture checks and integration-source provenance are committed alongside the code. The repository capability matrix is the detailed source of truth for the current release.