wreckit

390 posts

wreckit banner
wreckit

wreckit

@wreckitcc

official account of $wreckit ca: 7BJ6Mogdczju5hGGzpCqEvLVBTdDu6ixGUH3MMHmBAGS

Katılım Ocak 2026
32 Takip Edilen316 Takipçiler
Sabitlenmiş Tweet
wreckit
wreckit@wreckitcc·
Our official $WRECKIT telegram chat is now live. The goal of creating this chat is to foster a community of builders and supporters of our ecosystems. There will be exclusive rewards and announcements to members of this chat. Link below 👇
wreckit tweet media
English
4
8
30
2.8K
wreckit
wreckit@wreckitcc·
In @mikehostetler we trust. The agentic future is happening on Solana.
English
1
6
16
801
FINNT
FINNT@Traderfinn0·
what’s your conviction pick?
English
122
6
57
4.6K
JR5
JR5@JR5_Crypto·
What's the 100x ticker?
English
203
14
101
16K
wreckit
wreckit@wreckitcc·
Infinite Wreckits. Powered by JIDO.
English
4
8
25
1.4K
FINNT
FINNT@Traderfinn0·
What's 1 coin your currently holding that you would never sell?
English
92
2
46
3.9K
JR5
JR5@JR5_Crypto·
Pump and dumps are over. Real projects are up next. Shill me REAL projects.
English
156
0
104
16.7K
shah
shah@shahh·
> Solana will touch $80 > Everyone will say it's dead > Smart people will buy the dip > One last flush, and the people who bought will think they made a mistake. > People will sell and give up > Memes and Solana will bottom out > The retards buy more > Solana rallies to $1,000 and on-chain goes insane > The believers get called lucky (again)
English
160
48
703
58K
PattyIce
PattyIce@patty_fi·
Any safe places to park size for a 40% annual gain?
English
118
9
115
12.2K
wreckit
wreckit@wreckitcc·
@supercontraa Crazy work. And yet you’re still fading $wreckit? I wonder the bias here.
English
0
0
3
89
wreckit
wreckit@wreckitcc·
@funcry Hey, you should check us out then. The ticker is $wreckit. Real builders + tech. Speculation is mostly around JIDO 👀
English
1
1
6
201
funcry
funcry@funcry·
Guys, I don’t want to be a momentum creator for a meme. I want an organic runner where I can clearly see a path to millions and support it along the way. I can very easily tell what can reach $100M and what can’t. If I step in, my target is high. Almost delusionally high.
English
133
7
214
16K
JITTOSHI³ (Gojo arc)
JITTOSHI³ (Gojo arc)@jittoshi·
I've taken @wreckitcc and built an automated workflow to continue working on any repo I want while I am away from my desk or just working on other things. Yesterday I had 3 agents writing code for me while I was out all day. Last night before bed I built out some more functionality for a fully mobile WreckitGO experience (will share diagram for that when its complete). For now, here is a diagram of how my new automated flow works. If you have questions or want to get this setup join the @wreckitcc community. Link below 👇
JITTOSHI³ (Gojo arc) tweet media
English
4
2
13
379
wreckit
wreckit@wreckitcc·
People still don't know about JIDO. Perfect.
wreckit tweet media
English
6
5
18
783
wreckit
wreckit@wreckitcc·
/wreckit
English
0
1
9
296
wreckit retweetledi
JITTOSHI³ (Gojo arc)
JITTOSHI³ (Gojo arc)@jittoshi·
🧵 Just automated my entire overnight dev workflow. Using @wreckitcc with inspiration from @ryancarson automation article (will link below). Here's the setup 👇 Every night at 10:30 PM, an agent reviews all my @AmpCode threads from the past 24 hours. It extracts patterns, gotchas, and decisions I made then updates my AGENTS.md files automatically. At 11:00 PM, Wreckit takes over. It picks the #1 item from my backlog, researches my codebase, writes a detailed plan, breaks it into user stories, implements each one, runs tests, and opens a PR. I wake up to a draft PR ready for review. The magic is the sequencing: 1. Compound review runs FIRST — extracts learnings 2. Wreckit runs SECOND — benefits from fresh context The agent that ships my code at 11 PM is smarter than the one from yesterday because it just learned from my debugging sessions. This is compound engineering: Each unit of work makes the next one easier. Patterns discovered Monday inform Tuesday's implementation. Gotchas hit Wednesday are avoided Thursday. My AGENTS.md went from a static doc to a living knowledge base that grows every night. The stack: → @ampcode as the AI agent → Wreckit for the autonomous research→plan→implement→PR loop → launchd for macOS scheduling → MEMORY.md as a mid-session scratch pad Setup took 30 minutes. ROI is already insane. If you're still prompting → waiting → prompting → waiting, you're leaving mass productivity on the table. Let your agent learn. Let it ship. Review in the morning. Wreckit is open source: github.com/mikehostetler/… @ryancarson article: x.com/ryancarson/sta… token $WRECKIT: 7BJ6Mogdczju5hGGzpCqEvLVBTdDu6ixGUH3MMHmBAGS
JITTOSHI³ (Gojo arc) tweet media
English
6
7
26
2.2K
JITTOSHI³ (Gojo arc)
JITTOSHI³ (Gojo arc)@jittoshi·
Just stepped out for the day. Gym + baby shower + city moves. While I’m out I’ll be adding a @moltbook integration to my app (TBA). All thanks to @wreckitcc and @AmpCode cc:@mikehostetler
JITTOSHI³ (Gojo arc) tweet media
JITTOSHI³ (Gojo arc)@jittoshi

🧵 Just automated my entire overnight dev workflow. Using @wreckitcc with inspiration from @ryancarson automation article (will link below). Here's the setup 👇 Every night at 10:30 PM, an agent reviews all my @AmpCode threads from the past 24 hours. It extracts patterns, gotchas, and decisions I made then updates my AGENTS.md files automatically. At 11:00 PM, Wreckit takes over. It picks the #1 item from my backlog, researches my codebase, writes a detailed plan, breaks it into user stories, implements each one, runs tests, and opens a PR. I wake up to a draft PR ready for review. The magic is the sequencing: 1. Compound review runs FIRST — extracts learnings 2. Wreckit runs SECOND — benefits from fresh context The agent that ships my code at 11 PM is smarter than the one from yesterday because it just learned from my debugging sessions. This is compound engineering: Each unit of work makes the next one easier. Patterns discovered Monday inform Tuesday's implementation. Gotchas hit Wednesday are avoided Thursday. My AGENTS.md went from a static doc to a living knowledge base that grows every night. The stack: → @ampcode as the AI agent → Wreckit for the autonomous research→plan→implement→PR loop → launchd for macOS scheduling → MEMORY.md as a mid-session scratch pad Setup took 30 minutes. ROI is already insane. If you're still prompting → waiting → prompting → waiting, you're leaving mass productivity on the table. Let your agent learn. Let it ship. Review in the morning. Wreckit is open source: github.com/mikehostetler/… @ryancarson article: x.com/ryancarson/sta… token $WRECKIT: 7BJ6Mogdczju5hGGzpCqEvLVBTdDu6ixGUH3MMHmBAGS

English
3
0
10
593
FINNT
FINNT@Traderfinn0·
Small market cap Big potential What's the ticker fam?
English
145
3
80
7.1K