Wires all 4 microservice-backed agents into the chat so the LLM can call real services and return session URLs.
Changes
New
src/routes/chat.ts
Added a direct HTTP chat endpoint.
When the LLM calls:
start_interview_session
analyze_resume
start_roleplay_session
compute_qscore
The route executes real service probes and returns live session URLs.
Fixed
src/index.ts
Rivet proxy now forwards requests to the engine at localhost:6420
instead of using registry.handler().
Prevents the:
Runtime already started as runner
conflict.
src/actors/user-actor.ts
receiveMessage() now returns:
{reply,sessions:[]}
Includes per-module session URLs in responses.
docker-compose.yml
Fixed:
Gitea health check port
Port mapping
A2A_ALLOWED_KEY default value
src/config.ts
Added:
resumeServiceUrl
Configured to use port 8002.
Rewritten
prompts/system.txt
Reworked into a conversational step-by-step flow.
Added explicit rule:
CALL THE TOOL IMMEDIATELY
Updated
agents/*.md (6 files)
Updated:
Domain descriptions
Trigger phrases
Agent boundaries
Verified
Agent
Service
Result
Resume (Mira)
resume-builder:8002
Real analysis
Sara
interview-service:8007
Real Gemini session + URL
Emily
roleplay-service:8008
Real roleplay session + URL
Quinn
qscore-service:8000
Real Q-Score (~84)
Outcome
The chat system can now:
Trigger real backend agent services directly from LLM tool calls
Return live session URLs
Maintain structured multi-agent responses
Avoid Rivet runtime conflicts
Support end-to-end conversational workflows across all 4 agents
# Wire All 4 Microservice Agents Into Chat
Wires all 4 microservice-backed agents into the chat so the LLM can call real services and return session URLs.
---
## Changes
### New
* `src/routes/chat.ts`
* Added a direct HTTP chat endpoint.
* When the LLM calls:
* `start_interview_session`
* `analyze_resume`
* `start_roleplay_session`
* `compute_qscore`
* The route executes real service probes and returns live session URLs.
---
### Fixed
* `src/index.ts`
* Rivet proxy now forwards requests to the engine at `localhost:6420`
instead of using `registry.handler()`.
* Prevents the:
```txt
Runtime already started as runner
```
conflict.
* `src/actors/user-actor.ts`
* `receiveMessage()` now returns:
```ts
{
reply,
sessions: []
}
```
* Includes per-module session URLs in responses.
* `docker-compose.yml`
* Fixed:
* Gitea health check port
* Port mapping
* `A2A_ALLOWED_KEY` default value
* `src/config.ts`
* Added:
```ts
resumeServiceUrl
```
* Configured to use port `8002`.
---
### Rewritten
* `prompts/system.txt`
* Reworked into a conversational step-by-step flow.
* Added explicit rule:
> CALL THE TOOL IMMEDIATELY
---
### Updated
* `agents/*.md` (6 files)
* Updated:
* Domain descriptions
* Trigger phrases
* Agent boundaries
---
## Verified
| Agent | Service | Result |
| ------------- | ------------------------ | --------------------------- |
| Resume (Mira) | `resume-builder:8002` | Real analysis |
| Sara | `interview-service:8007` | Real Gemini session + URL |
| Emily | `roleplay-service:8008` | Real roleplay session + URL |
| Quinn | `qscore-service:8000` | Real Q-Score (~84) |
---
## Outcome
The chat system can now:
* Trigger real backend agent services directly from LLM tool calls
* Return live session URLs
* Maintain structured multi-agent responses
* Avoid Rivet runtime conflicts
* Support end-to-end conversational workflows across all 4 agents
- Added workflow job actor to manage job application workflows.
- Implemented agent catalog for various workflow agents.
- Created service agents for interview, roleplay, and Q-Score functionalities.
- Enhanced user authentication to automatically create users if they do not exist.
- Updated configuration to support new LLM provider and API keys.
- Introduced new routes for agent and workflow management.
- Refactored Docker management to improve Gitea admin user creation and token generation.
- Removed deprecated Anthropics SDK integration.
- Added ensureOrg and ensureOrgRepo methods to GiteaClient for centralized organization and repository management.
- Updated main application flow to ensure central Gitea readiness at startup.
- Introduced prompt-loader for dynamic loading of agent modules and system prompts from disk.
- Refactored agent routes to return sub-agent module catalog.
- Modified git routes to interact with a central Gitea instance instead of per-user containers.
- Updated workflow routes to utilize a unified user actor per user, streamlining job application workflows.
- Improved service agent handling with a new lightweight reference type.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Wire All 4 Microservice Agents Into Chat
Wires all 4 microservice-backed agents into the chat so the LLM can call real services and return session URLs.
Changes
New
src/routes/chat.tsAdded a direct HTTP chat endpoint.
When the LLM calls:
start_interview_sessionanalyze_resumestart_roleplay_sessioncompute_qscoreThe route executes real service probes and returns live session URLs.
Fixed
src/index.tsRivet proxy now forwards requests to the engine at
localhost:6420instead of using
registry.handler().Prevents the:
conflict.
src/actors/user-actor.tsreceiveMessage()now returns:Includes per-module session URLs in responses.
docker-compose.ymlFixed:
A2A_ALLOWED_KEYdefault valuesrc/config.tsAdded:
Configured to use port
8002.Rewritten
prompts/system.txtReworked into a conversational step-by-step flow.
Added explicit rule:
Updated
agents/*.md(6 files)Updated:
Verified
resume-builder:8002interview-service:8007roleplay-service:8008qscore-service:8000Outcome
The chat system can now: