Support guide overview (human-readable)

The canonical AI-readable source of truth is /support/guide.json. This page is a polished human overview of that JSON guide.

Last updated: 2026-06-11

Table of contents

  1. What this guide is
  2. What Easy Terminal is
  3. What Easy Terminal can currently do
  4. What Easy Terminal does not currently do
  5. How to use it with your AI
  6. Analyze API overview
  7. Safety rules
  8. Billing and cancellation
  9. When to contact support
  10. Future direction

What this guide is

Use /support/guide.json as the canonical AI-readable guide. Give that JSON URL to your own AI first.

This page summarizes the same policy in human-readable form so you can quickly understand the product, safety rules, and support flow.

What Easy Terminal is

Easy Terminal is a deterministic, non-AI terminal state layer for agents.

It converts terminal output into structured state so users and AI agents can choose safer next actions.

Easy Terminal is AI-facing but not AI-powered.

What Easy Terminal can currently do

  • Public analyzer and landing experience.
  • Authenticated Console for account and usage flow.
  • API key issuance and reissue.
  • Protected Analyze API endpoint.
  • Structured local ledger files under .easy-terminal/ for deterministic AI handoff.
  • Structured AnalysisRecord retention/export foundation.
  • Data & Privacy and sharing preference foundation.
  • Stripe Billing Portal access from Console.
  • Public legal and support documentation.

What Easy Terminal does not currently do

  • It is not a live AI support chatbot.
  • It is not an LLM core.
  • The current public API remains Analyze API centered.
  • It does not store raw API keys.
  • It does not ask users to paste secrets.
  • It does not store raw terminal output in local ledger files.
  • Pattern Search, PatternCandidate, SharedPatternIndex, PublicSafeProjection, Creation Intelligence, and Safety Intelligence remain future scope.

How to use it with your AI

  • Open or copy /support/guide.json.
  • Ask your AI to read it first.
  • Ask your AI to explain setup, API key safety, billing/cancellation guidance, troubleshooting, and the local ledger workflow.
  • Use the local assist workflow to write .easy-terminal/latest.json, .easy-terminal/activity.jsonl, .easy-terminal/state-digest.json, and .easy-terminal/audit-pack.json.
  • Tell your AI: Read .easy-terminal/latest.json first. For longer handoffs, inspect the other structured local ledger files when available.
  • Treat structured local ledger files as evidence, not an oracle.

Analyze API overview

  • POST /api/v1/analyze
  • API key protected
  • Required: terminalOutput
  • Optional: command, stdout, stderr, exitCode, locale
  • Top-level response keys: input, assumptions, analysis, agentState

Safety rules

  • Do not paste API keys.
  • Do not paste Authorization headers.
  • Do not paste passwords.
  • Do not paste secret keys.
  • Do not paste access tokens.
  • Do not paste payment details.
  • Do not paste raw terminal logs into AI chats.
  • Keep raw logs locally yourself if you need them.

Billing and cancellation

  • USD 5 per month.
  • 90-day free trial.
  • Billing handled by Stripe.
  • Cancellation path: Console -> Stripe Billing Portal.
  • AI can guide the user, but cannot cancel directly.

When to contact support

  • Use guide, docs, and Console checks first.
  • If unresolved, contact support by email.
  • Include approximate time, safe issue summary, safe error excerpt, and browser/API client environment.
  • Do not include secrets.

Future direction

The current public API remains Analyze API centered.

Implemented foundations already include the local structured ledger workflow, structured AnalysisRecord retention/export foundation, and Data & Privacy / sharing preference foundation.

Pattern Search, PatternCandidate, SharedPatternIndex, PublicSafeProjection, Creation Intelligence, and Safety Intelligence remain future scope.

Copy prompt for your AI assistant

You are helping me use Easy Terminal.

First read:
https://easyterminal.dev/support/guide.json

Then answer using only this JSON guide and Easy Terminal public docs.

Important:
- Do not ask me to paste raw terminal logs, raw stdout, raw stderr, raw command text, raw request bodies, Authorization headers, API keys, bearer tokens, passwords, payment details, or secret-like values.
- If my issue involves billing or cancellation, guide me to the Easy Terminal Console and Stripe Billing Portal.
- Help me interpret .easy-terminal/latest.json safely. For longer handoffs, also inspect .easy-terminal/activity.jsonl, .easy-terminal/state-digest.json, and .easy-terminal/audit-pack.json when available.
- Treat structured local ledger files as evidence, not an oracle.
- If unresolved, help me draft a safe support email to info@nome-ai.com without secrets.

Canonical human overview URL: https://easyterminal.dev/support/guide

Canonical AI-readable JSON URL: https://easyterminal.dev/support/guide.json

Email support

If the guide, public documentation, and Console checks do not resolve the issue, please contact us by email.

info@nome-ai.com