Changelog

Changelog

Notable changes to logcat.ai : new supported formats, new capabilities, and behavior that affects how you use the platform. Newest first.

2.2.0 (2026-07-20)

Breaking: investigation steps in search results now carry a smaller, stable set of fields.

  • What changed. A step used to include internal working data from how the investigation ran. Those fields were never part of what a step means to you, and every one of them was something we had to keep unchanged forever. A step now reports what it examined and what it found: step_number, step_title, step_title_key, key_findings, citations, duration_ms, confidence, next_action, and the fields that describe the shape of the investigation when it splits into parallel threads and merges again (is_fork, is_synthesis, synthesis_kind, branch_id, branch_label, branch_status, parent_step_number, subset_label, is_planner_step).
  • What you need to change. If you read chunks_found, search_query, detailed_findings, reasoning, web_search_*, gerrit_*, external_*, library_search_*, source_discovery_result, fetch_url_*, inspected_*, next_step_title, confidence_note, effective_max_steps, unanswered_questions, dismissed_questions, or subset_files off a step, those fields are gone. The findings themselves are unchanged: key_findings and citations still carry what the step concluded and what it relied on. This applies to search results wherever they appear, including shared and printed reports.
  • Why. The answer is the product. How we arrived at it changes as the investigation improves, and publishing it made every internal adjustment a change to your integration.

2.1.0 (2026-07-15)

Breaking: the structured and unstructured file types are retired. Both are now log.

  • file_type is log for text logs. The two old values never described the file: they recorded whether logcat.ai could parse a log into columns. That is a property of what we managed to read, not of what you uploaded, so it now travels as its own field instead of masquerading as a type. Every remaining value names a real format or container: bugreport, logcat, dmesg, log, config, perfetto, pcap, ramdump, bundle.
  • What you need to change. If you filter GET /api/v1/files by file_type=structured or file_type=unstructured, use file_type=log. Those two values are now rejected with a 400 rather than silently returning nothing. If you send entity_type on a search or WebSocket frame, send log. Existing files were converted, so nothing needs re-uploading.
  • has_field_grammar tells you what the old split was trying to. Each file reports whether it was parsed into columns, so you can tell a column-filterable log from a plain-text one directly instead of inferring it from a type name.

2.0.0 (2026-07-12)

logcat.ai now analyzes binary captures and memory dumps as queryable data, and every analyzed file gets a dashboard.

  • Kernel ramdump analysis. Upload a Qualcomm dump archive and get post-mortem forensics on a device that crashed hard: reset reason, NoC bus faults, DCC hardware registers, running tasks and CPUs, loaded drivers. Upload a matching vmlinux to the new References library and the analysis also recovers the kernel log, the userspace logcat, and the on-screen framebuffer from memory. See Kernel ramdumps & References.
  • Network captures and Perfetto traces. .pcap / .pcapng, btsnoop Bluetooth HCI logs, SQLite snapshots, and Perfetto traces are decoded at upload and analyzed as structured data, so Quick Search and Deep Research query the records directly and can answer with exact counts, flows, and slices. See Network captures and Perfetto traces.
  • Multi-file bundles. Upload an archive of logs as-is. Each file is analyzed on its own and findings are correlated across the set, so an identifier that’s meaningless in one file can be resolved using another file in the same upload. See Multi-file bundles.
  • The analysis dashboard. Every analyzed file gets a dashboard built for what it is, with an event timeline and charts chosen for that format. See Analysis output & dashboards.
  • The public API and webhooks. Upload, poll, fetch a dashboard, and search over /api/v1, or subscribe to a webhook and skip polling. See the developer docs.
  • Every file is analyzed automatically. You don’t trigger analysis and it doesn’t cost you units. Only telecom, automotive, and kernel-dump logs need a matching capability on your account.
  • Usage is metered in investigation units. One budget covers search and research, priced by the size of the question. Uploading and analyzing a file costs nothing. See Investigation units & quotas.