[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f1xhlx3820qct0":3},{"code":4,"message":5,"data":6,"timestamp":34},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":16,"summary_md":17,"topic":18,"github_topics":21,"license":31,"homepage":31,"updated_at":32,"history":33},"Haryy985\u002Fyunkun-console-preview",18,"云鲲自动化渗透控制台：功能介绍、使用流程、新增与优化、界面预览。当前仓库仅含文章与截图，暂无产品源码。","Go",135,8,13,10,[],"A preview console that keeps authorized pentest tasks, agent traces, HTTP evidence and findings in one workspace.","Treat this as a product preview and design document, not a tool you can install and rely on today. The repository's own description states it currently contains only articles and screenshots with no product source, while the README points to a `source\u002F` directory and Windows offline releases, so the two accounts of what is shipped conflict and should be checked before planning around it.\n\n## The problem\n\nIn an authorized pentest, the hard part after the scan is often reconstructing what happened: which tool the agent called, what request produced a finding, and whether a colleague can reproduce the result. Teams end up stitching together chat logs, proxy history, notes and a separate report. The stated workflow here puts the conversation, execution trace, HTTP request\u002Fresponse records and finding report in one console, so the report is assembled from linked evidence rather than retyped afterward. The promised result is a task view showing what is running, where a conclusion came from, and what someone else would need to repeat it.\n\n## What's different\n\nThe distinctive mechanism is a human-gated loop around an agent. The agent may submit proposals to add or correct knowledge, but those enter retrieval only after a person approves them. Findings are meant to carry real step and traffic evidence plus manual quality review, and reports are organized around the vulnerability description, URL, HTTP request packet and key response instead of old curl repro commands. Automation speeds collection and drafting while authorization boundaries and conclusions stay with the operator.\n\nThe console also bundles RAG knowledge bases, proxy discovery and validation via FOFA\u002FQuake, tool\u002FMCP\u002FSkills configuration, token accounting and flow auditing beside the agent chat. That breadth is the main trade-off: fewer vantages point, but many moving parts to configure and keep running, and the author admits the full chain of real models, proxies and complete tasks has not been accepted end to end. The supplied material is release notes and screenshots, so the quality of that gated loop cannot be judged.\n\n## Who should try it\n\nA reasonable fit is a security team running authorized engagements in an isolated lab that wants to evaluate whether an evidence-centric agent workspace matches its reporting process. It is a poor fit for anyone needing a working tool now: there is no public demo or signed installer, Linux and macOS have no tested conclusion in this version, and the repository description says source is absent while the README links to one. A solo learner curious about approval-gated knowledge and traffic evidence is the other plausible audience.\n\n## Requirements and limitations\n\nThe documented default is Windows x64. The [offline package and update manual](https:\u002F\u002Fgithub.com\u002FHaryy985\u002Fyunkun-console-preview\u002Fblob\u002Fmain\u002Fdocs\u002FOFFLINE_UPDATE.md) describe a bundle with the console and PostgreSQL runtime, so that path needs no Go, Node.js, npm, Docker or network downloads; the [project instructions](https:\u002F\u002Fgithub.com\u002FHaryy985\u002Fyunkun-console-preview) also list an online build path in the source directory. Upgrades use backup-and-migration rather than replacing the running program, so stop the old install and back up the private database, config and Skills first. The [acceptance record](https:\u002F\u002Fgithub.com\u002FHaryy985\u002Fyunkun-console-preview\u002Fblob\u002Fmain\u002Fdocs\u002FRELEASE_1.0.3_ACCEPTANCE.md) recommends a dedicated low-privilege environment because the native agent uses the account's local permissions with no container isolation.\n\nScanned PDFs, encrypted documents and older Office formats are outside general parsing guarantees; Linux and macOS have no tested conclusion here; and the author says real-model and proxy chains, external database migration and clean-system installs still need environment-specific checks. The preview also limits permitted use to reading, studying and local isolated verification.\n\n## HotRepo's take\n\nOne dated observation places this repository at #24 on the 2026-10-25 NEW-REPOSITORY board (新项目榜, not an overall Trending rank) with 135 total stars. There is insufficient comparable daily-board history to judge persistence. Given the ten-day age and the conflict over whether source and releases exist, verify repository contents and release integrity first; the acceptance record covers tests and a simulated upgrade, not the real-model task chain.",{"slug":19,"name":20},"security","Security & Privacy",[22,23,24,25,26,27,28,29,30],"aiagent","aisecurity","cybersecurity","network-security","penetration-testing","penetration-testing-tools","red-team","security-automation","vulnerability-assessment",null,"2026-10-25T03:18:35Z",[],1792915240]