Skip to content

Looking for: DevRel, Growth Hacker, Community partners. Real upside. #417

@mksglu

Description

@mksglu

Read this if you want in early

context-mode is a small open-source MCP plugin doing a real number on AI coding agents. 120,000+ users across npm and the Claude Code marketplace. 98% context window saved per session. Solo built.

It runs on 14 agents: Claude Code, Cursor, Codex CLI, Gemini CLI, VS Code Copilot, JetBrains Copilot, OpenCode, OpenClaw, KiloCode, Qwen Code, Antigravity, Kiro, Zed, and Pi Coding Agent.

The product works. People are downloading it. What is missing is a team.

I am hiring three OSS partners today. DevRel, Growth Hacker, Community. No salary yet, but real credit, real public proof, and a real first offer when context-mode raises.

If you have ever said "I wish I joined that early-stage thing before it blew up", this is that thing, before it blows up.

What context-mode is

context-mode is an open-source MCP plugin that saves AI coding agents around 98% of their context window. It sits between the agent and its tools, intercepts raw output (Bash, WebFetch, Grep, Read, Playwright snapshots, log files), indexes it into a local FTS5 sqlite, and only feeds the agent the chunks it actually searches for. Works across 14 platforms: Claude Code, Cursor, Codex CLI, Gemini CLI, VS Code Copilot, JetBrains Copilot, OpenCode, OpenClaw, KiloCode, Qwen Code, Antigravity, Kiro, Zed, and Pi Coding Agent.

Concrete numbers from the README benchmarks:

Scenario Raw After context-mode Saved
Playwright snapshot 56.2 KB 299 B 99%
GitHub issues batch (20) 58.9 KB 1.1 KB 98%
Access log (500 reqs) 45.1 KB 155 B 100%
Repo research (subagent) 986 KB 62 KB 94%

Over a full session: 315 KB raw becomes 5.4 KB. Session time stretches from 30 minutes to 3 hours.

Where the project actually is

Metric Value Source
Total users 120,000+ stats.json
npm installs 100,000+ stats.json
Marketplace installs 20,000+ stats.json
npm version 1.0.107 npm
Platforms supported 14 README
License Elastic-2.0 (source-available) LICENSE
Funding $0 reality
MRR $0 reality
People building it 1 (me) reality

Repo: https://github.com/mksglu/context-mode
npm: https://www.npmjs.com/package/context-mode
Demo: https://www.youtube.com/watch?v=QUHrntlfPo4

Why I am posting this

I cannot grow this alone. Solo founder. No investors. No marketing budget. The product is shipping, the downloads are climbing, but distribution is one person and that person is also writing the code.

I am looking for three partners. Each one owns a clear surface. Each one has measurable output. Each one ships in public.

This is the part where you ask whether it is worth the bet.

120k users, climbing. 14 agents, growing. Real benchmarks, real users, real product. The thing that is missing is the loud part. If you bring the loud part, we go from 120k to 1M users together. That is the bet.

Before anything else: thank you to the community

None of this happens without the community.

Not the 120,000 users. Not the 14 agents. Not a single line of it.

Every issue someone took the time to open. Every PR for a typo nobody else would have caught. Every DM with a screenshot saying context-mode saved a session at 2am. Every retweet, every comment, every quiet install. Every bug report that made the product less broken than yesterday. Every contributor who shipped a fix while I was sleeping.

I see all of it. I really do.

To everyone who has ever installed context-mode, replied to a thread, opened an issue, sent a PR, filed a bug, or just kept the project tab open while you worked: thank you. Genuinely. Without exaggeration. You are the reason this is here. Every kind word landed. Every honest critique made it better. I will never stop being grateful for that.

The community that got us to 120,000 is the community I want to grow with. The three people who join from this issue are joining a project that belongs to its users first. That is not a slogan, that is the operating principle. We are kind. We answer. We listen. We say thank you. Always.

The three roles

1) DevRel Engineer

You are the face on camera. English. You explain context-mode to people who have never heard of MCP and to people who already ship their own.

Once you are in:

  • Ship at least 2 long-form YouTube videos per month (5 to 12 minutes). Each video shows context-mode doing one specific thing on one specific stack. Real screens, real ctx_stats output, no slideware.
  • Ship 3 to 6 YouTube Shorts per month. Vertical, first 3 seconds is the hook, loop completion matters more than CTR.
  • Run live demos on X Spaces or YouTube live at least once a month.
  • Answer GitHub issues and Discord questions in your own voice. Triage incoming bugs and tag me when something needs core fix.
  • Maintain a public roadmap of upcoming demos so the community knows what is shipping next.
  • Show up at meetups and conferences when we have travel budget. Until then, virtual is fine.

You are not a script reader. You can debug a hook, read TypeScript, install a Cursor plugin without me holding your hand. If a demo breaks live, you fix it on stream.

2) Growth Hacker

You build AI-assisted pipelines that find moments where context-mode actually solves what someone is asking about, then ship a useful reply from a real human account.

