Jamailar/beav-deepseek-harness
Beav Creator for Xiaohongshu/RED, social-media AI operations, research, copywriting, images and video in DeepSeek Harness|小红书与社媒AI运营
Listed
1
Tools
Bundle verified
What it does
Connects DSH to local Beav for Xiaohongshu (RED/RedNote) and social-media AI operations: topic research, knowledge, copywriting, image, audio, and short-video workflows with approval and artifact tracking.
Best for
- Xiaohongshu, RED, or RedNote creators producing research-backed posts, covers, audio, and short videos.
- Social-media teams managing durable multi-step projects, tasks, approvals, knowledge, and verified artifacts.
- DSH users who already run local Beav and want its creator workflows exposed through native tools, jobs, commands, and UI contributions.
Not ideal for
- Setups without Beav 2.7.4 or later; the proprietary Beav application and services are not included with the connector.
- Remote Beav deployments; the connector accepts only loopback HTTP endpoints.
- Workflows requiring the connector to auto-approve paid or destructive operations.
- Users seeking a self-contained, fully open-source media engine rather than an MIT connector to proprietary Beav components.
README
Beav Creator
Beav Creator brings Xiaohongshu (RED/RedNote), social-media operations, and creator AI workflows into DeepSeek Harness. Use it for topic and trend research, knowledge management, copywriting, cover and post images, audio, short video, and durable multi-step content production. It exposes Beav workspaces, projects, tasks, approvals, and verified artifacts through Cordis services, Harness tools, background jobs, slash commands, session events, and Web client contributions. It does not use MCP.
Install
Requirements:
- Beav 2.7.4 or later
- DeepSeek Harness
0.1.0-rc.6 - Node.js 22 or later
Install into a Harness profile:
dsh plugin --profile web add beav-creator-dsh
Start that profile, open Settings → Plugins → Beav Creator, and select Connect Beav. Harness opens beav://connect/authorize; Beav starts if needed and shows the requested permissions. After you approve in Beav, the connector completes a five-minute, single-use PKCE exchange and stores the resulting credential under BEAV_CREATOR_TOKEN. No token is copied through the clipboard, URL, browser client, chat, session event, or tool result.
If Beav is not running, an operation that needs it opens beav://open once and performs a bounded health retry. You can override the local endpoint or credential reference in the profile patch:
- update:
id: beav
config:
endpoint: http://127.0.0.1:41700
tokenRef: BEAV_CREATOR_TOKEN
autoLaunch: on-demand
requestTimeoutMs: 30000
Only loopback HTTP endpoints are accepted.
Use
- Ask naturally: “Use Beav to research a Xiaohongshu topic and turn the latest knowledge in my launch workspace into a post, cover images, and a 60-second video.”
- Type
@beavto select a stable workspace or project reference. - Use
/beav connect,/beav status,/beav open,/beav workspaces,/beav new,/beav import, or/beav savefor direct actions without a model turn. - Long-running work appears as a native Harness job and a replayable Beav task card.
- Completion is accepted only after Beav reports durable artifact read-back verification and each returned artifact can be read back through the Creator Gateway.
Beav retains ownership of AI orchestration, knowledge access, media generation, approvals, billing, persistence, and artifact verification. The connector cannot auto-approve paid or destructive actions.
Trust and privacy
This package runs as trusted local Host code. Pairing exposes only a local approval/status surface before authorization; creator operations still require a revocable client credential. Deep links contain a random request ID and PKCE challenge, never a token or verifier. The connector connects only to Beav on loopback, requests bounded summaries, and never transfers raw media bytes through model tool parameters. The connector source is public so the community can audit the integration. The Beav desktop application, creator runtime, knowledge engine, media pipeline, and commercial services remain proprietary and are not included in this repository or npm package.
This is a community plugin and is not an official DeepSeek product or endorsement.
Development
Clone the official Harness checkout at the pinned compatibility revision beside this repository:
git clone https://github.com/deepseek-ai/deepseek-harness.git ../deepseek-harness
git -C ../deepseek-harness checkout 47f943859bef60e4160492346772ded9b24f765a
pnpm -C ../deepseek-harness install
pnpm -C ../deepseek-harness run build:lib
pnpm install
pnpm check
The published tarball contains prebuilt lib/ files and treats every Harness runtime package as a peer dependency. Users do not run a build or prepare script during plugin installation.
License
MIT. This license applies to the connector only, not to the Beav application or services.
Frequently Asked QuestionsFAQ
Use the verified command dsh plugin --profile default add github:Jamailar/beav-deepseek-harness in a DSH-enabled shell. The command resolves the public package metadata and keeps the plugin attached to the catalog identity shown on this page.
Compatibility follows the bundle and profile status shown above. If a profile is not detected, keep the plugin disabled there and check the repository documentation before enabling it in production.
The GitHub link and activity metadata are the source of truth for releases and maintenance. Revisit this page after a new release to confirm the catalog has observed the latest version.