Autonomous Growth Cockpit for Ivy-Tendril powered by local Antigravity (
agy) agents, built with Rust (axum) and Vite+ (vp).
SpaceCorps/GrowthHack is an engineering-grade growth hacking platform designed to scale Ivy-Tendril from ~175 to 100,000 GitHub stars through real developer adoption, automated 10x technical publishing, multi-directory submission blitzes, and real-time trend hijacking.
SpaceCorps/GrowthHack/
├── backend/ # High-performance Rust Backend (Axum + Tokio)
│ ├── src/
│ │ ├── main.rs # Axum server entry point (Port 4200)
│ │ ├── config.rs # Autodetects local agy.exe & environment
│ │ ├── db/mod.rs # Data persistence (Issues, Articles, Trends, Listings)
│ │ ├── agent/ # Local Antigravity CLI runner & SSE stream broadcaster
│ │ └── api/ # REST API endpoints
│ └── Cargo.toml
├── frontend/ # Modern Cockpit Frontend (Vite+ / vp, React 19, Tailwind)
│ ├── src/
│ │ ├── views/ # IssuesHub, ArticleEngine, TrendRadar, ListingBlitz, AgentConsole
│ │ ├── components/ # Navigation, LiveTerminal, ArticleModal
│ │ └── main.tsx
│ ├── vite.config.ts
│ └── package.json
└── README.md
- [ISSUE-01] Daily 10x Feature Article Engine (10 articles/day): Rotates through core Tendril capabilities (Worktrees, Multi-Agent, Issue-to-PR, Verification Gates, Voice, Tunneling) across 6 content archetypes with mandatory 3+ external authority citations and Tendril backlinks.
- [ISSUE-02] Ecosystem Listing & Awesome-Repo Blitz (50+ targets): Automated submission tracking and PR blurb generator for
awesome-ai-agents,awesome-devtools,AlternativeTo,OpenAlternative,DevHunt, and software factory catalogs. - [ISSUE-03] VS Code & Cursor Companion Extension: Bridges developers directly from their active editor into Tendril background agent worktrees.
- [ISSUE-04] Package Manager & One-Line Install Blitz: Homebrew, winget, scoop, and
npx @ivy-interactive/tendrilfor <60s onboarding. - [ISSUE-05] "Built with Tendril" Pull Request Badge Flywheel: GitHub Action and PR templates embedding verification badges and viral backlinks on every PR generated. Includes fork-safe error handling for open-source repositories where
GITHUB_TOKENis read-only on fork pull requests, supporting both single-workflow graceful fallback (suppressing 403 errors with actionable warning notices) and a companionworkflow_runpattern (tendril-comment.yml) that securely posts verification comments on external fork PRs with write permissions. Features automated companion workflow validation and dry-run simulation in CI (tendril-verify.yml) along with on-demand manual testing viaworkflow_dispatch. - [ISSUE-06] Real-Time Social Radar & Technical Discussion Monitor: Scans Hacker News, Reddit (
r/LocalLLaMA,r/programming), and X for agent complaints and auto-drafts helpful technical solutions. - [ISSUE-07] Public Daily "State of Coding Agents" Benchmark Matrix: Automated daily benchmarks of Claude Code vs Codex vs Gemini vs OpenCode in Tendril worktrees (the #1 backlink magnet for tech newsletters).
- [ISSUE-08] Ready-to-Run Workflow Pack & Recipe Hub: 1-click community recipes (
bugfixer,dependency-upgrader,test-generator). - [ISSUE-09] Daily Tech Radar & Trend Synthesizer (GitHub, Reddit, LinkedIn Trending → Website Posts): Autonomous scout that finds hot developer trends and synthesizes them into high-authority website posts with customizable Tendril tie-ins (Direct, Subtle, or Pure Tech Commentary).
- [ISSUE-10] Feature Video Demos & LinkedIn/Social Blitz (SpaceCorps/web-demo-generator): Generates 15-45 second animated UI video demos using
SpaceCorps/web-demo-generator(Playwright headless browser + Claude + H.264 video recorder), paired with high-converting LinkedIn post scripts and video storyboards.
- Rust & Cargo (1.95+)
- Node.js (v24+) & Vite+ (
vpCLI) - Antigravity CLI (
agy) installed atC:\Users\<user>\AppData\Local\agy\bin\agy.exe(or inPATH)
cd backend
cargo runBackend will start on http://127.0.0.1:4200 with real-time SSE streaming.
cd frontend
vp devOpen http://localhost:5173 to access the interactive Cockpit.
Or run production mode where the Rust backend serves the compiled frontend assets directly from frontend/dist.
The Article Engine's "Export to Ivy Web" pipeline writes Markdoc posts and hero images into a local checkout of ivy-web. The backend resolves these two directories in the following order, so no developer-specific path is ever hardcoded:
- Request payload — an explicit
target_dir/target_images_dirpassed on a single export call. - Saved default — an override persisted via
POST /api/settings/export-paths(surfaced in the Cockpit's Export tab as "Save as Default"). IVY_WEB_CONTENT_PATH/IVY_WEB_IMAGES_PATHenvironment variables — set these to pin the paths for your machine without touching the UI. A blank value is treated as unset and falls through to auto-detection.- Auto-detected fallback — the backend probes common relative locations (e.g.
../ivy-web/apps/web-new/content/posts,~/git/ivy-web/apps/web-new/content/posts) and finally falls back to./content/posts/./public/site/images.
GET /api/settings/export-paths returns the currently resolved paths along with which of settings/environment/detected produced each one.
SpaceCorps / Ivy-Interactive Internal.