The last month of work moves Clo0p from a structured checklist and connector UI toward a proto-intelligent collaborator: it senses external signals, extracts work, organises it into meaning, decides whether action is possible, drafts interventions, and asks the human for approval. It is promising, but not complete: the evidence rails are uneven, the confidence gates are early, and quality still depends on fragile runtime glue.
Clo0p now has the outline of an intelligence loop: sense → extract → organise → decide → draft/act → learn from undo/ignore.
The strongest recent work is not a single screen. It is the coupling between heartbeat ingestion, Compass organisation, people/contact memory, action tools, and the new Agentic Inbox. Those pieces make the app feel less like a passive dashboard and more like a system that notices unfinished loops.
This is still an early, brittle form of intelligence. It has tool-mediated agency, not robust judgement. It can draft and auto-tick under constraints, but the tests expose mock/runtime drift, lint exposes React/compiler debt, and several subsystems still rely on prompt policy rather than durable evaluators.
The repo changed across three surfaces: the production app, the public site, and a new local-first desktop/vault direction. The product center of gravity shifted from “show my tasks” to “maintain my loop across tools.”
Self-organising tasks, containers, push-back UX, calendar-aware day/week views, meeting notes, people pages, multi-account connectors, and a sidebar/inbox shell all landed or were materially expanded.
tasks-panel.tsx, day-column.tsx, project-canvas.tsx became major surfaces.P13 shipped a heartbeat-driven sibling to the interactive task rail. For each open task, the runtime can auto-tick, draft an email/Slack/meeting, or stay silent.
runAgenticTurn.ts implements a one-agent, three-verdict loop.agentic_drafts, blocklist, backoff, watch mode, transcript views, and inbox preferences create a reviewable action queue.A new Electron/Obsidian-flavoured app appeared: vault picker, editor, file tree, graph canvas, connector plumbing, Granola connector, SQLite engine, device secrets, and local graph/search primitives.
| Theme | Representative changes | Why it matters |
|---|---|---|
| Agentic Inbox | single-runtime three-verdict pipeline, watch mode, confirm modal, DateTimePicker, Granola pivot, Google REST, inbox UI polish | Turns latent checklist items into evaluated opportunities for action. |
| Compass v5 | push-back UX, scheduledFor routing, extraction hit-rate work, reorganise, container scoring, dedup indexes | Makes the task substrate more semantic and less manually curated. |
| People graph | people page, merge/delete, top contacts RPC, source icons, Granola/Notion sources, dossiers | Moves from tasks-in-isolation to tasks embedded in relationships. |
| Integrations | Google, Slack, Notion, Granola auth callbacks, heartbeat status, multi-account labels, token refresh | Intelligence depends on live context; connectors are the sensory organs. |
| Public site | Cloop rename, auth/signup polish, Attio sync, force graph, pricing/agent/relay sections, POST route hardening | Sharper external story and acquisition funnel, plus CRM feedback loop. |
| Desktop/vault | cloopdrive package, SQLite, vault/editor/graph UI, Granola connector, Obsidian-style wiki links | Explores local-first ownership and personal knowledge graph rails. |
The valuable work is concentrated where the system reduces open loops without adding a new inbox burden.
Best new product primitive. It inverts the P10 interactive task rail: instead of the user opening every item, the heartbeat walks open items and only surfaces drafts worth reviewing.
Value: reduces “I need to click everything” into “approve the few things Clo0p can actually help with.”
Containers, scoring, fingerprinting, and reorganise passes make the task list pattern-aware. It can infer projects/themes/identities across the whole set rather than only sorting rows.
Value: transforms raw extraction into an attention cockpit.
Moving tasks across day checklists is a clean primitive. It collapses ambiguous scheduled/deadline UX into “when should I see this?” plus system-extracted urgency hints.
Value: makes attention temporal without requiring heavy project management.
Top contacts, merge, source icons, and social dossier compilation are the beginning of relationship-aware task execution.
Value: many actions are about people; the system needs a social substrate.
The repo now contains several cognitive-looking loops. They are narrow and engineered, but they are real primitives for an intelligent collaborator.
Clo0p is not “intelligent” because it calls a large model. It is becoming intelligent because the codebase is starting to wrap model calls in durable loops: source evidence, user context, tool surfaces, confidence gates, reversible side effects, draft review, telemetry, and correction memory. The intelligence lives in the loop architecture, not inside a single completion.
The sharpest risks are no longer “can we build a UI?” They are judgement quality, reliability, trust, and whether the system compounds rather than spams.
Unit tests fail in Granola heartbeat because the mock Supabase client lacks schema(), causing real-content paths to error and insert nothing. That is a sign the integration test harness is behind the production code shape.
Lint reports React purity, set-state-in-effect, declaration-order, and explicit-any errors. Build passes, but static hygiene is not yet clean enough for high-confidence iteration.
P13 deliberately avoids cheap cascades, capability gates, and a skill registry. That simplicity shipped, but it means judgement quality is highly dependent on one agent call and one preamble.
Auto-tick records evidence summaries; drafts have transcripts; Compass has reasoning. But there is not yet a unified evidence ledger connecting signal → extraction → priority → action → outcome.
Undo and ignore are good rails, but the system is not yet building a nuanced model of “Connor dislikes this class of suggestion unless X.”
cloopdrive is exciting, but the hosted app, local vault, relay, and future Obsidian-like ownership model need a crisp source-of-truth story.
The month included route hardening and private Granola schema work, which is good. But an app that reads mail, calendars, meetings, Slack, and Notion needs explicit provenance, least privilege, retention, and user-visible control.
Drafts do not auto-send and auto-tick is reversible. The next risk is subtle: bad timing, wrong account, stale contact identity, or overconfident completion.
In one month the app added Compass, inbox, people, multi-account, public-site growth, and desktop/vault tracks. The architecture needs visible boundaries before complexity compounds.
git pull --ff-only updated main to 1635bb6.clo0p-app npm ci completed.clo0p-app npm run build compiled successfully, TypeScript completed, and 54 app routes generated.clo0p-com npm ci && npm run build completed and generated 26 routes.clo0p-app npm test -- --run: 103 passed, 6 failed, all in granola.test.ts, rooted in supabase.schema is not a function in the test double.clo0p-app npm run lint: 11 errors and 23 warnings, mostly React compiler/lint issues plus one any.npm ci reported 16 app vulnerabilities and 19 public-site vulnerabilities. I did not run audit fix because that would mutate dependencies beyond the requested review.Fix the Granola Supabase mock drift, then clear lint’s real errors. The repo is now moving fast enough that broken gates will hide actual regressions.
Unify signal, extraction, container, priority, agent verdict, draft, send, undo, ignore, and user outcome into one inspectable path. This is the difference between vibes and trust.
Ignore/undo should not just suppress exact rows. It should graduate into typed preference memory: source, person, action class, timing, account, and risk tolerance.
Decide what lives in Supabase, what lives in the vault, what is synced, and what is only transient. cloopdrive is powerful if it becomes a coherent ownership layer rather than a parallel app.
Sample P13 runs weekly: precision of auto-ticks, draft usefulness, out-of-scope false negatives, account routing mistakes, and ignored-card reasons.
The strongest wedge is probably “meeting/email/Slack commitments become reviewed drafts or completed tasks automatically.” Make that one loop boringly reliable before broadening.