Introducing Genesis Rewards
Every developer knows the pause: the agent is thinking, the tests are running, the plan is coming together, the next step is almost ready.
Genesis Rewards turns those moments into something useful.
It is a new opt-in experience for developers using AI coding tools in the CLI and VS Code, with a path to approved public developer inventory such as Genesis Reward Badges, package README slots, docs pages, changelog lines, examples, templates, and listings. It can show one quiet sponsored moment during eligible pauses or reviewed public inventory, without reading code, prompts, completions, filenames, raw paths, command contents, terminal output, or transcripts.
The product starts simple: install the client, sign in, turn it on, and keep working in Codex, Claude Code, OpenCode, generic CLI sessions, or VS Code. Genesis stays out of the way until there is an approved rewards moment. For public developer surfaces, Genesis uses approved inventory units and opaque inventory IDs so runtime reward events do not carry repository names, package names, raw URLs, source, prompts, transcripts, or workspace details.
Rewards are not guaranteed. Estimated balances are not payable balances. Credits stay pending until eligibility, duplicate-session review, fraud review, event reconciliation, payout setup, and program availability are complete.
What Developers Can Test
- Install and initialize the Genesis Rewards CLI.
- Wrap Codex, Claude Code, OpenCode, or a generic CLI command in a disabled-by-default flow.
- Use the VS Code status-bar extension for local reward state.
- Preview approved public inventory units for Genesis Reward Badges, package README
- slots, docs pages, changelog lines, examples, templates, and listings.
- Follow environment-specific onboarding for local CLI, VS Code, Remote-SSH,
- devcontainers, tmux, Codex, Claude Code, OpenCode, and generic CLI tests.
- Send feedback through the private cohort channel or Genesis contact route with
- redacted session IDs and environment details only.
- See signed-out, disabled, pending-review, duplicate, capped, and paused states.
- Confirm that duplicate windows, panes, wrappers, and extension hosts do not
- multiply payable activity.
- Validate that source code, prompts, completions, chat history, filenames, raw
- paths, command contents, terminal output, transcripts, secrets, credentials,
- and private files are not sent to Genesis.
What Must Stay True
Sponsored placements should not be presented as host-tool, model, editor, or developer endorsements unless a separate approved relationship exists. The Genesis Rewards client keeps placements separate from prompts, completions, source code, and terminal output.
Developer traffic is also subject to fraud and quality review. Automated sessions, forced engagement, manipulated wait-state signals, duplicate windows, duplicate panes, duplicate wrappers, hidden impressions, and other invalid activity can delay, reduce, or block rewards.
Payout Caveats
Reward reporting may include estimated, pending, confirmed, payable, and paid states. Estimated and pending values can change after duplicate-session review, invalid traffic review, advertiser settlement, refunds, disputes, payout holds, tax setup, or program availability changes.
The goal is simple: give developers a tasteful way to benefit from the time they already spend with AI coding tools, while keeping the work private and the experience quiet.