About the project
Inspiration
Troubleshooting conversations often contain the answer, but the handoff still loses the exact reproduction path, expected behavior, and environment. Dev Handoff turns explicit labels in a conversation into a reviewable issue draft so a human can triage without copying everything by hand.
What it does
The processor reads records with id, text, timestamp, and source. It recognizes explicit English labels for problem, reproduction, expected, actual, environment, and blockers, keeps the first value per field, preserves bounded evidence quotes, and reports a useful missing-fields checklist. It exports Markdown; it never files a GitHub issue.
This package includes a SYNTHETIC DEMO fixture and a local interactive viewer. The fixture is imported local data and is not validated Bee hardware evidence. Live mode is implemented, but a LIVE BEE read has not been validated in this environment; no live validation claim is made.
How it was built
The core algorithm is the original Python standard-library implementation: deterministic regular-expression label extraction, inert text handling, JSON input, and Markdown output. A standalone run.py loads either --fixture sample.json or an explicitly requested --live Bee CLI read. The browser demo ports the same label-boundary algorithm to vanilla JavaScript and runs entirely from local files with no requests or remote dependencies.
What I learned
A useful handoff is not just a summary: preserving evidence IDs, timestamps, and source context lets a reviewer check each extracted field. A missing-field checklist is more honest and more actionable than filling gaps with guesses. Keeping live lookup separate from fixtures also makes provenance visible.
Challenges
Natural speech does not always use stable labels, ASR can change punctuation or words, and one conversation may mix multiple issues. The parser therefore stays conservative: it only extracts explicit labels, never executes transcript text, and keeps one first-seen value per field. The offline UI also had to make its synthetic status unmistakable instead of resembling a live capture.
Limitations
This is a heuristic English parser, not semantic understanding. It can miss unlabeled or unusual phrasing, has limited punctuation/multiline coverage, processes one batch as one handoff, and does not deduplicate or verify facts. ASR evidence is unverified. It has no authentication, privacy redaction, issue API, backend, persistence, or automatic filing. --live requires the user's own authorized Bee CLI session and a supported credential store; it fails clearly rather than silently falling back to the fixture. A LIVE BEE NOT VALIDATED claim remains in force until a consented real-device run is independently completed.
Log in or sign up for Devpost to join the conversation.