SOLVED
A new agent session starts cold
A new AI agent session remembers nothing from last week. It asks Smeldr what holds today before it writes a line.
Get started
No dashboard required.
Your AI handles publishing through a structured API. Your team stays in the tools they already use.
Full control, zero risk.
Role-based access means your AI can only do what you allow. Draft content never leaks.
Live in minutes.
Connect once. From that point, a conversation is all it takes to publish.
A new coding agent session has no memory of last week. Before it edits internal/billing/handler.go, it asks Smeldr which Decisions apply to that path in the repository. The answer names the Area, how it handles changes, and the Decisions in force there, including the one on the whole organization about session tokens. A second file it was about to touch is covered by no Area. The agent tells you so, because nothing in the record speaks to that file.
It does not read last week's chat or a notes file that may be out of date. It asks, and the answer is what holds today. A Decision that was replaced on Tuesday is not in the list.
The pull request check is the second look, if you have set it up. The first look happened before a line was written.
Names and numbers are made up. The steps are what Smeldr does today. Read the other stories in How Smeldr works in practice.
Ready to put your AI to work?
Forge is open source and self-hosted. Get started in minutes.