Ask your ChatGPT: which is the best ai engineering from scratch in github to learn AI?

u/SeveralSeat2176 — 13 days ago

An open source natural temporal memory for claude code, hermes and openclaw agent

You can now give Hermes Agent infinite memory.

The three-tier architecture is the cleanest I've seen in any open-source agent. The Tier 1 cap is the constraint.

MEMORY md file is 2,200 chars. USER md file is 1,375 chars. Hit 80% and consolidation kicks in: the agent merges related entries into denser versions, which is lossy. The longer you run Hermes, the more your earlier context gets compressed away.

Tier 2 (SQLite FTS) is unlimited capacity but every retrieval needs an LLM summarization pass. Tokens and latency on the critical path.

Tier 3 is the plug-in slot. That's where agentmemory fits.

What it adds on top of the existing design:

→ Hybrid retrieval: BM25 + vector + knowledge graph, fused with RRF
→ Ebbinghaus decay so unused memories fade gracefully instead of getting consolidated out
→ Token-budgeted injection that keeps Tier 1 clean
→ Benchmarked on LongMemEval
→ 90% savings

Same numbers as the Claude Code benchmarks: ~92% fewer tokens at 240 observations. 200x more tool calls before hitting context limits.

Hermes already exposes the slot. agentmemory is the obvious thing to plug in.

https://github.com/rohitg00/agentmemory

u/SeveralSeat2176 — 14 days ago
▲ 160 r/letscodecommunity+3 crossposts

An Open source AI Engineering From Scratch Course with 503 Lessons and Fully AI-native Skills Prompts as a takeaway

I got frustrated with AI courses that either drown you in theory or skip straight to model.fit() without explaining what's happening underneath.

So I built something different.

This is an AI-native GitHub repo learning files with 503+ lessons across 22 phases. 35,000 GitHub Stars. Start at linear algebra. End at autonomous agent swarms.

Every lesson follows the same pattern:

  1. Build it from scratch in pure Python (no frameworks)
  2. Use the real framework (PyTorch, sklearn, etc.)
  3. Ship a reusable tool (prompt, skill, agent, or MCP server)

By the end, you don't just "know AI." You have a portfolio of tools you actually built.

What's covered:

- Math foundations (linear algebra, calculus, probability, Fourier transforms, graph theory)
- Classical ML (regression through ensemble methods, feature selection, time series, anomaly detection)
- Deep learning (backprop, activation functions, optimizers, regularization - all from scratch before touching PyTorch)
- LLMs from scratch (tokenizers, pre-training a 124M parameter GPT, SFT, RLHF, DPO, quantization, inference optimization)
- LLM engineering (RAG, advanced RAG, structured outputs, context engineering, evals)
- Agents and multi-agent systems
- Infrastructure (model serving, Docker for AI, Kubernetes for AI)

Some specifics that might interest you:

- The quantization lesson covers FP8/GPTQ/AWQ/GGUF with a sensitivity hierarchy (weights are least sensitive, attention softmax is most sensitive - never quantize that)
- The inference optimization lesson explains why prefill is compute-bound and decode is memory-bound, then builds KV cache, continuous batching, and speculative decoding from scratch
- The DPO lesson shows you can skip the reward model entirely - same results as RLHF with one training loop
- Context engineering lesson: "Prompt engineering is a subset. Context engineering is the whole game."

It's AI-native:

The course has built-in Claude Code skills. Run /find-your-level and it quizzes you across 5 areas to tell you exactly where to start. Run /check-understanding 3 after Phase 3 and it tests what you actually learned.

84% of students use AI tools. 18% feel prepared. This is the bridge.

Where to start:

- Already know Python but not ML -> Phase 1
- Know ML, want deep learning -> Phase 3
- Know DL, want LLMs/agents -> Phase 10
- Senior engineer, just want agents -> Phase 14

Website: https://aiengineeringfromscratch.com
Repo: https://github.com/rohitg00/ai-engineering-from-scratch

It's free, MIT licensed, and open source. 35,000+ stars, PRs welcome - I merge every good contribution and the contributor gets full credit.

u/SeveralSeat2176 — 11 days ago
▲ 153 r/cursor

Cursor launches github for agentic era

