---
title: "Resource Management"
description: "Managing tokens, credits, and computational resources"
---

---

Verdent for VS Code uses a credit-based system to manage computational resources. Understanding credit usage, quotas, and monitoring helps you optimize performance and manage costs effectively.

---

## Credit & Token Monitoring

### Credit Balance (In VS Code)

Monitor your credit balance through the **User Center** in VS Code:

- Click the User Center button in the top bar of the Verdent panel
- View account name, current plan, and credit balance
- See total credits (subscription + top-ups), credits left in subscription, and remaining top-up credits
- Credit balance updates in real-time as you use Verdent

### Token Usage Monitoring (Website Dashboard)

For detailed token usage analytics and monitoring:

<Steps>
  <Step title="Access Dashboard">
    Visit the [Verdent Dashboard](https://verdent.ai/dashboard) on the official website
  </Step>
  <Step title="View Token Usage">
    Check detailed token consumption across all your sessions and projects
  </Step>
  <Step title="Analyze Patterns">
    Review usage patterns, model selection impact, and cost optimization opportunities
  </Step>
</Steps>

<Info>
  **Credit balance** (available in VS Code User Center) shows your remaining credits. **Token usage details** (available on website Dashboard) show granular consumption analytics for optimization.
</Info>

---

## Plans, Top-Ups, and Billing Cycle

Shared subscription rules now live in [Account & Billing](/docs/account-billing/overview). Use those pages for pricing tiers, top-ups, billing-cycle refresh, and what affects credit consumption across products.

<CardGroup cols={2}>
  <Card title="Credits & Plans" href="/docs/account-billing/credits-and-plans">
    Shared pricing tiers, top-ups, and credit usage basics
  </Card>
  <Card title="Billing Cycle & Rollover" href="/docs/account-billing/billing-cycle-and-rollover">
    Credit refresh timing and rollover rules
  </Card>
</CardGroup>

---

## Managing Long-Running Tasks

Effective resource management requires strategic session planning. See [Best Practices: Context](/docs/verdent-for-vscode/best-practices/context) for detailed guidance on breaking tasks into chunks, monitoring performance, and context window optimization (200K vs 1M tokens).

**Quick Tips:**

- Use Plan Mode for complex changes to understand scope before execution
- Start fresh sessions between major tasks to reset context and tool approvals
- Complete atomic work units (feature → test → commit), then start fresh sessions
- Watch for slower responses or less accurate outputs as sessions grow longer

---

## See Also

<CardGroup cols={3}>
  <Card title="Execution Modes" icon="toggle-on" href="/docs/verdent-for-vscode/execution-modes/overview">
    Understanding execution modes and their resource implications
  </Card>
  <Card title="Best Practices: Context" icon="layer-group" href="/docs/verdent-for-vscode/best-practices/context">
    Context window management and optimization strategies
  </Card>
  <Card title="Configuration Settings" icon="gear" href="/docs/verdent-for-vscode/configuration/settings">
    Configure model and performance presets
  </Card>
</CardGroup>