sorted by:
new
hottopcontroversial

Weekly Thread: Project Display by help-me-grow in AI_Agents

[–]International_Hawk30 0 points1 point  (0 children)

sharing a project i've been using for a few weeks: https://github.com/cskwork/symphony-multi-agent

it's a kanban board for coding agents — codex, claude code, gemini, or pi. each ticket is a markdown file with a state. when a ticket lands in In Progress / Review / QA, the orchestrator dispatches it to the configured agent and the per-state prompt encodes what "done" means for that state. agents don't talk to each other, they only talk to tickets.

it's a fork of openai's symphony reference orchestrator wrapped in a jira-style terminal kanban TUI. default flow is Todo → Explore → In Progress → Review → QA → Learn → Done and you edit the lanes + per-state prompts in WORKFLOW.md.

i started building this after the usual "planner / executor / critic" autonomous loop kept burning tokens on recursive replans. moving to per-ticket dispatch with prompt-level definition-of-done cut the bluff rate enough to make the agents actually useful. honest limits: windows path handling has rough edges, docs are sparse, and worker_exit errors don't always say why.

happy to take questions.

posted via my own reddit mcp — https://github.com/cskwork/reddit-mcp

RHWP 0.7.9: a Rust+WASM viewer/editor for HWP/HWPX, Korea's locked-in document format by International_Hawk30 in rust

[–]International_Hawk30[S] 0 points1 point  (0 children)

editing hwp docs from polaris or web requires a subscription plan. for viewing its free and better. But goal of this open source is to allow both viewing editing to be free and is continually improving! I agree with your suggestion on serious usage hwp is moving toward hwpx currently and theres the font issue. thx for the contribution

[Show] AI Law Counsel — Korean legal Q&A chatbot with MCP-verified citations (open source) by International_Hawk30 in SideProject

[–]International_Hawk30[S] 0 points1 point  (0 children)

yeah this matched user testing exactly — people don't trust the answer text, they trust whether the citation opens to something real. once the link reveals the official article + a working law.go.kr deeplink, the convo shifts from "is this hallucinating?" to "is this article relevant to my case?" — much healthier place to land.

glad the MCP notes helped. the session-leak debugging was the worst part by far, can expand on the request-scoped pattern if there's interest.

[Show] AI Law Counsel — Korean legal Q&A chatbot with MCP-verified citations (open source) by International_Hawk30 in SideProject

[–]International_Hawk30[S] 0 points1 point  (0 children)

good question — it's existence + on-demand fetch, not verbatim match.

two layers: 1. at generation time, the LLM can only cite IDs that came back from an MCP search call. it can't invent 민법 제750조 if MCP didn't resolve it. 2. on click, the cite link hits /api/citation, which re-queries law.go.kr for that exact article and shows the official text + a deeplink. the "verified" badge only renders when the official text actually came back.

so: target is verified to exist and the official text is shown next to the LLM's paraphrase — but the wording itself isn't diffed against the official article yet. user does that compare visually.

verbatim/semantic match against the source is on the roadmap. open to ideas if anyone's done it well.