---
title: "Send feedback and propose marketplace artifacts"
description: "Tell Axiom what to build or fix, and request a package, node, or flow that doesn't exist yet — from the editor's feedback dialog, the axiom CLI (axiom feedback / axiom propose), or an MCP client. Every submission feeds the roadmap review."
category: guide
surfaces: [canvas, cli]
related: [guides/author-with-claude-code, guides/hosted-mcp-server, reference/cli/axiom-feedback, reference/cli/axiom-propose]
last_reviewed: 2026-07-18
---

# Send feedback and propose marketplace artifacts

Axiom has two ways to hear from you, split by **what you're telling us**:

- **Feedback on the product** — a bug, a feature idea, or general thoughts about
  Axiom itself.
- **A proposal for the marketplace** — a **package, node, or flow you wish
  existed** (or a change to one that does). This is the request that turns "the
  catalog is missing X" into demand we can act on.

Both land in the same review queue and seed our roadmap planning. Nothing here
is public, and nothing is deleted — submissions are kept so we can come back to
them.

## From the editor

Click **Send feedback** in the header (or open the command palette with `⌘K` /
`Ctrl-K` and choose *Send feedback…*). Pick one of four options:

| Option | Use it for |
|--------|------------|
| **Feature request** | Something Axiom should do |
| **Bug report** | Something broken or surprising |
| **General feedback** | Anything else on your mind |
| **Propose a package/node/flow** | A marketplace artifact you wish existed |

Choosing **Propose a package/node/flow** reveals a small extra picker:

- **What kind?** — Node, Package, or Flow.
- **Against an existing artifact? (optional)** — if you're asking us to *extend*
  something that already exists (say, "add pagination to `acme/notion`"), name it
  here. Leave it blank for a brand-new artifact.

Then describe what it should do — for a proposal, its inputs, outputs, and an
example are the most useful things you can give us — and click **Send**.

## From the CLI

The `axiom` CLI mirrors the editor. Both verbs need a prior `axiom login`; the
message can be an argument or piped on stdin, and `--json` prints the persisted
submission.

### Report on the product

```bash
axiom feedback bug     "axiom invoke printed the error to stdout, not stderr — broke my jq pipe"
axiom feedback feature "let axiom search filter by handle so I can find one publisher's nodes"
axiom feedback general "inspect + source is a great combo — I trusted a node in one pass"
```

### Propose a marketplace artifact

```bash
axiom propose node    "refund a Stripe charge by id, returning the refund object"
axiom propose package "first-class Notion connector (query + append rows)"
axiom propose flow    "new-signup onboarding: create user, send welcome email, seed workspace"

# --details adds the longer shape; --for points at an existing artifact to extend.
axiom propose node "add cursor pagination" --for acme/notion \
  --details "page through database rows; inputs: cursor, page_size; outputs: rows, next_cursor"
```

See the [`axiom feedback`](/docs/reference/cli/axiom-feedback) and
[`axiom propose`](/docs/reference/cli/axiom-propose) reference pages for the full
flag set.

## From an MCP client

If you drive Axiom through the [hosted MCP server](/docs/guides/hosted-mcp-server),
the **`axiom_propose`** tool submits a package/node/flow proposal — the same review
queue as the CLI and editor. It is **propose-only**: an agent can request a missing
artifact (the highest-signal moment is right after `axiom_search` turns up nothing
for a real task), but product bug reports and feature requests stay with a human,
through the CLI or the editor, because they need human judgment to reproduce.

## What happens next

Every submission goes to Axiom's review queue and feeds roadmap planning. Today
proposals are reviewed centrally by the Axiom team — they are **not** yet routed
to the author of the package you named in `--for`; that's on the roadmap. The best
proposals read like a spec: what the artifact does, the inputs it takes, the
outputs it returns, and a concrete example of when you needed it.