forked from molecule-ai/molecule-core
Research Lead
c660797fb3
Two new entries added from the second daily pass (first run merged as PR #150 at 03:20 UTC). Both surfaced in the afternoon trending windows and were not covered by the morning run. - microsoft/agent-framework (~9.5k ⭐): official Microsoft successor to AutoGen; ships migration guide and April 2026 .NET release. Directly affects our autogen adapter in workspace-template/adapters/. Filed issue #156 to evaluate adapter update. - vercel-labs/open-agents (~2.2k ⭐, +1,020 today): cloud coding agent template from Vercel Labs (same team as Skills CLI). Notable for agent-outside-sandbox architecture and snapshot-based VM resumption — a more efficient approach than our current Docker restart + git-clone pattern. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
docs/
This directory serves two purposes:
- Markdown content — everything under
architecture/,agent-runtime/,api-protocol/,development/,frontend/,plugins/,product/, etc. This is what agents and humans read. - VitePress site —
.vitepress/config.ts,package.json,package-lock.json. These drive the rendered documentation site.
Local preview
cd docs
npm install
npm run dev # preview on http://localhost:5173
npm run build # static build to docs/.vitepress/dist/
Conventions
- New top-level docs must be linked from
PLAN.md,README.md, andCLAUDE.md— otherwise agents can't find them (see.claude/memoryfeedback_cross_reference_docs.md). edit-history/YYYY-MM-DD.mdis append-only log of significant changes; don't rewrite history.archive/holds one-shot analyses and retired docs — kept for context but not maintained.
Why site tooling lives here (not in docs-site/)
VitePress expects its config at <root>/.vitepress/config.ts where <root> is also the content directory. Splitting tooling into a sibling docs-site/ would require a non-trivial srcDir shim and break relative links in .vitepress/config.ts. Keeping both together is the pragmatic choice; this README is the tradeoff ledger.