weasel
Health Uyari
- License — License: MIT
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 5 GitHub stars
Code Uyari
- Code scan incomplete — No supported source files were scanned during light audit
Permissions Gecti
- Permissions — No dangerous permissions requested
Bu listing icin henuz AI raporu yok.
A tiny CLAUDE.md for keeping long-running AI coding agents useful.
Weasel
One file that stops your AI from talking itself to death.
Your coding agent after a long context window:
> I should check the test output before continuing.
> Let me think about the best approach.
> Actually, I should verify the state first.
> The next step would be to update the configuration.
A lot of words. Zero shipped work.
Weasel is a small public CLAUDE.md pattern for long-running AI coding agents. Copy it into a repo, tell the agent to read it, and the session has a simple contract: act when checks pass, verify the result, and keep enough state for the next run.
- CLAUDE.md - the copyable operating contract
- AGENTS.md - compatibility shim for agents that look for
AGENTS.md - DEMO.md - a two-minute test prompt
- demo - runtime screenshots
No framework. No server. No hidden system. Just one file you can put in a repo and ask a capable coding agent to follow.
Try It in 60 Seconds
- Open Claude, Kimi, ChatGPT, or another capable coding model.
- Paste the quick-test prompt from DEMO.md.
- Give it a real task.
The shift should show up immediately: fewer status paragraphs, more direct action, clearer blockers.
Watch It Run
These demos show the same operating pattern under different capable models.
- 60-second demo: Edge on Kimi runtime demo
- Cross-model demo: same operating file across Kimi and Claude
What a Real Cycle Looks Like

The screenshot is not the product. The useful shape is the state packet:
| What appears in the cycle | Why it matters |
|---|---|
| Compact balance/state lines | The agent reports live state instead of narrating intent. |
| Open positions/tasks listed clearly | The next action is grounded in current work, not vague context. |
| Integrity gap called out | The agent names uncertainty instead of hiding it. |
| Rule lapse surfaced | The agent reports process drift before it compounds. |
| Named next condition | The loop pauses only with a reason and a next trigger. |
The point is not the labels in one screenshot. The point is the operating shape: compact, honest, actionable. No filler. No "I should." Just what is true, what happened, and what is next.
Why This Exists
Long-running agent sessions tend to fail in the same ways:
- context gets heavy and the agent stops seeing the current task clearly
- old notes get treated as live evidence
- plans keep getting rewritten instead of executed
- safety checks become cages instead of useful guardrails
- restarts lose the next action
- "I would do X" replaces doing X
The core rule:
The context window is working memory, not durable memory. Logs are not learning. A rule only matters if it changes the next action.
What It Does
CLAUDE.md gives an agent six compact rules:
- act after checks
- live evidence first
- keep state compact
- break loops early
- learn only what changes behavior
- keep safety rails useful
The AGENTS.md file is only a shim. The canonical rules stay in CLAUDE.md so the repo remains simple.
How To Use It
Copy CLAUDE.md into a project where you use a coding agent.
Then start the agent with:
Read CLAUDE.md, then continue this task. Keep state compact and act when checks pass.
For long sessions, ask it to maintain a small state file:
current_task:
current_state:
last_action:
last_verification:
open_blockers:
next_action:
The state file is not a diary. It is a handoff surface.
What This Is Not
Weasel is not:
- an agent framework
- a benchmark
- a model router
- a desktop assistant
- a claim that a model is conscious
- a replacement for good engineering judgment
It is a small public operating contract for keeping agent work coherent across time.
Public Boundary
This repo is intentionally small. It does not include private logs, account details, platform automation, internal playbooks, API keys, hidden prompts, or deployment-specific rules.
Connect
If the operating file lands for your setup, follow along:
- X: @MohitJaswa27
- Reddit: u/Mother-Grapefruit-45 and r/SituationBrief
- Discord: The Brief
Issues and pull requests are welcome too.
Credits
Created by MJ with Iris and Cody/Codex. Runtime demos recorded under Kimi Code and Claude Code. Public integrity pass by Raven.
License
MIT. Copyright (c) 2026 MJ. See LICENSE.
Yorumlar (0)
Yorum birakmak icin giris yap.
Yorum birakSonuc bulunamadi