Add dsh-qingagent under Domain specific - #4
Merged
Conversation
Writing bridge to the open-source QingAgent client: the agent drafts and revises documents on a typeset rice-paper panel, every edit staged for review before it lands. Install command copied verbatim from the project's own README (the github: spec it recommends). Requires the QingAgent desktop client running locally, stated in the description. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DKSCvE7UUcTdzbesdFW9Xw
Contributor
|
Merged — thanks @void2anything. Verified the I kept your note that the QingAgent desktop client has to be running. That's a real prerequisite and hiding it would waste a reader's time. Maintainer edit: star figure 2 → 4 to match the live count. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change is this?
Checklist (for new entries)
with [name](repo-url) by [author](author-url).then a factual description, star count, license and**[tag]**— left unchecked on the**[tag]**part only: CONTRIBUTING says "No tags" and no live entry carries one, so the entry has none; everything else in the format is followedAnything else maintainers should know?
github:spec (the repo commits its builtlib/, so this path needs no build step). The same README warns thatdsh-qingagent@lateston npm can resolve to an older version during pnpm's default release observation window, so I did not list the npm spec.**[tag]**, so I followed CONTRIBUTING's format (no tag), and Domain specific is not currently alphabetized, so I appended at the end. Happy to move it wherever you prefer.node .github/scripts/build-readme-sections.mjs README.mdon my branch parses the entry (77 entries, Domain specific at 7); I reverted the regenerated regions to keep the diff to the one entry. I also left the header count, badge, and generated data files for your CI. Star count in the entry is the real current figure (2).Generated with Claude Code
https://claude.ai/code/session_01DKSCvE7UUcTdzbesdFW9Xw