Skip to content

[0.9.1] Background intelligence and AI Now unavailable #279

@abn

Description

@abn

Describe the bug
When using Google as the LLM provider all operations fail, including timeline addition as well as AI Now. The following diagnostic was received.

AI Now request failure diagnostics
message: StreamReader.readline() got an unexpected keyword argument 'max_line_length'

StreamReader.readline() got an unexpected keyword argument 'max_line_length'
source: provider
code: (unknown)
app_log_path: (unknown)
agent_log_path: /home/abn/.config/co.nowledge.mem.desktop/kimi_home/.kimi/logs/kimi.log
agent_log_summary: (none)
details: StreamReader.readline() got an unexpected keyword argument 'max_line_length'
stderr_tail:
(none)
app_log_tail:
(none)
agent_log_excerpt:
(none)
agent_log_tail:
2026-04-30 12:06:06.431 | INFO     | kimi_cli.soul.toolset:_connect_server:259 - Connected MCP server: nowledge-mem
2026-04-30 12:06:06.431 | INFO     | kimi_cli.soul.toolset:_connect_server:259 - Connected MCP server: nowledge-mem
2026-04-30 12:06:25.557 | INFO     | __main__:prompt:962 - Received prompt request for session: f69e2f0d-bc24-4e0f-8d2a-a47f04d0ceed
...

To Reproduce
Steps to reproduce the behavior:

  1. Configure Google Gemini as LLM provider.
  2. Add timeline entry or start a new AI Now task.

Expected behavior
Timeline entity is processed or AI Now responds.

Screenshots

Image Image

Additional context
Installed via rpm nowledge-mem-0.9.1-1.x86_64.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions