gitlearnos

GitLearnOS

Learner-owned Git memory · GitLearnOS-exclusive native DeepSeek Harness support

Learning happens anywhere. State belongs to you.

Open the official website →

·

Core-ready Quickstart →

[中文](zh-CN/README.md) ·

[Website](https://guojiz.github.io/gitlearnos/) ·

[Documentation map](DOCUMENTATION.md) ·

[Protocol](GITLEARNOS.md) ·

[Author site](https://guojiz.github.io/) ·

[X](https://x.com/guojizh) ·

[Bilibili](https://space.bilibili.com/3493114115263006) ·

[Sponsor](https://github.com/Guojiz/Sponsors)

The core promise

GitLearnOS gives one capable, replaceable main AI agent a learner-owned Git

memory. It notices useful learning events, connects evidence to a goal, guides

the next action, and leaves an inspectable, reversible record.

Learning can happen with a teacher, in class, on paper, in a book, on a

practice platform, in a project, with peers, or with another AI. GitLearnOS

does not move all learning into one application. The main agent connects only

the evidence that is useful for the learner's next decision.

The core is ready with a private local Git repository, one write-capable agent,

the GitLearnOS protocol, and one subject or real learning event. GitHub and

other remotes are optional. During normal learning, Git stays in the

background: the learner should not have to manage folders, branches, or

commits.

The default recommendation is private. Add a remote only when the learner

chooses backup, cross-device continuity, teacher review, collaboration, or

publishing, and keep private answers and gaps separate from shared material.

Core-ready, then everyday learning

The agent answers the immediate request first. Under safe-auto, it may then

make the smallest safe writeback when the target, evidence, goal, and privacy

boundary are clear. preview proposes the exact change without writing;

manual waits for approval. Original answers, notes, and external feedback

are preserved; AI interpretations remain revisable and must link to evidence.

Once configured, a learner should not need to say “use GitLearnOS” or name a

Skill. A question, attempted answer, page photo, class note, teacher comment,

practice result, or repeated difficulty can be a learning event. Incidental

conversation is not stored.

goal and real input
→ organize traceable evidence
→ ask from the current gap
→ keep the answer or external feedback
→ recheck independently later
→ update state with one reversible Git commit

The success condition is better independent performance on later questions,

not a larger pile of generated notes. A normal receipt distinguishes what the

current agent did immediately from what a verified scheduled run actually did.

A small, useful repository

gitlearnos.yml
AGENTS.md
automation.md
dashboard.md
learner-profile.md
subjects/
└── /