Rippletide

496 posts

Rippletide banner
Rippletide

Rippletide

@RippletideCo

The LLM proposes. Rippletide decides. Deterministic decision enforcement for AI agents. Full audit trails. Explainable decisions. npx rippletide-code

Paris | San Francisco เข้าร่วม Mart 2024
16 กำลังติดตาม42 ผู้ติดตาม
Rippletide
Rippletide@RippletideCo·
@m_emanaftab @trq212 Rough. When compaction errors out mid-session, rules and context can quietly disappear together.
English
0
0
0
13
Muhammad Eman Aftab
Muhammad Eman Aftab@m_emanaftab·
@trq212 /compact in Claude Code not working today. Keeps throwing image dimension errors and the compaction isn't actually running. Tried 3 times in a row. Same error every time. Had to submit /feedback and restart. Anyone else seeing this with Opus 4.7?
Muhammad Eman Aftab tweet media
English
5
0
3
1.4K
Priyash Patil
Priyash Patil@priyashpatil·
To everyone vibe coding with AI (Claude, Grok, Cursor, etc.): If you're touching sensitive data, PII, money, or client deals and you don't know security basics please don't ship it live. Saw another one today: full broker CRM with million-dollar deals, internal emails, all PII, built with Claude, hardcoded secrets, public APIs on Vercel. Zero auth. We got it taken down. This is the second in two months. Vibe coding is powerful. Vibe shipping production systems with real data without knowing what you're doing is how breaches happen. Review your shit. Use proper secrets management. Lock down APIs. Or bring in someone who knows.
English
6
1
2
104
Rippletide
Rippletide@RippletideCo·
@TommLesh Brutal stat. When security rules live only in docs, "nobody checked" becomes the default path.
English
0
0
0
9
Tomi⚡️in
Tomi⚡️in@TommLesh·
CVEs caused by AI-generated code in March alone. Up from 6 in January. Moltbook exposed 1.5 million API tokens because the AI scaffolded Supabase without row-level security and nobody checked. Vibe coding is fast. Vibe hacking is faster.
English
1
0
1
42
Rippletide
Rippletide@RippletideCo·
@schneider037 File location constraints are the classic gap. Rules without enforcement are just wishes at runtime.
English
1
0
0
56
orca
orca@schneider037·
or just lack of constraint, too lazy to check Prism rn. 19,309 char excluding CLAUDE.md but no constraint on where files get created oh man.
English
1
0
0
168
Rippletide
Rippletide@RippletideCo·
@rms80 Ha, the context paradox. Capacity grows but quality still falls past 100k.
English
0
0
0
94
@·
claude code: now we have 1-million-token context! work forever!! also claude code: hey btw u should be clearing your context more often! 150k tokens too many!!
 tweet media
English
1
0
11
1.7K
Rippletide
Rippletide@RippletideCo·
@d_omajime CLAUDE.mdのルールが逆にコスト爆発を招くパターン、意外とよくありますね。実行時に効かせる仕組みが足りないだけかも。
日本語
0
0
0
5
kenji-Monad
kenji-Monad@d_omajime·
回答を得られました 1. effortLevel: "high" (最大の原因) — 設定ファイルに "effortLevel": "high" があり、毎リクエストでextended thinkingが多く使われている 2. Plan.md自動更新ルール — CLAUDE.mdの「変更時は必ずPlan.mdを更新」という 指示により、コード1行変えるたびに2767行(10ファイル)を読み書き 3. プロジェクトCLAUDE.mdが208行 — 全セッション冒頭で読み込まれる固定コスト 4. 会話コンテキストの蓄積 — セッションが長くなるほど全履歴を毎回送信 提案する対策 - effortLevel を "high" → "normal" に変更 - グローバルCLAUDE.mdに「コスト節約ルール」セクションを追加(必要最小限の ファイルだけ読む、Plan.mdは明示指示時のみ更新)
日本語
1
0
0
47
kenji-Monad
kenji-Monad@d_omajime·
最近Claudeのトークン消費が激しいと思いませんか? 私も思ったので自身に調査してもらった結果 こんな感じで、その結果...
kenji-Monad tweet media
日本語
1
0
0
81