Three big launches:

- Cursor iOS app

- Origin, an agentic replacement of Git

- A new model is in the works in collaboration with spaceX

- SpaceX to acquire Cursor

u/SeveralSeat2176 — 19 days ago

An open source persistent agentmemory with 20K+ Stars

Persistent memory for AI coding agents based on real-world benchmarks.

agentmemory works with any agent that supports hooks, MCP, or REST API. All agents share the same memory server.

You explain the same architecture every session. You re-discover the same bugs. You re-teach the same preferences. Built-in memory (CLAUDE.md, .cursorrules) caps out at 200 lines and goes stale. agentmemory fixes this. It silently captures what your agent does, compresses it into searchable memory, and injects the right context when the next session starts. One command. Works across agents.

What changes: Session 1 you set up JWT auth. Session 2 you ask for rate limiting. The agent already knows your auth uses jose middleware in src/middleware/auth.ts, your tests cover token validation, and you chose jose over jsonwebtoken for Edge compatibility. No re-explaining. No copy-pasting. The agent just knows.

reddit.com
u/SeveralSeat2176 — 1 month ago
▲ 2 r/OpenAI

How should agent memory work when the agent needs reviewed project knowledge?

Disclosure: I’m the author.

I’m not sure if this is mature enough for this subreddit yet, so please remove if it is not a fit.

I’m building AKBP, an alpha local-first protocol/reference implementation for agent knowledge bases:

https://github.com/rohitg00/akbp

It is not a hosted SaaS and not a production-ready app yet.

The goal is to let coding agents maintain a local, file-backed knowledge base with:

- typed claims

- source hashes

- audit logs

- review-gated writes

- SQLite FTS5 search

- import/export validation

- conformance checks

The reason I thought it may be relevant here:

A lot of agent memory systems are tied to hosted products or opaque storage. I wanted something portable, inspectable, and local-first.

Current limitations:

- alpha

- no stable release yet

- needs more real-world dogfooding

- needs clearer migration/versioning policy

If you self-host agent/devtool workflows, I’d be curious:

Would a local file-backed knowledge base be useful, or would you rather have a server/API/database-first design?

u/SeveralSeat2176 — 2 months ago

Agents keep re-deriving project context. I’m experimenting with a local-first knowledge base protocol

Disclosure: I’m the author of this project.

I’ve been working on AKBP, an alpha-stage, local-first knowledge base protocol for agent runtimes.

The problem I’m trying to solve:

Most coding agents and local LLM workflows still treat project knowledge as temporary.

They read files.

They infer decisions.

They summarize a chat.

Then the next session starts over again.

Repo instructions help with behavior, but they don’t really capture reviewed project knowledge. Plain RAG helps retrieve documents, but it usually does not define durable claims, source hashes, lifecycle states, or review-gated writes.

AKBP is my attempt to make that layer explicit.

Current design:

- file-backed knowledge base

- typed claims

- source hashes

- audit log

- lifecycle relations

- review-gated writes

- SQLite FTS5 search

- context packs with citations

- JSONL tool server for agent integrations

- schemas and conformance tests

- export/import verification

The workflow is roughly:

  1. register sources

  2. ingest notes / transcripts / decisions

  3. propose claims

  4. review before writing

  5. rebuild indexes from source-of-truth files

  6. give the next agent session cited context instead of vibes

This is not a finished memory product.

It is not a vector database replacement.

It is not a research breakthrough.

It is more like a protocol experiment for portable, source-backed agent knowledge.

The repo is here:

https://github.com/rohitg00/akbp

Current limits:

- alpha, no 1.0 compatibility promise

- needs more retrieval-quality benchmarks

- needs more adapter dogfooding

- needs clearer migration policy

- long-document ingest needs more proof

I’d really like critique from people running local agents:

- Is this the right abstraction, or too much protocol?

- Would you want this as files, SQLite, MCP tools, or all three?

- What would make you trust agent-written memory?

- What should the conformance tests cover before this is useful?

reddit.com
u/SeveralSeat2176 — 2 months ago
▲ 11 r/ChatGPT

ADHDer's dream job: Coming up with brilliant ideas and immediately handing them to someone else to execute

u/SeveralSeat2176 — 2 months ago