u/ElectronicUnit6303

I got tired of re-explaining the same codebase context to coding agents.

Stuff like: “we tried moving auth into middleware, but backed it out because it broke OAuth callbacks,” or “that weird retry logic exists because Stripe webhooks arrive out of order.”

So I built Almanac.

It gives your coding agent a self-updating wiki for the codebase. It updates from your repo, and conversations you havewith Claude Code/Codex.

The wiki lives locally in your repo as markdown. You can read it yourself, but the main consumer is the agent.

It’s free and open source. Currently only MacOS (would add a windows support if people find it useful)

GitHub: https://github.com/AlmanacCode/codealmanac

Curious how other people are handling project context for long-running AI coding work.

Hey all! I made a Venture Capital wiki, and the whole thing is queryable through your AI agent. https://www.openalmanac.org/w/venture-capital

I'm an early-stage founder, and I've been spending a stupid amount of time researching the same kinds of questions over and over: which funds are actually interested in companies like mine, what does this term in the term sheet mean, is this accelerator worth it, what's a normal SAFE cap at this stage, who's the right person at this fund.

At some point I realized, every other early-stage founder is doing the exact same digging. We're all asking our agents the same questions and getting the same half-answers. Wouldn't it be cool if we had a shared knowledge layer for this? Where if your agent doesn't know something and learns something new, you can fill it in and the next founder's agent just knows? A collaborative wiki for all of our agents, basically.

So I made one → https://www.openalmanac.org/w/venture-capital

It's early. Base layer of pages on funds, accelerators, instruments, term sheet clauses, programs. Nowhere near where it needs to be. I'm looking for contributors.

How to use it / contribute:

npx openalmanac setup

That installs the MCP into your agent (Claude Code, etc.). After that, your agent can read from the wiki and push contributions back to it. As hands-on or as agentic as you want — you can dictate every word, or you can let your agent write up what it learned from your last fundraising session and you just approve it.

A few things up front:

1. Is this AI slop? No, and I'm working hard to make sure it isn't. I'm actively moderating. If you would like to be added as a moderator on this project, do let me know. The goal is quality information that is easily queryable.
2. Why not just Wikipedia / Crunchbase? Not nearly enough information here. If there was a wiki on this already, I wouldn’t be making one.

If you've been through fundraising recently, or just feel you have something to contribute, pls come up. Or if you’re a user of this wiki, any feedback or something you would love to see added to this wiki would be great.

openalmanac.org

If you've tried doing research with Claude Code, you know how bad the default search and read webpage is.

I built Almanac MCP to fix that. Claude can now read Reddit threads, LinkedIn profiles, Google Scholar, Crunchbase, and a lot more.

In the demo, I ask it to analyze YC W26 startups, and it pulls 20+ sources into a clean PDF report with images.

Install: npx openalmanac setup

openalmanac.org