Last Development Day progress

2026-10-27 Last development day

Versions: 0.109.1 → 0.110.1

5 commits on this day.

Summary

Geo. remember can now find the places among the entities it extracts and store their coordinates (off by default). The rest of the day was a package move and docs: the timeseries package, the gligabao_int paths in the docs, the roadmap and the geo documentation. The geo release needs a new database.

Highlights

• Geo (0.110.0): after a text is stored, remember asks an LLM (new detect_geo stage) which entities are places, asks a geo resolver for their coordinates, and stores them in the new table gb_entity_geo (latitude, longitude, kind, country, region, bounding box, ...). The response has a new geo list. The stage never fails the call, and entities that already have geo data are not looked up again.
• Geo is off by default, because it costs one more LLM call per text and sends place names to the geocoder. Turn it on with geo = true or serve --geo (OpenStreetMap Nominatim), or supply your own resolver with ServeOptions.GeoResolver. New package internal/geo. See docs/geo.md; query does not use geo yet (on the roadmap).
• Roadmap (0.109.3): OpenAI is listed as a planned main reasoning provider for remember and query (today it is used for embeddings only).

Breaking changes

• Geo schema (0.110.0): gb_remember_runs has the columns of the new resolve_geo stage, and the knowledge evals set the reasoning of detect_geo to none. No migration: recreate the database.

Other changes

• The timeseries endpoints moved from internal/api/timeseries to internal/timeseries; no change in behaviour or API (0.109.1).
• Docs: README and docs/hooks.md point at the new gligabao_int paths (0.109.2).
• Docs: geo trajectory steps, the geo step in docs/remember.md, and the geo table and structs in docs/listings/ (0.110.1).

Releases