ModelContextProtocol

4 replies

@everyone Some big features from recent convexconvex npm releases (1.34, 1.35, 1.36):

- Staging deployments and branch-based development
- Cloud deployments for agents
- Inline queries from the CLI
- Self-aware functions
- and more!

Full changelog.

Staging deployments and branch-based development

Create prod, dev, and preview deployments from the CLI with

npx convex deployment createnpx convex deployment create

Use this for staging environments, per-branch deployments, and more.

npx convex deployment create staging --type prod
# Create a per-branch shared dev deployment
npx convex deployment create $(git branch --show-current) \
  --type dev --select

npx convex deployment create staging --type prod
# Create a per-branch shared dev deployment
npx convex deployment create $(git branch --show-current) \
  --type dev --select

--select--select does the equivalent of npx convex deployment selectnpx convex deployment select, to select the deployment for development.

Docs on multiple deployments.

Related: preview deployments will now be re-used by default (instead of re-created).

Default environment variables

Did you know you can set default environment variables, so new dev/preview/prod deployments start with the right values? Now you can manage them from the CLI with

npx convex env default get/set/listnpx convex env default get/set/list

These match npx convex env get/set/listnpx convex env get/set/list, but operate on environment defaults.

Agentic development

Cloud deployments for agents

Create cloud deployments from a git worktree setup script with auto-expiration:

# Create a new deployment and select it for development
npx convex deployment create --type dev --select \
  team-slug:project-slug:dev/$USER/$(basename $PWD) \
  --expiration "in 5 days"

# Create a new deployment and select it for development
npx convex deployment create --type dev --select \
  team-slug:project-slug:dev/$USER/$(basename $PWD) \
  --expiration "in 5 days"

For local deployments, setup has gotten easier. We'll automatically set up a local anonymous deployment whenever one isn't set up yet and it's a non-interactive terminal. CONVEX_AGENT_MODECONVEX_AGENT_MODE generally isn't necessary anymore. Just npx convex dev --oncenpx convex dev --once, or if you want to set up env vars before deploying, npx convex initnpx convex init.

AI context files

npx convex ai-filesnpx convex ai-files allows you to add and maintain Convex skills and other context files like AGENTS.mdAGENTS.md / CLAUDE.mdCLAUDE.md without bloating your default prompt.

Human developer ergonomics

We haven’t forgotten about you!

Inline test queries from the CLI

You can now run npx convex run --inline-query 'ctx.db.query("messages").take(5)'npx convex run --inline-query 'ctx.db.query("messages").take(5)' - or define a whole query function with loops and conditionals. This helps make inspecting the database more scriptable, while allowing you to leverage indexes and experiment with syntax that you can directly paste into your functions.

Docs on run —inline-queryrun —inline-query

Running your frontend and backend in parallel

If you’ve cloned a template or wrangled your own package scripts to start Convex and your local frontend in parallel, you likely saw a mess of predevpredev and run-prun-p / npm-run-all2npm-run-all2. You can now simplify these scripts to just:

"scripts": {
  "dev": "convex dev --start 'vite'",
  ...

"scripts": {
  "dev": "convex dev --start 'vite'",
  ...

--start--start will run a command in parallel to convex devconvex dev once convex devconvex dev has set up your backend and successfully deployed once. It supports passing through interactive I/O and graceful Ctrl-CCtrl-C shutdown.

Deployment messages

On the deployment side, pass --message--message to npx convex deploynpx convex deploy to provide release metadata that will show up in the History tab in the dashboard. If you’re releasing from CI, it automatically infers the git hash (in supported CI environments, like GitHub Actions)

Function metadata reflection

Functions are now more self-aware! Don’t be scared.

ctx.meta.getFunctionMetadata() 
  -> { type: "query", visibility: "public", name: "folder/file:fn" }

ctx.meta.getFunctionMetadata() 
  -> { type: "query", visibility: "public", name: "folder/file:fn" }

Queries and mutations can also now inspect the current transaction metrics, to know how close to limits they are getting:

ctx.meta.getTransactionMetrics()
  -> { bytesRead: { used, remaining }, documentsWritten...

ctx.meta.getTransactionMetrics()
  -> { bytesRead: { used, remaining }, documentsWritten...

Convex Community•4w ago•

4 replies

ian

Staging deployments and branch-based development

Create prod, dev, and preview deployments from the CLI with

npx convex deployment createnpx convex deployment create

Use this for staging environments, per-branch deployments, and more.

npx convex deployment create staging --type prod
# Create a per-branch shared dev deployment
npx convex deployment create $(git branch --show-current) \
  --type dev --select

npx convex deployment create staging --type prod
# Create a per-branch shared dev deployment
npx convex deployment create $(git branch --show-current) \
  --type dev --select

Default environment variables

Agentic development

Cloud deployments for agents

Create cloud deployments from a git worktree setup script with auto-expiration:

# Create a new deployment and select it for development
npx convex deployment create --type dev --select \
  team-slug:project-slug:dev/$USER/$(basename $PWD) \
  --expiration "in 5 days"

# Create a new deployment and select it for development
npx convex deployment create --type dev --select \
  team-slug:project-slug:dev/$USER/$(basename $PWD) \
  --expiration "in 5 days"

AI context files

npx convex ai-filesnpx convex ai-files allows you to add and maintain Convex skills and other context files like AGENTS.mdAGENTS.md / CLAUDE.mdCLAUDE.md without bloating your default prompt.

Human developer ergonomics

We haven’t forgotten about you!

Inline test queries from the CLI

Running your frontend and backend in parallel

"scripts": {
  "dev": "convex dev --start 'vite'",
  ...

"scripts": {
  "dev": "convex dev --start 'vite'",
  ...

Deployment messages

Function metadata reflection

Functions are now more self-aware! Don’t be scared.

ctx.meta.getFunctionMetadata() 
  -> { type: "query", visibility: "public", name: "folder/file:fn" }

ctx.meta.getFunctionMetadata() 
  -> { type: "query", visibility: "public", name: "folder/file:fn" }

Queries and mutations can also now inspect the current transaction metrics, to know how close to limits they are getting:

ctx.meta.getTransactionMetrics()
  -> { bytesRead: { used, remaining }, documentsWritten...

ctx.meta.getTransactionMetrics()
  -> { bytesRead: { used, remaining }, documentsWritten...

Continue the conversation

Join the Discord to ask follow-up questions and connect with the community

Convex Community

Join the Convex Discord! Explore Convex, the backend platform that keeps your app in sync.

16,164 Members

Join

Staging deployments and branch-based development

Default environment variables

Agentic development

Cloud deployments for agents

AI context files

Human developer ergonomics

Inline test queries from the CLI

Running your frontend and backend in parallel

Deployment messages

Function metadata reflection

Staging deployments and branch-based development

Default environment variables

Agentic development

Cloud deployments for agents

AI context files

Human developer ergonomics

Inline test queries from the CLI

Running your frontend and backend in parallel

Deployment messages

Function metadata reflection

Continue the conversation

Convex Community

Continue the conversation

Convex Community

Similar Threads