issues Search Results · language:Dune language:JavaScript language:Python language:JavaScript linked:pr language:JavaScript
Filter by
4.5M results
Goal
Make bare aippocampus config default to a compact foreground decision card, with the full knob inventory available only
through explicit detail/operator modes.
User-Visible Problem
The JSON config ...
Goal
Strengthen the foreground-action contract so any action containing command_template is explicitly marked template_only:
true, and fix current self-note/control surfaces that omit it.
User-Visible ...
Goal
Bring aippocampus update --json and aippocampus update apply --json missing-argument recovery onto the same
foreground-action-v1 contract as the rest of update/status.
User-Visible Problem
When ...
Goal
Make aippocampus update status --json and --agent-json default to a compact setup/readiness card, with full readiness
dossiers behind operator/detail output.
User-Visible Problem
update status ...
Goal
Keep default aippocampus agent recall ... --json focused on route choices and the next source-reopen action, while
moving projection/audit metadata behind detail/operator output.
User-Visible Problem ...
Goal
Make successful why-recall / why-not-recall --json output a compact explanation-and-next-action card by default, with
full surface reports and observatory detail behind an explicit detail/operator ...
Goal
Make aippocampus agent deepen --json without a selected handle return a compact needs-input / recovery card, not an
operator-detail envelope.
User-Visible Problem
When a foreground agent calls ...
Description
In the mini-compare-chart variant, icons rendered inside slot[name= icons ] within .top-section stack vertically instead
of displaying in a horizontal row. The base Shadow DOM CSS (merch-card.css.js:244) ...
Problem
AIppocampus benchmark fixtures currently report strong route/search behavior, but live agent-facing recall/deepen can
still feel poor in ordinary use. In a 2026-06-20 local agent session, explicit ...
benchmark
bug
Improvement
Enable the built-in prefer-object-spread rule in the shared config.
It flags building a new object with Object.assign({}, ...) and steers it to object spread instead:
// flagged
const merged ...

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.