How to Get Support for Semantica AGI: Documentation, Community, and Enterprise Channels

Semantica AGI offers a tiered support ecosystem including self-service documentation in docs/, community help via GitHub Discussions and Discord, structured issue tracking with templates, and private enterprise assistance through dedicated email channels.

Semantica AGI (semantica-agi/semantica) provides multiple pathways for assistance, ranging from comprehensive markdown documentation to real-time chat and SLA-bound commercial support. Whether you are troubleshooting a pipeline configuration in semantica/pipeline/pipeline_usage.md or reporting a security vulnerability, the repository contains specific protocols and contact methods to ensure timely resolution.

Self-Service Documentation

The fastest way to resolve questions is through the extensive markdown guides located in the repository's docs/ directory. These files cover everything from basic setup to advanced API usage.

For programmatic verification of your installation, you can check the client version:

from semantica import Semantica

client = Semantica()
print("Semantica version:", client.version())

This snippet references semantica/__init__.py, where the Semantica class is implemented.

Community Support Channels

For interactive assistance, Semantica AGI maintains two primary community platforms.

GitHub Discussions

Use GitHub Discussions for open-ended questions, architecture advice, and sharing implementations.

This forum is ideal for peer-to-peer assistance and capturing knowledge for future users.

Discord

For real-time troubleshooting and informal chat, join the Discord server:

Developers often share tips and rapid feedback in this channel. You can also launch an interactive bot locally using the CLI:

semantica discord --token $DISCORD_BOT_TOKEN

This command is implemented in semantica/cli.py.

Bug Reports and Feature Requests

Structured issue tracking ensures maintainers receive complete context. The repository uses GitHub Issues with specific templates.

Issues are typically acknowledged within 48 hours. Before submitting, run the built-in diagnostics to collect environment details:

semantica diagnostics --output diagnostics.json

This utility, defined in semantica/cli.py, generates a diagnostics.json file containing version and environment data that should be attached to your report.

Security Disclosures and Enterprise Support

Critical issues requiring confidentiality follow distinct paths from public issue trackers.

Security Vulnerabilities

Never use public GitHub Issues for security bugs. Instead, email the security team directly at kaif@getsemantica.ai with the subject line prefixed by [SECURITY]. The disclosure process is detailed in SECURITY.md. You will receive a guaranteed response within 24 hours and confidential handling throughout the resolution process.

Enterprise Support

For SLA-bound assistance, custom development, or consulting, contact the team at kaif@getsemantica.ai with the subject line prefixed by [ENTERPRISE]. This channel provides dedicated support, potential paid plans, and tailored solutions for production deployments.

Pre-Request Best Practices

Before opening a new support request, follow this workflow to expedite resolution:

  1. Search the documentation in docs/concepts.md, docs/cookbook.md, and docs/faq.md for relevant explanations.
  2. Review existing GitHub Discussions and Issues for similar problems.
  3. Test relevant example code from docs/cookbook.md or semantica/pipeline/pipeline_usage.md to isolate the issue.
  4. Select the appropriate channel from the tiers above based on sensitivity and urgency.

Summary

  • Self-service: Browse docs/getting-started.md, docs/concepts.md, docs/cookbook.md, and docs/faq.md for immediate answers.
  • Community: Post questions in GitHub Discussions or join the Discord at https://discord.gg/sV34vps5hH for peer assistance.
  • Issues: Use templated GitHub Issues for bugs and features, expecting acknowledgment within 48 hours.
  • Security: Email kaif@getsemantica.ai with [SECURITY] prefix for vulnerabilities, guaranteed 24-hour response.
  • Enterprise: Email kaif@getsemantica.ai with [ENTERPRISE] prefix for commercial support and SLAs.
  • Diagnostics: Use semantica diagnostics --output diagnostics.json (implemented in semantica/cli.py) to gather system info before reporting bugs.

Frequently Asked Questions

How do I report a security vulnerability in Semantica AGI?

Email kaif@getsemantica.ai with the subject line starting with [SECURITY]. Do not use public GitHub Issues for security disclosures, as detailed in SECURITY.md. The team guarantees a response within 24 hours and will handle the report confidentially.

Where can I find working code examples for Semantica AGI?

The docs/cookbook.md file contains hands-on examples and common workflows. Additionally, semantica/pipeline/pipeline_usage.md provides specific pipeline implementations. For API reference, consult docs/reference/core.md which documents the Semantica class.

What is the typical response time for community support requests?

GitHub Issues receive acknowledgment within 48 hours. Security disclosures sent to kaif@getsemantica.ai receive a guaranteed response within 24 hours. Community channels like Discord and GitHub Discussions operate asynchronously based on volunteer availability.

How do I verify my Semantica AGI installation before requesting help?

Run the diagnostics command semantica diagnostics --output diagnostics.json from semantica/cli.py to generate an environment report. You can also verify the client initialization by running:

from semantica import Semantica
print(Semantica().version())

This confirms your environment matches the supported configuration described in docs/getting-started.md.

Have a question about this repo?

These articles cover the highlights, but your codebase questions are specific. Give your agent direct access to the source. Share this with your agent to get started:

Share the following with your agent to get started:
curl -s "https://instagit.com/install.md"

Works with
Claude Codex Cursor VS Code OpenClaw Any MCP Client

Maintain an open-source project? Get it listed too →