Once you are in:

  • Build a listening pipeline (n8n, Lindy, custom Claude or GPT-5 scripts) that scans X, YouTube, Reddit, and HackerNews for keywords like "Claude Code context window", "/compact", "MCP", "context overflow", "FTS5", "agent loop pain".
  • Score and draft replies with an LLM. The bot never posts. A human (you) reviews the queue, edits, and ships from a real aged account.
  • Hold mention rate of context-mode under 30% across all replies. Most replies should be useful even if context-mode did not exist. Three rules before posting: does the OP describe a problem we solve, does the reply teach something, would I post this if context-mode did not exist.
  • Track ban risk. No upvote automation. No follow automation. No duplicate phrasing across accounts. No sock puppets. No posting in r/programming. No LinkedIn Chrome extensions. Cloud IP only on the listening side.
  • Run experiments. A/B reply tone, hook framing, and account voice. Report weekly with what worked, what got throttled, what got engagement.
  • Build the bridge to influencers with the Community lead. They handle the human side, you handle the listening side.

You are an operator, not a content marketer. You read platform ToS. You know the difference between AI-assisted research and AI-pasted spam.

3) Community / Marketing

You own the human side. You know the dev creator graph. You write the launch threads. You move the conversation from passive downloads to active community.

Once you are in:

  • Map the top 50 to 100 creators in dev tooling, Claude Code, MCP, agent infrastructure. Maintain a live spreadsheet with handle, audience size, content cadence, last-touched date, status.
  • Run Discord and the X account. Daily presence. Reply to every mention within 24 hours. Welcome every new contributor. Pin the right threads.
  • Write the LinkedIn and X posts I do not have time for. Founder voice, not HR voice. Numbers, screenshots, and one clear hook per post.
  • Run launches. Every release gets a launch post, a release note thread, and a tagged shoutout to contributors. Coordinate with DevRel on the demo video.
  • Run influencer outreach. You and the Growth Hacker share a target list.
  • Surface user wins. When someone tweets that context-mode saved their session, you find it, retweet it, and ask them for a quote we can use.

You are not a social media manager. You are the project's public memory. You remember every contributor name. You know who is on which release.

What you get now

  • Contributor credit pinned in the README, listed in every CHANGELOG entry
  • Shoutout from the project account on every release
  • A public body of work that speaks for itself in your next interview
  • Direct access to me. Weekly call. Slack DM. No middle layer.

What you get if context-mode raises

  • First offer at market rate for your role
  • Founding-team equity, real numbers on paper, not vibes

What you do not get

  • Salary right now
  • Equity with no math behind it
  • A promise that this works out
  • Anyone holding your hand

How to apply

No DMs. No "hey can we chat". You apply by shipping the deliverable for your role as a comment on this issue. Public, in the open.

Pick exactly one role. Doing all three does not score higher, it shows you cannot pick.

The deliverables below are intentionally small. I am not asking you to work for free. I am asking you to show me you can ship something.

DevRel deliverable (~30 to 60 minutes of work)

Record a 60 second screen recording. Any platform you want: YouTube short, X video, Loom, your own website, anywhere public. Show context-mode doing one cool thing. ctx_stats output, a ctx_batch_execute saving 50 KB, an install on your favorite agent, whatever excites you.

Open camera is a plus but not required. English voiceover or captions.

Drop the link as a comment.

Judged on: can you explain it, do you sound like you understand it, would I send this video to a friend.

That is it. No production value. No subscriber count. No editing tricks. Just show me you can hold a thought and walk through a screen.

Growth Hacker deliverable (~30 to 45 minutes of work)

Find 3 AI, Claude Code, or MCP related YouTube videos posted in the last 30 days with over 1,000 views. Write a useful comment on each.

Mention context-mode only on the videos where it actually solves what the OP is talking about. The other comments are pure value with no plug.

Post a single comment here with the 3 YouTube comment URLs and 2 to 3 sentences on how you picked the videos and decided when to mention us.

Optional flex: drop a link to a tiny script (gist, repo, anything) that does the listening for you. Not required to win.

Judged on: contextual fit of the replies, zero spam signals, clarity of your thinking.

Community / Marketing deliverable (~45 to 60 minutes of work)

Pick 5 creators on X, TikTok, or YouTube who post Claude Code, MCP, or agent tooling content. Any audience size, even 500 followers if their content is good.

For each: handle, profile link, audience size, 1 line on why they fit, 1 personalized DM opener (max 3 sentences, no templates).

Post the table as a single comment here.

Judged on: quality of the picks, personalization of the DMs, evidence you actually watched their content.

Rules

  • One role per applicant. Pick one.
  • 30 days from the day this issue opens. Then I close it and pick.
  • First good one in each track wins. The next two stay in the running for follow-up gigs.
  • AI-assisted is fine. AI-pasted is obvious and disqualifying.
  • All work happens in this thread, in public.
  • If you have questions, ask in a comment. If the format does not work for you, that is also fine.

What I will not do

  • Ask you to work full time without pay
  • Promise vague equity with no math
  • Take more than 5 hours per week of your time before there is real money on the table
  • Treat this as free labor

One last thing

If you have ever wanted to be one of the first three names on a project that is going somewhere, this is that moment.

If you ship something good, you ride this from 120k users to 1M with me.

Worst case: you put a public artifact in the world that people see.

Best case: you are on the team when context-mode defines how AI agents handle context.

Ship something.

Mert

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is needed

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions