Your team's AI reasoning, in one shared log
People now reason through decisions with Claude Desktop or ChatGPT Desktop before they reason with a colleague, and that judgment sits stranded in private histories. A menu bar widget captures the transcript region on-device, you tag the session, and colog synthesizes what the team is deciding, where it diverges, and what nobody has resolved.
Free for teams of three. Nothing is transmitted until you tag and review a session.
How capture works ↓Contradiction alert
Incompatible assumption about idempotency key lifetime. R. Chen's replay design assumes provider keys expire after 24 hours s38 · turn 22. M. Okafor's cutover plan retries failed charges against the same keys for up to 7 days s41 · turn 9. One of these is wrong.
Positions
- M. Okafor holds that a single cutover window is safer than a long dual-write period, since dual-write doubles the surface for drift. s41 · turn 6
- R. Chen holds that dual-write through Q3 with nightly reconciliation is the only way to validate the new ledger against real traffic. s38 · turn 14
- J. Lindqvist holds that either approach works if webhook replay is solved first, and that sequencing matters more than the choice. s44 · turn 3
Decisions
- Ledger table stays append-only. Corrections are new rows, never updates. Committed by M. Okafor, Feb 12. s41 · turn 18
- Refund flows migrate last, after charge and invoice paths are stable. Committed by R. Chen, Feb 13. s43 · turn 11
Open threads
- Who owns reconciliation when the nightly job flags a mismatch? Raised in two sessions, resolved in neither. s38 · turn 27 s44 · turn 8
Duplicated effort
Unexamined AI contributions
- The model raised PCI scope expansion from storing raw provider payloads. J. Lindqvist did not respond to it. s44 · turn 12
Capture stays inside one box, on one machine
The widget locates the transcript region of a supported app and snapshots each message only after it finishes rendering.
No video, no full screen. Capture is confined to the detected region, or to a box you draw yourself. Other windows and everything outside the box never enter the buffer.
Streaming output is never recorded mid-render. A snapshot fires only once the region has settled, and scrolling back through earlier messages re-records nothing.
Each snapshot is read by an on-device OCR model. Raw images and extracted text stay local. If the window is obscured, the widget pauses itself rather than keep degraded frames.
13:58:41 target detected claude-desktop (pid 4021) 13:58:41 transcript region 612×488 at (704, 318) · confidence 0.94 13:59:07 user turn committed snapshot 06 · ocr 41 words · kept local 14:00:52 response streaming region changing · holding 14:01:19 region settled 900ms snapshot 07 · ocr 318 words · kept local 14:01:44 scrollback detected 3 earlier turns matched · nothing re-recorded 14:03:02 window obscured capture paused · person notified 14:03:15 window visible capture resumed 14:04:31 window resized region re-detected 640×512 at (688, 302) buffer: 7 turns · 2,614 words · transmitted: 0 bytes
Nothing leaves until you tag and confirm
Applying a tag opens the full buffer for review, including everything captured before the tag existed, and commit proceeds only on your say-so.
- Asked how to sequence the ledger cutover without a write freeze
- Proposed dual-write with nightly reconciliation, listed three drift risks
- Rejected the freeze option, cited the EU invoicing deadline
- Pasted internal on-call notes excluded
- Suggested append-only corrections instead of row updates
Review is not optional and cannot be defaulted past. Everyone in the workspace can read committed sessions, and that is acceptable only because you see exactly what you are sharing, every time, before you share it.
Tagging late loses nothing. The whole buffer commits, including turns captured before the tag was applied. After the first commit, later turns in the same session commit automatically until you pause.
Untagged buffers die quietly. They are deleted 24 hours after the session ends, or immediately on quit if you set that. They are never transmitted.
Read it back into the chat you are having now
From the widget, pull any tag's current digest or search its sessions, then copy a result straight into your open conversation.
The loop closes where the work happens. Before you spend an hour re-deriving a constraint, search the tag. If a teammate already settled it, the decision and its reasoning are one paste away.
Same visibility rules everywhere. Nothing retrievable through the widget is hidden from the web app, and nothing hidden from the web app is retrievable through the widget.
Chen's replay design assumes provider keys expire after 24 hours. Okafor's cutover plan retries against the same keys for up to 7 days.
Ledger table stays append-only. Corrections are new rows, never updates. Committed by M. Okafor, Feb 12.
How it works
-
Install the widget
It lives in the macOS menu bar or Windows system tray. Onboarding walks you through screen recording permission, detecting your first transcript region, and a live capture of a throwaway conversation, so you see exactly what colog reads before any real session is recorded. Capture never starts on install.
-
Work as usual
Start capture with one click or a global shortcut. A visible indicator shows whenever capture is live, snapshots fire only after a message settles, scrolling back never re-records earlier turns, and everything stays in a local buffer. Untagged buffers are deleted after 24 hours.
-
Tag and review
Name the work the session belongs to: a project with an end state, or an ongoing operation. Before commit, you see the full buffer and can drop any turn. Tagging late loses nothing, because the whole buffer commits, including what came before the tag.
-
Read the digest
The tag's digest regenerates as sessions arrive: positions per participant, decisions with the reasoning behind them, open threads, and contradiction alerts. Every claim links to its source turn, where the retained snapshot sits next to the extracted text.
Priced per workspace, not per session
Capture and tagging are unlimited on every plan. Plans differ by how many people share a workspace.
Solo
For one to three people proving the loop works. Full capture, tagging, and digests, capped at three workspace members.
- Up to 3 workspace members
- Unlimited capture and tagging
- Digests with per-turn source links
- Snapshot review before every commit
Team
For a working team that wants one shared record of what everyone is concluding.
- Up to 10 workspace members
- Contradiction and duplicated-effort alerts
- Widget read-back and in-tag search
- Admin controls for membership and captured apps
Org
For multiple teams under one workspace with shared visibility rules.
- Up to 30 workspace members
- Workspace retention policy
- Activity log for merges, renames, and admin deletions
- Priority support during early access
Early access pricing. Committed sessions are retained until you delete them or your admin sets a shorter retention period. Cancel anytime.
FAQ
What leaves my machine, and when?
Nothing, until you apply a tag. Snapshots and OCR text stay in a local buffer while you work. Committing a tag transmits the session after you have reviewed every turn and excluded anything you want out. Untagged buffers are deleted 24 hours after the session ends, or immediately on quit if you set that.
Which AI applications does it capture?
Claude Desktop and ChatGPT Desktop in v1, on macOS and Windows. Browser-based sessions, terminal tools, and IDE-embedded assistants are not captured. You can disable any supported app from the widget, and admins control which apps a workspace may capture at all.
Can it capture without me knowing?
No. Capture never starts on install, it starts only when you start it, and a visible indicator is on whenever capture is live. Capture is confined to the detected or hand-drawn transcript box, and if the target window is obscured the widget pauses itself rather than recording degraded frames. We treat any bug in the indicator or the capture boundary as the highest-severity class in the product.
How accurate is the extracted text?
OCR degrades most on code blocks and tables, and we measure prose and code accuracy separately. Because of this, digests never present verbatim quotes. Every claim is stated in the digest's own words and links to the source turn, where the original snapshot is kept next to the extracted text so you can check the pixels.
Who can see my sessions?
Committed sessions and digests are visible to everyone in your workspace. That is acceptable only because commit is preceded by review: you see exactly what you are sharing before you share it, every time. You can delete any of your own sessions at any point, which removes them from the tag and regenerates the digest.
What stops tags from sprawling into duplicates?
Anyone can create a tag, and matching is exact, so sprawl is a real risk we instrument from day one. When you create a tag, the widget shows existing tags with similar names or descriptions and offers to attach instead. Any member can rename, merge, or archive tags from the web app, and every change lands in the workspace activity log.
The model's output is reproducible. Your team's judgment is not.
Every correction, rejection, and constraint your people apply against a model today evaporates into a private chat history. Tag the session and it becomes something a teammate can find before the meeting where you would otherwise discover you disagree.
Free for teams of three. Questions: hello@colog.igotnostrings.com