Troubleshooting

Start with the checks below before changing organization settings. Keep the machine connected while testing so recent configuration and activity can reach the Console.

The agent does not appear in the Console

Run:

~/.gesta/bin/gesta-agent status

Then check:

1. the installation command came from the expected Gesta organization;
2. the command was run as the employee who uses Codex or Claude Code;
3. the machine can reach the Gesta URL shown in the Connect dialog;
4. the connect token was prepared for the current user;
5. the runtime is still running;
6. the Console is showing the expected organization.

Open Connect again and compare the current user and connected-machine summary. If needed, rerun the current installation command for the same employee.

The runtime is degraded or Last seen is old

• Run gesta-agent status.
• Confirm that the machine is online.
• Confirm that company networking, VPN, DNS, or proxy settings allow access to Gesta.
• Reopen the machine details in Observability → Agents.
• Rerun the current Connect command if the Console recommends a newer runtime.

After recovery, confirm that Last seen advances.

A Context Rule does not apply

Check:

• the rule is Active;
• its Agent setting includes the employee's agent;
• the prompt contains the expected keyword or matches the expression;
• the rule content is not empty;
• the connected machine has synchronized recently;
• the employee started a new agent session after installation or integration changes.

Use a direct, safe test prompt that clearly matches the trigger. Confirm the rule's match count or Last matched value after the test.

A Context Rule applies too often

• Replace broad keywords with more specific phrases.
• Use a regular expression when several conditions must appear together.
• Split unrelated expectations into separate rules.
• Disable the rule while revising it if it disrupts normal work.
• Test against both matching and non-matching prompts before reactivation.

An Operational Policy does not match

Check the rule status, Agent value, command expression, and recent synchronization time. Test the expression with harmless examples before trying it against a real operation.

If an approval remains pending, confirm that an authorized Owner has opened the request and selected Approve or Deny. See Review approval requests.

A prompt is blocked unexpectedly

Open Security → Sensitive Data and inspect the finding:

• matched rule;
• category and severity;
• detector pattern;
• source;
• configured outcome.

Use synthetic content to reproduce the match. Narrow the detector only after confirming that the change will not expose the protected data category.

A session does not appear in My Activity

• Confirm the machine appears under your employee identity.
• Start a new session or add new activity after the runtime is connected.
• Perform a supported agent action and wait briefly for activity ingestion.
• Confirm that My Activity is showing the current user.
• Ask an Owner to check whether the same session appears under Team Activity.

Installation does not import existing session history. See Existing session history for that boundary.

A Recap is not available

Recap availability and selection use a separate processing path from My Overview. Follow the canonical checklist in Understand daily recaps.

Information to collect for support

Provide:

• organization name;
• affected employee;
• hostname;
• operating system;
• Gesta runtime version;
• agent type and version;
• approximate time of the problem;
• the visible error message;
• relevant rule name or session ID.

Do not include connect tokens, credentials, private keys, raw customer data, or other secrets.

For short answers to common product questions, see Frequently asked questions.