Zero-trust AI platform with code reviews, desktop chat, tool packs, and developer libraries.
Your credentials, your GitHub App, your control.
- GitHub Actions Reviewer
- IX Chat (Windows desktop tray app)
- IX Tools (tool packs for chat and integrations)
- CLI tools (setup/auth/ops workflows)
- .NET library
- PowerShell module
- Issue Ops + Project Control
Screenshots below are sourced from current blog/gallery assets and mirrored under Assets/README/ for stable GitHub rendering.
AI PR reviewer for actionable findings, merge-blocking triage, and cleaner review loops.
- Docs: https://intelligencex.dev/docs/reviewer/overview/
- Blog: https://intelligencex.dev/blog/ix-reviewer-in-action/
Picture 1:
Picture 2:
Windows tray chat app with provider/runtime selection and tool-calling support for diagnostics and investigation workflows.
Warning
IX Chat is experimental.
- Use in dev/test environments only.
- Do not use for unattended production operations.
- Keep human review in the loop.
- Docs: https://intelligencex.dev/docs/chat/overview/
- Blog: https://intelligencex.dev/blog/chat-flow-and-options/
- Blog: https://intelligencex.dev/blog/multilanguage-support-in-action/
Picture 1:
Picture 2:
Tool packs for event/AD/system workflows used by IX Chat and custom integrations.
- Docs: https://intelligencex.dev/docs/tools/overview/
- Docs: https://intelligencex.dev/docs/library/tool-packs/
- Blog: https://intelligencex.dev/blog/event-viewer-in-action/
Current packs and representative tools:
| Pack | Representative tools | License | Usage |
|---|---|---|---|
| Event Log (EventViewerX) | eventlog_pack_info, eventlog_channels_list, eventlog_live_query, eventlog_evtx_query |
MIT | Open-source pack; usable in IX Chat and custom integrations. |
| File System | fs_pack_info, fs_list, fs_read, fs_search |
MIT | Open-source pack; usable in IX Chat and custom integrations. |
| Reviewer Setup | reviewer_setup_pack_info, reviewer_setup_contract_verify |
MIT | Open-source pack; usable in IX Chat and custom integrations. |
| Email (Mailozaurr) | email_pack_info, email_imap_search, email_imap_get, email_smtp_send |
MIT | Open-source pack; runtime dependency gated. |
| Office Documents (OfficeIMO) | officeimo_pack_info, officeimo_read |
MIT | Open-source pack; runtime dependency gated. |
| PowerShell Runtime | powershell_pack_info, powershell_environment_discover, powershell_hosts, powershell_run |
MIT | Open-source pack; opt-in by policy due execution risk. |
| ADPlayground | ad_pack_info, ad_domain_info, ad_group_members, ad_search |
Private/commercial | Usable inside IntelligenceX (licensed/private builds) only; not for external/custom-host reuse. |
| TestimoX | testimox_pack_info, testimox_rules_list, testimox_rules_run |
Private/commercial | Usable inside IntelligenceX (licensed/private builds) only; not for external/custom-host reuse. |
| ComputerX | system_pack_info, system_info, system_process_list, system_service_list |
Private/commercial | Usable inside IntelligenceX (licensed/private builds) only; not for external/custom-host reuse. |
Picture 1:
Picture 2:
Project board and issue triage workflows for handling blockers, confidence signals, and follow-up actions.
- Docs: https://intelligencex.dev/docs/project-ops/overview/
- Docs: https://intelligencex.dev/docs/reviewer/projects-pr-monitoring/
- Blog: https://intelligencex.dev/blog/ix-issue-ops-in-action/
Picture 1:
Placeholder (generated visual; to be replaced with real product capture).
Picture 2:
Placeholder (generated visual; to be replaced with real product capture).
Developer-facing interfaces for setup automation, embedding IntelligenceX in .NET apps, and scripting in PowerShell.
- Docs: https://intelligencex.dev/docs/cli/overview/
- Docs: https://intelligencex.dev/docs/library/overview/
- Docs: https://intelligencex.dev/docs/powershell/overview/
- Blog: https://intelligencex.dev/blog/setup-best-practices-for-teams/
Picture 1:
Placeholder (generated visual; to be replaced with real product capture).
Picture 2:
Placeholder (generated visual; to be replaced with real product capture).
The .NET library includes a generic treatment layer for workflows that need to turn private input artifacts into structured AI output. A caller provides a brief, source artifacts, output expectations and optional image-generation settings; IntelligenceX handles prompt construction and provider execution.
using IntelligenceX.OpenAI;
using IntelligenceX.Treatment;
var request = new TreatmentRequest {
Id = "writer-job-2026-05-19",
Prompt = "Read the evidence and produce original publication drafts in Polish.",
Instructions = "You are an independent technology editor. Do not copy source text.",
WorkingDirectory = @"C:\Support\GitHub\NewsIntel\.newsintel\scan\evidence\appleradar",
Inputs = new[] {
new TreatmentInputArtifact {
Id = "writer-job",
Role = "brief",
MediaType = "application/json",
Path = "writer-job.json"
},
new TreatmentInputArtifact {
Id = "evidence-bundle",
Role = "evidence",
MediaType = "application/json",
Path = "evidence-bundle.json"
}
},
Outputs = new[] {
new TreatmentOutputSpec {
Id = "writer-output",
Modality = TreatmentOutputModality.Json,
Description = "Publisher-safe article drafts with source references."
}
},
OutputSchema = new TreatmentOutputSchema {
Contract = "newsintel.writer-output.v1",
Strict = true
}
};
using var client = await IntelligenceXClient.ConnectAsync();
var engine = new TreatmentEngine(new OpenAIChatTreatmentProvider(client));
TreatmentResult result = await engine.RunAsync(request);Local text-like input files such as JSON, Markdown, text, XML, YAML, CSV and HTML can be inlined into the model prompt with a per-file character limit. This keeps private evidence available to the AI writer without making the evidence a public website contract.
Recommended onboarding:
intelligencex setup wizardLocal web setup flow:
intelligencex setup webFrom source:
dotnet run --project IntelligenceX.Cli/IntelligenceX.Cli.csproj -c Release -- setup wizard- No backend service: IntelligenceX runs locally and/or in your GitHub Actions.
- Secrets stay under your control: stored in the environments you own.
- Bring your own GitHub App for identity, permissions, and auditability.
- Workflow changes happen via PRs so setup changes stay reviewable.
- Start here: https://intelligencex.dev/docs/getting-started/
- Reviewer: https://intelligencex.dev/docs/reviewer/overview/
- IX Chat: https://intelligencex.dev/docs/chat/overview/
- Tools: https://intelligencex.dev/docs/tools/overview/
- CLI: https://intelligencex.dev/docs/cli/overview/
- .NET library: https://intelligencex.dev/docs/library/overview/
- PowerShell: https://intelligencex.dev/docs/powershell/overview/
- Project Ops: https://intelligencex.dev/docs/project-ops/overview/
- Security: https://intelligencex.dev/docs/security/
IntelligenceX/: core libraryIntelligenceX.Reviewer/: review pipeline executableIntelligenceX.Cli/: setup/auth/ops commandsIntelligenceX.Chat/: desktop chat app, host, service, clientIntelligenceX.Tools/: in-repo tool packs and contractsDocs/: source docs (published to the website)
Core CI-equivalent build check:
dotnet build IntelligenceX.CI.slnf -c Release
dotnet test IntelligenceX.CI.slnf -c Release
# CI also runs the executable test harness:
dotnet ./IntelligenceX.Tests/bin/Release/net8.0/IntelligenceX.Tests.dll
dotnet ./IntelligenceX.Tests/bin/Release/net10.0/IntelligenceX.Tests.dllIntelligenceX.sln includes Chat/Tools projects for local integration work.
Publish CLI (self-contained portable style):
pwsh ./Build/Build-Project.ps1 -ToolsOnly -Targets IntelligenceX.Cli -Runtimes win-x64 -Frameworks net8.0 -Styles PortableCompatMIT





