AI Usage Policy
This policy is adapted from Ghostty's AI Policy with modifications for the Letta project.
Rules
-
All AI usage in any form must be disclosed. You must state
the tool you used (e.g. Claude Code, Cursor, Copilot, ChatGPT) along with
the extent that the work was AI-assisted.
-
The human-in-the-loop must fully understand all code. If you
can't explain what your changes do and how they interact with the
greater system without the aid of AI tools, do not contribute
to this project.
-
Issues and discussions can use AI assistance but must have a full
human-in-the-loop. This means that any content generated with AI
must have been reviewed and edited by a human before submission.
AI is very good at being overly verbose and including noise that
distracts from the main point. Humans must do their research and
trim this down.
-
No AI-generated media is allowed (art, images, videos, audio, etc.).
Text and code are the only acceptable AI-generated content, per the
other rules in this policy.
Enforcement
Issues that do not comply with this policy will be automatically closed and locked.
Specifically, all issues must:
- Fill out the AI Disclosure checkboxes indicating whether the issue was human-written or AI-assisted.
- Include the Human Verification phrase as instructed in the issue template.
- Acknowledge that they have read this policy.
Members of the letta-ai GitHub organization and
trusted contributors are exempt from automated checks,
but are still expected to follow the spirit of this policy.
There are Humans Here
Please remember that Letta is maintained by humans.
Every discussion, issue, and pull request is read and reviewed by
humans. It is a boundary point at which people interact with each other
and the work done. It is rude and disrespectful to approach this boundary
with low-effort, unqualified work, since it puts the burden of
validation on the maintainer.
AI is Welcome Here
Letta is a company that builds AI tools — of course we use AI!
Many of our maintainers use AI tools extensively in their daily workflow.
As a project, we welcome AI as a tool.
Our reason for the strict AI policy is not due to an anti-AI stance, but
instead due to the volume of low-quality, AI-generated issues and PRs
that waste maintainer time. It's the quality of the contribution that
matters, not whether AI was involved in creating it.
Maintainers are exempt from automated enforcement of these rules and
may use AI tools at their discretion; they've proven themselves
trustworthy to apply good judgment.