#Too much cost
1 messages · Page 1 of 1 (latest)
I will need your job ID where you face any issue. You can find it by opening the chat and clicking on the 'i' button in the top right corner. You may have to close the preview to see the button. From the panel that opens, please copy the job ID and share with us.
346bf819-2c6e-4c0b-91cc-5b1937076e89
there is arround 500-600 unreal wasted credit
running health check cost me again 200 credit, the page write 2 -3 credit😩
Upon reviewing your usage, we can confirm that you were operating on Opus 4.6 with a 1M context window.
This configuration is designed for large, complex workflows and long-context reasoning. However, it also consumes significantly more credits because:
- A 1M context window allows the model to process a very large amount of tokens (conversation history, files, logs, instructions) in a single execution.
- The larger the context processed, the higher the token usage.
- Complex multi-file edits, retries, and full-project scans further increase token consumption.
- Opus 4.6 is a high-tier reasoning model, and its per-token cost is higher than lighter models.
How to Reduce Credit Consumption
To optimize usage:
- Use a lighter model for routine or small edits.
- Avoid keeping very long chat histories; fork sessions when they grow large.
- Break large tasks into smaller, scoped instructions.
- Avoid re-running full-project analyses unless necessary.
- Limit large log or file dumps in a single prompt.
Opus 4.6 with 1M context is best reserved for architectural decisions, major refactors, or complex reasoning tasks — not routine iterations.
I understand, but 2 sub agent question 2 agent wake up and 1 health check cost me 600 credit? how can i chnage the context?
Upon reviewing the job activity, we can confirm that the health check execution consumed 178 credits, not 600 as mentioned.
It appears that the health check was triggered via an agent prompt. When you instruct the agent to perform such tasks, it processes the request through the full reasoning workflow, which can consume higher credits depending on context size and execution scope.
For future reference, when an application is deployed, Emergent provides a built-in “Run Health Check” option that is significantly more efficient.
You can access it by:
- Opening the specific job.
- Clicking the Redeploy button from the top-right corner of the dashboard.
- Scrolling down to find the green “Run Health Check” button.
Using this built-in option typically consumes only 4–5 credits, as it runs a lightweight system-level check instead of invoking the full agent reasoning process.
Since the health check was executed via agent prompt in this instance, the credits were consumed accordingly.
It uses 600 credit for:
Health check 1 time
2times question how can I change the context
and 2 wake up agent
Hi
We are currently facing a high volume of support tickets, but you are important to us and so is your query. Your ticket is being reviewed; however, due to the high volume, the time to resolution may be longer than usual.