issues Search Results · repo:jonmagic/scripts language:Ruby
Filter by
25 results
(83 ms)25 results
injonmagic/scripts (press backspace or delete to remove)📌 Problem Statement
Currently, github-conversations-research-agent treats different conversation types inconsistently:
1. Semantic search results ✅ Include summaries and relevance scores from Qdrant ...
jonmagic
- Opened 10 days ago
- #42
Background
We need a two-step quality gate: macro evaluation then micro fact checking.
Tasks
8.1 EvaluatorNode
- [ ] Insert between FinalReportNode and stdout.
- [ ] Prompt (fast model): rubric ...
jonmagic
- Opened 12 days ago
- #36
Dynamic Depth 10-Minute Time Cap
Background
We need smarter stopping logic: finish early if answer is “complete” or when wall clock hits 10 minutes.
Tasks
- [ ] On flow.run start set shared[:start_time] ...
jonmagic
- Opened 12 days ago
- #35
Background
Conversations often reference other GitHub threads worth pulling in.
Tasks
- [ ] After each successful fetch in RetrieverNode, scan body comments for URLs matching: https://github.com/ ...
jonmagic
- 1
- Opened 14 days ago
- #34
Background
When Planner chooses semantic but qualifiers exist (e.g., repo:), we should translate them into Qdrant payload filter
blocks.
Tasks
- [ ] Add helper build_semantic_query(user_query):
...
jonmagic
- 1
- Opened 14 days ago
- #33
Background
Planner now selects a tool, but Retriever still only calls semantic search.
Tasks
- [ ] Rename existing DeepResearchNode → RetrieverNode.
- [ ] In exec, switch on @shared[:next_search][:tool]: ...
jonmagic
- 1
- Opened 14 days ago
- #32
Background
We need a node that decides whether to run semantic search, keyword search, or both.
Tasks
- [ ] Create PlannerNode (in github-conversations-research-agent):
- Input: shared[:current_query] ...
jonmagic
- Opened 14 days ago
- #31
Background
We often pair GPT-4.1 (1M ctx) with o1 (128k).
Nodes that chew lots of tokens need the bigger window; lighter reasoning can use the smaller, faster model.
Tasks
- [ ] Update option parsing ...
jonmagic
- Opened 14 days ago
- #29
Background
bin/github-conversations-research-agent and friends currently use puts for all output.
We need INFO-level progress by default and DEBUG-level detail behind --verbose.
Tasks
- [ ] Add require ...
jonmagic
- Opened 14 days ago
- #27
🎯 Implementation Plan: bin/github-conversations-research-agent
This document explains, step by step, how to build a multi-turn research agent CLI script. You should be able to follow
it without guessing ...
jonmagic
- Opened 16 days ago
- #25

Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Press the /
key to activate the search input again and adjust your query.
Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Restrict your search to the title by using the in:title qualifier.