yukta / web
CLAUDE.md1 starsChanged 20 days agoApache-2.0View on GitHub
In this repository21 other files it gives its agents.
- architecture/CLAUDE.mdCLAUDE.md
- boot/CLAUDE.mdCLAUDE.md
- build-logic/CLAUDE.mdCLAUDE.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- cli/CLAUDE.mdCLAUDE.md
- core/CLAUDE.mdCLAUDE.md
- mcp/CLAUDE.mdCLAUDE.md
- messaging/CLAUDE.mdCLAUDE.md
- plugin-api/CLAUDE.mdCLAUDE.md
- plugins/CLAUDE.mdCLAUDE.md
- plus/CLAUDE.mdCLAUDE.md
- ui/CLAUDE.mdCLAUDE.md
- ide-index-mcpSkill
- pickupSkill
- playwrightSkill
- testsSkill
- ticketSkill
- yuktaSkill
- yukta-supervisorSkill
- yukta-workflowsSkill
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 35
Follow the tiered "Test Execution Policy (speed)" in the root CLAUDE.md: run --tests for the classes you changed first.
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Web Module CLAUDE.md
Overview
Web layer with REST controllers and UI support.
Build & Development Commands
# Run web tests
yk gradle :web:testPatterns
- Controllers return
Mono<ApiResponse<T>>(or aFluxofServerSentEvent). They never catch errors: core throwsNotFoundException,GlobalExceptionHandlermaps the status. - Execution routes live at
/api/executions/{id}/…; the/api/workflow/…paths are deprecated aliases. UseExecutionAccessfor session-ownership checks,Paginationfor lists andSseStreamsfor SSE. GET /api/plugins/{type}includesconfigSchema;POST /api/sessions/validatedry-runs a draft workflow withWorkflowValidator(always 200,valid=falseplus the first problem) and returns each node's output ports;GET /api/sessions/{id}/configreturns the full config in the shapePOST /api/sessionsaccepts./api/supervisor-enginesis the engine catalog (/{type},/{type}/presets) and/api/supervisorsthe configured supervisors, their/{id}/assignments(GET,PUT,/check; only MANUAL ones are writable, DEFINITION and SYSTEM give 409;409 OWNERSHIP_CONFLICTnames the other owner),/validate,/decisions,/{id}/versions,/rollback,/replay,/{id}/engine/rules(GET/PUTthe rules document of arulessupervisor, andPOST .../replaya draft; common settings stay, 409 for another engine; the logic isSupervisorRulesin core, shared with MCP) (SupervisorsController,SupervisorTypesController).GET /api/supervisors/statuslists the running supervisors (SupervisorHost.status(): id, kind, type, dry-run, and applied/rejected/recorded/dropped command counts since startup); the UI shows it on the Control page./api/agent/v1/**is the agent API of thehttpengine (AgentApiController,AgentCredentialFilter; a supervisor credential only, never a person's key) and/api/agent/v1/mcpits MCP form (AgentMcpController).yukta.api-keys(optional) guards/api/**and the actuator (except/actuator/health); the server binds to loopback unlessYUKTA_SERVER_ADDRESSis set, and refuses to start on another address without a key (ExposureGuardin boot).yukta.api-keys[i].{name,key,role,sessions}define the keys, each with a role:VIEWER(GET only),OPERATOR(also POST/DELETE under/api/executions/and/api/workflow/),ADMIN(everything, including sessions/workflows, scheduler limits, raw node commands and the actuator). A key is plain text orsha256:<hex>; several keys at once allow rotation. A key withsessionsreaches only/api/sessions/{s}/**,/api/workflow/{s}/**and/api/executions/{id}/**(runs in those sessions only). A role or session that does not allow a request gets 403; with named keys the control audit records the actorkey:<name>. The path is matched after decoding;;, encoded/ \ . %,//and dot segments give 400 (RequestPaths).HostOriginFilter(only without a key) answers 403 to a Host that is not loopback /yukta.allowed-hosts, and to a non-GET whose Origin is not the Host /yukta.allowed-origins. MCP (McpEndpointFilter) uses the same keys and checks eachtools/callagainst the key:VIEWERreads,OPERATORalso starts and controls,ADMINdoes everything (McpToolAccess); a session-limited key needs asessionIdof its own.GET /api/workflow/{s}/historytakesworkflowId,status,text(in the execution id),sinceanduntil(start time, ISO date-time) before it pages (HistoryFilter).GET /api/executions?sessionId=&limit=&workflowId=&status=&text=&since=&until=searches the runs of all sessions, newest first (ExecutionSearchController; each session's history is bounded byyukta.execution-log.retained-runs; a key limited to sessions cannot use it).- Input requests (
InputRequestsController, backed byInputRequestQueriesin core):GET /api/sessions/{s}/inputs?state=&workflowId=&executionId=&limit=&cursor=(VIEWER, newest first, defaultstate=OPEN,ESCALATED, unknown state 400),GET /api/executions/{e}/inputs/{id}(with the answer once answered),POST .../answer({decision, text?, data?, rationale?, expectedVersion?}) andPOST .../escalate({reason, advice?}) under/api/executions/so OPERATOR and session keys work as for other run controls. A request of another run is 404; answered is 409 witherrorsdecisionandresponder; expired or cancelled 409;InputForbiddenException403 witherrorsrule; wrong shape 422;InputLimitException429; standby 503. The legacy/signaland/approvalsstay until #1805. GET /api/control/audit?limit=&executionId=lists the newest control commands from the execution log (applied or refused, with the actor); the UI shows it on the Control page.GET /api/events/streamenvelopes carry aseverity(EventSeverity:ERRORfor a failed node/run or an error line,WARNfor a rejected command, cancelled node/run or warning line, elseINFO);?severity=WARNsends that and above.?type=takes a comma-separated list ofEventsController.TYPES(case-insensitive); an unknown name is a 400 that lists the valid ones. Each envelope also carriesrootExecutionIdanddepth(the run's place in its tree of sub-workflow runs; a run without a parent is its own root at depth 0). Log lines are rated by keyword (ponytail:inEventSeverity), so a plugin that reports a level should replace it.- MapStruct: Used for DTO mapping (
AppConfigMapper).
Key Files
- Controllers:
src/main/java/com/infenia/yukta/controller/ - Mappers:
src/main/java/com/infenia/yukta/mapper/ - Module guide:
../docs/contributing/modules/web.mdx(module guide); open risks, bugs and review findings: GitHub issues labelledweb(gh issue list -l web; risks also carryrisk); evolution path and quality lenses:../design/assessments/web.md
Imports
@.claude/rules/coding-standards.md @.claude/rules/git-workflow.md
Testing speed
Follow the tiered "Test Execution Policy (speed)" in the root CLAUDE.md: run --tests for the classes you changed first; full :web:test only when many files changed.
GET /api/sessions/{s}/workflows/{w}/versionslists the saved versions of a workflow (newest 20, newest first);POST .../rollback?version=<id>makes one current again (saved as a new version, workflow prepared again).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

