How jaykwok/artex works
ARTEX is a self-hosted AI penetration-testing system with a Go backend and Next.js interface. Users configure a task and its scope; the backend coordinates exploration agents that use tools to investigate assets and record findings, while traffic capture, evidence, approvals, and reports support review. The UI also exposes task execution, findings, traffic, and system configuration. Edges are limited to relationships shown by the README or SOURCE INDEX references; several important subsystems are represented from documented capabilities and the file tree, without asserting unsampled internal call chains.
Main entry points: server.go HTTP API · worker.go Intent worker · sqlite.go Business SQLite · manager.go Task manager
Components 20
User interface
- Task workspace
web/src/app/(main)/function/tasks/page.tsx - Findings UI
web/src/app/(main)/function/findings/page.tsx - Human-in-loop chat
web/src/app/(main)/chat/page.tsx - HTTP API
server/server.go
Exploration runtime
- Task manager
server/manager.go - Exploration engine
server/engine.go - Intent planner
agent/planner.go - Intent worker
agent/worker.go - Agent tools
agent/tools.go - Long-running tools
internal/toolrun/manager.go - Remote MCP
mcphttp/client.go
Evidence and review
- Finding records
db/findings.go - Finding reports
report/findings.go - Traffic capture
traffic/traffic.go - Evidence store
evidence/store.go - Command approvals
intercept/intercept.go
State and integrations
- Business SQLite
db/sqlite.go - LLM recordings
llmrec/llmrec.go - ScopeSentry sync
server/sync_scopesentry.go
Other components
- Operator
Connections 23
- Operator → Task workspace: manages tasks
README.md - Task workspace → HTTP API: requests task data
- Findings UI → HTTP API: requests findings
- Human-in-loop chat → HTTP API: sends chat
- HTTP API → Task manager: uses manager
server/server.go - HTTP API → Exploration engine: uses engine
server/server.go - Task manager → Business SQLite: persists state
README.md - Exploration engine → Intent worker: runs worker steps
server/engine.go - Intent worker → Business SQLite: reads and writes
agent/worker.go - Intent worker → Command approvals: gates tool calls
agent/worker.go - Intent worker → Agent tools: uses tools
agent/tools.go - Exploration engine → Intent planner: runs planner
- Agent tools → Long-running tools: delegates async runs
- Agent tools → Remote MCP: invokes remote tools
- Intent worker → Finding records: records findings
- HTTP API → Finding reports: serves finding reports
server/server.go - Task manager → Traffic capture: starts capture proxy
server/manager.go - Evidence store → Traffic capture: references traffic
evidence/store.go - LLM recordings → Business SQLite: stores usage
llmrec/llmrec.go - HTTP API → ScopeSentry sync: exposes asset sync
- ScopeSentry sync → Business SQLite: imports scoped assets
README.md - Operator → Findings UI: reviews findings
README.md - Operator → Human-in-loop chat: steers exploration
README.md