Logs

Connecting your logs lets Dev see what your code does once it's running, not only what it says on the page. When you're chasing a production bug, Dev can look up the errors behind it, tie a trace back to the code that produced it, and check the logs after a deploy to confirm a fix behaves as expected.

DevSpec works with Axiom. You connect it in Project settings → Integrations → Log providers, or from Connect logs on a project's Project setup page. Logs are optional, and you choose exactly which datasets Dev may search.

Why connect your logs

Without logs, Dev can only reason about your code. With Axiom connected, you can ask things like:

• "What errors has the API thrown in the last hour?"
• "Why are checkout requests slow this morning?"
• "Did the fix we shipped stop the timeout errors?"

Dev searches the datasets you've allowed, reads what comes back, and connects it to the code in your repositories. It searches your logs when a conversation calls for it.

Create an Axiom token for DevSpec

Create a token in Axiom that can read only the datasets you want Dev to search. The connect form in DevSpec shows these steps under How to create your token:

1. In Axiom, go to app.axiom.co/settings/api-tokens and click Create token.
2. Give it a name, such as DevSpec. Leave Expiration as None unless you want it to expire. Description and query cost limits are optional.
3. Under Token Permissions, choose Advanced permissions — Custom. Don't use Preset — Terraform.
4. Leave All datasets unticked. Under Individual datasets, find each dataset DevSpec should search and tick only Query → Read. Leave Ingest, Share, Starred queries, Trim, Vacuum and Virtual fields off.
5. Under Org level permissions, tick only Datasets → Read, so DevSpec can list your dataset names for you to pick from. Leave everything else off.
6. Click Create and copy the token. It starts with xaat- and Axiom shows it only once.

DevSpec only reads your logs. It never writes anything to Axiom.

Connect Axiom

Project Maintainers connect log providers.

1. Open Project settings → Integrations → Log providers and click Add provider.
2. In Connect a log provider, fill in:
   • Name: a label for you, such as "Production logs" or "Staging".
   • Environment: Staging or Production. DevSpec strongly recommends starting with a staging account while you evaluate it.
   • Provider: Axiom.
   • API token: the token you created.
3. If your Axiom account is in the EU region, open Advanced (optional) and set API URL (for example https://api.eu.axiom.co). Leave it blank for Axiom's US cloud. Org ID is only needed for a personal Axiom token, not a dataset-scoped API token.
4. Tick the datasets Dev may search (see "Choose which datasets Dev can search" below).
5. Click Connect.

DevSpec checks that it can reach Axiom before it saves the connection. You can connect more than one Axiom account, for example one for staging and one for production. Each connection's card shows its status: Connected, Connecting…, Needs reconnect or Error.

Choose which datasets Dev can search

When you enter your token, DevSpec loads your Axiom datasets under Datasets the AI can search (or click Fetch datasets).

None are selected until you pick them. Tick each dataset Dev is allowed to search, or use Select all and Select none. You must choose at least one before you can connect.

Dev can only query the datasets you selected. A query against any other dataset is refused, even if the token itself could read it. To change the selection later, use Reconnect / rotate token on the connection's card.

Keep in mind that everyone who can ask Dev a question in this project's sessions can ask it to search these datasets. Leave out any dataset your whole project team shouldn't see.

What Dev does with your logs

When a question in a session needs runtime evidence, Dev queries the Axiom datasets you allowed over the relevant time window, summarizes error patterns or traces, and connects what it finds to the code in your repositories. It never changes anything in Axiom.

Your agents don't query your logs through DevSpec; log search is something Dev does.

Rotate the token, change datasets or disconnect

To paste a new token, change the region, or change which datasets Dev may search, a Maintainer clicks Reconnect / rotate token on the connection's card in Project settings → Integrations → Log providers.

• Leave API token blank to keep the current token, or enter a new one to replace it.
• DevSpec reloads your dataset list, so datasets you've added in Axiom since you connected appear. Adjust the ticks.
• Click Save.

If a token expires or is revoked, the card shows Needs reconnect and an icon appears in the project header. Create a new token in Axiom and use Reconnect / rotate token to replace it.

Disconnect Axiom

To disconnect, a Maintainer clicks Disconnect provider on the connection's card, then Disconnect to confirm. Dev stops querying that account's logs. This can't be undone; to use the account again, connect it again. Delete the token in Axiom too if nothing else uses it.

What log searches cost

Dev's log searches are part of its replies. They're charged to your organization's balance with the rest of the reply and count toward your personal allowance, like the rest of the reply. There's no separate charge for having Axiom connected. See Billing, usage and limits.

The queries themselves run on your Axiom account, so they also count toward your usage on your Axiom plan.