Feature Requests

The best features in Parallax come directly from people using it to build games. If something is slowing you down, missing, or would make the platform significantly better — we want to hear it.

The fastest way to reach us is the #feature-requests channel on Discord. You can also open a GitHub issue if you prefer a more structured format.

What makes a good request

A clear request gets acted on faster. Before posting, try to answer these three questions:

1. What do you want? Describe the feature in one sentence. Be specific — "better agent" is hard to act on, "agent should remember physics conventions across projects" is actionable.

2. Why do you need it? What problem does it solve for you right now? What are you doing as a workaround? The "why" matters more than the "what" — sometimes there's a better solution to the underlying problem.

3. What does the workflow look like? Walk through how you'd actually use this feature. A short before/after example is more useful than a detailed spec. Even one or two sentences helps.

Submitting on Discord

Post in the #feature-requests channel. Use this rough format:

**Feature:** [one-line description]
**Why:** [the problem you're running into]
**Example:** [how you'd use it]

You don't need to be formal. A clear paragraph works just as well. Other members can react, add use cases, and help refine the idea before it gets picked up.

Talking to other members

• Search before posting — someone may have already raised the same request. Add your use case to their thread instead of starting a new one.
• React to requests you want — a row of 👍 on a post is a clear signal. We look at these when planning.
• Add your angle — if you want the same feature for a different reason, say so. Different use cases strengthen a request.
• Be constructive, not prescriptive — describe the problem you're facing, not the exact implementation. You might know the problem better than anyone, but we often find solutions that work better for the whole platform.

Submitting on GitHub

Open an issue in the Parallax repo with the label feature-request.

GitHub issues are good for requests that are more detailed or technical, where you want a persistent thread to track progress.

Current requests (open for voting)

Agent memory across projects

Give the agent the ability to remember decisions, conventions, and character archetypes across multiple projects in the same workspace.

Use case: I use the same physics conventions in every game I build. I have to re-explain them to the agent each time.

Vote on Discord ↗ · Vote on GitHub ↗

Tilemap editor integration (LÖVE-Tiles / Tiled)

Import .tmx files from the Tiled map editor directly into Parallax and have the agent scaffold the rendering code automatically.

Use case: I already design maps in Tiled — I don't want to re-do that work just to use Parallax.

Vote on Discord ↗ · Vote on GitHub ↗

VS Code extension

A VS Code extension that mirrors the Parallax agent panel, so I can prompt the agent without leaving my editor.

Vote on Discord ↗ · Vote on GitHub ↗

Shader support

The agent understands GLSL shaders for Love2D and can generate/explain them, including the love.graphics.newShader API.

Vote on Discord ↗ · Vote on GitHub ↗