Content Ownership
What are the differences between Personal Memory, Project Knowledge and project strategy
What are the differences between Personal Memory, Project Knowledge and project strategy
Personal Memory belongs to the current user, preserving language, expression methods, verification habits and personal collaboration experiences. Project Knowledge belongs to the current project, saving the project structure, dependencies, decisions, processes, constraints, and verified troubleshooting methods.Project Policy is a type of record in Project Knowledge, used to describe project decisions, stability patterns, operation processes and constraints. It is not a new Rule file and will not overwrite
AGENTS.md, rules of other platforms, source code, configuration or tests.What contents will the Agent Learning Loop record
What contents will the Agent Learning Loop record
Native, Classic, Hotfix and Tweak will provide structured task results, user feedback, verification, Review, fault recheck and Archive events. The Learning Loop extracts reusable candidates from these events and then hands them over to individual memory or Project Knowledge respectively by owner and source.Explicitly requiring “It will always be like this from now on” can directly form Personal Memory. The experience summarized by the system is usually tried out at a lower priority first, and then the status is elevated after successful application or conclusive evidence.
Will Comet save complete chats, tool logs or code diffs
Will Comet save complete chats, tool logs or code diffs
No. Long-term records only retain necessary context, action summaries, results, and evidence references, without preserving complete chats, complete task trajectories, complete Diffs, original tool logs, command outputs, or model hidden reasoning. Ordinary project facts that can be directly obtained from the current repository will not be written into Personal Memory either.
Context selection
The Dashboard has relevant records. Why isn't the current task directly used
The Dashboard has relevant records. Why isn't the current task directly used
The Context Director will filter the content based on the current project, path, task, operation and stage. A small number of key portraits and directly related stable records can be fully integrated into the context. Other candidates only enter the Context Manifest, provide the summary, application reason and stable ID, and expand the body and source when needed by the Agent.The existence of records does not mean that every task should be injected. When the scope does not match, the source has changed, the record has been replaced, or the current task has low relevance, Comet will skip it.
Will Personal Memory or Project Knowledge cover the current requirements
Will Personal Memory or Project Knowledge cover the current requirements
No. The current user requirements, system constraints, repository rules, source code, configuration, testing, and Runtime status remain at a higher priority. The long-term context only helps the Agent understand the collaboration preferences and project background more quickly, and does not expand the submission, push, deletion or publication permissions.
Management and Faults
What should be done after an error record is discovered
What should be done after an error record is discovered
Personal memories can be corrected, forgotten or rolled back on the Dashboard or through
comet memory correct, forget and rollback. By default, the recovery ability is retained when forgetting. Permanent deletion requires explicit selection.The source of Project Knowledge should be verified first. A change in source will render old records invalid. When corrections need to be retained, record them through the management entry of Project Knowledge. Do not overwrite project facts by modifying Personal Memory.Will a failed plugin or background Reflection block the workflow
Will a failed plugin or background Reflection block the workflow
When background collection, Reflection, retrieval or a single Learner fails, Comet will record the diagnosis and continue the current Native, Classic, Hotfix or Tweak process. Personal Memory and Project Knowledge use independent providers, and a plugin failure will not interrupt another type of context.When the explicit add, correct, forget, roll back or expand operation you are waiting for fails, Comet will return the actual error and maintain the original state, and will not report the failed operation as a success.