Israel B. Bitton @IsraelBitton

Author “A Brief and Visual History of Antisemitism” (Gefen) https://t.co/Bcggas9cGM New York Joined January 2014

Tweets

964
Followers

3K
Following

662
Likes

3K

Israel B. Bitton @IsraelBitton

3 months ago

Your next decision shouldn’t be one voice. Open source. Free. Two commands: claude plugin marketplace add b7069484/claude-committee claude plugin install committee Then type /committee: review — start an expert review suggest — auto-recommend the panel list — browse the committee experts add — create a custom persona custom — build an ad-hoc panel manage — promote or remove members github.com/b7069484/claud…

0 0 0 47 0

View Details

Israel B. Bitton @IsraelBitton

3 months ago

This isn’t a vibes project. Dozens of curated experts across eng, product, design, strategy, legal. Model-tiered by cost: Sonnet deep (~$0.01/member), Haiku scans (~$0.001/member), Opus synthesis only. Sessions checkpoint to disk — resumable mid-review, auditable after, fault-tolerant. Quorum is enforced before synthesis ships. Built for real work. Not demos.

1 0 0 45 0

View Details

Israel B. Bitton @IsraelBitton

3 months ago

CLAUDE CODE USERS Research is clear: multi-expert reasoning makes LLMs +8.69% more truthful. Debate-style prompting cuts hallucinations. (EMNLP + ICML, 2026.) Everyone agrees. Almost nobody does it. Because building a committee from scratch — every session, every deliverable — takes longer than the decision itself. Pick 8 experts. Write 8 personas. Keep them in character for 40 turns. Remember who said what. Reconcile the contradictions yourself. And then re-do the whole scaffolding tomorrow for the next thing. Until now. 🧵

1 0 1 398 0

View Details

Israel B. Bitton @IsraelBitton

4 months ago

@claudeai Did you dumb opus 4.6 down in the process? Not sure if it’s just me but wow has Claude Code been thick and stupid today! Extended to a million tokens but it forgot basic things in process long before reaching anywhere close to 40% context window usage. @bcherny perhaps you know?

3 0 2 398 0

View Details

Israel B. Bitton @IsraelBitton

4 months ago

@DrTedros @AliVaez What about firing rockets indiscriminately into population centers? 🤔 Ah yes, “War crimes for thee, but not for me!”

0 0 0 17 0

View Details

Israel B. Bitton @IsraelBitton

4 months ago

@EmmanuelMacron

0 0 0 96 0

View Details

Israel B. Bitton @IsraelBitton

4 months ago

@ianbremmer @ezralevant Can Europe respond faster?

0 1 17 2K 0

View Details

Israel B. Bitton @IsraelBitton

4 months ago

@vonderleyen

0 0 0 859 0

View Details

Dov Hikind @HikindDov

4 months ago

It’s past time, Mr. President. Time for a divorce. Tucker Carlson is not your friend. He is a danger to our country and all that is good about who we are. Cut ties with this man. I believe you know deep down it’s the right thing to do. It’s time, Mr. President. Let him spew his trash as he pleases, but it’s time you removed this particular piece of trash out of our White House.

1K 389 2K 27K 45

View Details

Dov Hikind @HikindDov

6 months ago

Always proud to share work by the immensely talented Israel Bitton. You’ll be amazed at what’s contained in this thread and if you’ve seen any work of his in the past, you know it’ll be worth every moment. Use link below to view dashboard. pw-dashboard.lovable.app Trust me on this one and check it all out.

Israel B. Bitton @IsraelBitton

6 months ago

WARNING: A new blood libel is spreading right now. Patagonia wildfires are being blamed on “Israeli tourists” or “IDF soldiers” with no identification, no evidence chain, and no official confirmation. This is scapegoating at the speed of algorithms. 1/12 🧵

4 5 16 3K 2

0 2 6 888 1

View Details

Israel B. Bitton @IsraelBitton

6 months ago

12/12 If you want to explore this incendiary case of anti-Jewish propaganda, check out pw-dashboard.lovable.app and review the collected data exposing this pernicious blood libel that has spread like literal wildfire.

0 1 2 98 0

View Details

Israel B. Bitton @IsraelBitton

6 months ago

11/12 We need a new posture: stop arguing the rumor and start exposing the pipeline. Document the seed posts, the super-spreaders, the blog loops, the repeated phrases, and the engagement spikes. If you saw early posts, reply with links and timestamps.