Research moves fast. Cly keeps every claim connected.
The local-first system of record for computational research—linking sources, methods, code, experiments, results, and decisions in one auditable graph.
Interactive Cly workspace using a dummy project
Explore four curated product views with built-in dummy data. The rest of the workspace remains visible but locked in this public preview.
Local
Project overview
Neural surrogate reliability
A computational study of uncertainty-aware neural surrogates across out-of-distribution physical regimes.
- Question
- Sources
- Method
- Experiment
- Evidence
- Claim
Research phaseEvidence consolidationUpdated today
Active claims42 need attention
Experiments41 running
Reproducibility76%Mostly reproducible
Evidence graph1412 relationships
Research direction
The question and hypothesis currently organizing this project
Claims and integrity
What is strongest, what is weakest, and what could block publication
Search papers without losing why each one mattered.
Cly ranks open literature locally, preserves the ranking rationale, and connects saved methods, limitations, and claims back to the project graph.
Compare methods, results, limitations, and claims.
Designed around the tools research teams already use.
- Local projectsLocal-first
- GitHubRepository adapter
- VS Code + CursorEditor-independent
- Jupyter notebooksScan and register
- Claude + CodexHarness support
- Local LLMsOllama-compatible
Cly keeps the research record provider-neutral: run Claude Code, Codex, Cursor or OpenCode harnesses, or keep private work on Ollama-compatible local LLMs. External connection setup continues to harden while the research core remains editor-independent.
The research claim is the central object.
Cly preserves why the work exists—and whether the conclusion still holds.
A notebook can show what ran. A repository can show what changed. Cly keeps those facts connected to the question, evidence, method, decision, and claim they serve.
Watch the graph assembleWatch the record assemble around the claim.
Separate research objects move onto one shared graph. Relationships appear only when the record can name them.
- 01Objects
- 02Relationships
- 03Claim
From question to claim, without losing the thread.
Cly keeps the research record beside the work as it changes. Earlier decisions remain visible; new evidence changes the state instead of erasing the history.
01
Plan
Name what the work needs to establish.
Keep the question, hypothesis, metric, constraints, and decision criteria in view before an agent or notebook begins.
02
Build
Carry research context into computation.
Cly Dev gives sessions, code, diffs, terminals, tests, branches, and approvals a place inside the larger research record.
03
Audit
Let changed evidence change the status.
Stale outputs, irreproducible runs, incomplete support, and disagreement remain visible instead of resolving into false confidence.
04
Coordinate
Hand off a record, not a pile of files.
Collaborators and reviewers can see the decisions, open questions, object history, and exact evidence that still needs judgment.
Every result has a lineage.
Trace the dummy project from input to claim. Every object below is selectable, and every state represents a different integrity story.
neural-surrogate / chainArtifact objectfigure-2.svg
Feeds Claim 04 through an explicit project relationship.
Delegate the work. Keep its purpose attached.
Start a preplanned dummy session and watch Cly Dev return execution evidence to the research record—not just a chat transcript.
agent/figure-2-lineageLocalReady for a research-scoped task.
The session already knows the project, selected objective, branch, and approval boundary.
Research defines the record. Dev performs the work. Core keeps the lineage intact.
Primary surface
Cly Research
Questions, evidence, experiments, decisions, claims, and review.
SourcesExperimentsClaimsAudits
Execution surface
Cly Dev
Computational work recorded against the research objective it serves.
Agent sessionsFiles + diffsTerminal + testsBranches + approvals
Shared foundation
Cly Core
Project-scoped state, relationships, provenance, identity, and permissions.
Research graphObject historyProvenancePermissions + sync
Your research stays yours.
Cly is built around project-scoped local state, visible transfer boundaries, and explicit human decisions. Provider-specific controls continue to harden as external adapters are implemented.
Neural surrogate reliabilityLocal project
Research recordProject-scoped SQLite and referenced local artifactsLocal
Provider accessContext should be previewed and approved before transmissionBoundary
Device identityFingerprint verification, key rotation, and revocationImplemented
Audit historyObserved, approved, and changed state remains attributableVisible
Local by default
Research metadata is project-scoped; large artifacts stay where your work already lives.
Approval before effects
Human judgment remains the boundary for context transmission and consequential actions.
Conflicts stay explicit
Concurrent or contradictory state requires resolution instead of silent replacement.