Version: v1.17.0 — 6 minor issues found while evaluating for adoption, filed together to avoid ticket spam. Happy to split any into its own issue/PR, all with repro.
- Internal errors leak to the user.
engram timeline 999999 → …: sql: no rows in result set — stdlib/SQL plumbing surfaced in a user-facing message. Wrap with a friendly error.
- Mixed path separators on Windows.
engram stats prints C:\Users\…\.engram/engram.db — a hardcoded / instead of filepath.Join.
doctor false-positive on intentional --project. A deliberate short alias in a repo whose git remote infers a different name yields a permanent warning, and the suggested remediation is "use --project" — the very thing that triggered it. No mute.- CLI
save without --project stores project=NULL inside a repo. The MCP path auto-detects the project (detectProject); the CLI doesn't — so a CLI save in a repo creates memory invisible to --project <name>. Inconsistent with the MCP path.
- Tool counts disagree across sources. docs say 20,
--help says 19/15, runtime v1.17.0 reports all=22, agent=18, admin=4. Docs/help look stale vs runtime.
projects prune missing from top-level --help. The command works but isn't listed in the overview.
Found while evaluating Engram v1.17.0 for adoption in a multi-agent workflow; reproduced with AI-assisted testing. — Marcelo Escallon
Version: v1.17.0 — 6 minor issues found while evaluating for adoption, filed together to avoid ticket spam. Happy to split any into its own issue/PR, all with repro.
engram timeline 999999→…: sql: no rows in result set— stdlib/SQL plumbing surfaced in a user-facing message. Wrap with a friendly error.engram statsprintsC:\Users\…\.engram/engram.db— a hardcoded/instead offilepath.Join.doctorfalse-positive on intentional--project. A deliberate short alias in a repo whose git remote infers a different name yields a permanent warning, and the suggested remediation is "use--project" — the very thing that triggered it. No mute.savewithout--projectstoresproject=NULLinside a repo. The MCP path auto-detects the project (detectProject); the CLI doesn't — so a CLIsavein a repo creates memory invisible to--project <name>. Inconsistent with the MCP path.--helpsays 19/15, runtime v1.17.0 reports all=22, agent=18, admin=4. Docs/help look stale vs runtime.projects prunemissing from top-level--help. The command works but isn't listed in the overview.Found while evaluating Engram v1.17.0 for adoption in a multi-agent workflow; reproduced with AI-assisted testing. — Marcelo Escallon