Skip to Content

Dev server

The agent reads the dev server's config, module graph and served code through the server plugin.

The built-in server plugin lets the agent ask the dev server about itself: its resolved config, where it listens, how an import resolves, a file's place in the module graph, and the code it serves. It can also open a file in your editor.

The agent calls these as code-mode tools (server_config, server_urls, server_resolve, server_graph, server_transform, server_restart, and open). You call the same methods from a terminal with conciv plugin call server.

Methods

Prop

Type

conciv plugin call server config
conciv plugin call server urls
conciv plugin call server resolve --data '{"spec":"@/components/Header","importer":"src/routes/index.tsx"}'
conciv plugin call server graph --data '{"file":"src/routes/index.tsx"}'
conciv plugin call server transform --data '{"url":"/src/main.ts"}'
conciv plugin call server open --data '{"file":"src/routes/index.tsx","line":12,"column":4}'

Restart

Restarting the dev server is the server_restart tool only: it has no RPC method, because it asks you first. The agent calls it with force: true for a full restart.

Errors

typeCause
BUNDLER_UNAVAILABLENo dev server is attached to conciv.
BUNDLER_FAILEDThe dev server failed the request. data.message holds its message.

config and urls fail only with BUNDLER_UNAVAILABLE. open never fails this way: it needs no dev server.

On this page