Skip to content

Add cleared-compliance test employee + fix dead Groq model name - #18

Open
rahulkini31 wants to merge 2 commits into
nasscomAI:mainfrom
rahulkini31:student/rahul-bangalore
Open

Add cleared-compliance test employee + fix dead Groq model name#18
rahulkini31 wants to merge 2 commits into
nasscomAI:mainfrom
rahulkini31:student/rahul-bangalore

Conversation

@rahulkini31

Copy link
Copy Markdown

What I changed

  1. First task: added a new employee EMP-2026-0849 (Arjun Reddy, Platform Engineering, L4) to data/employees.json, and their compliance record — already overall_status: CLEARED — to data/compliance_state.json, so the agent can be exercised on the straight-through path (no ask_human pause), as distinct from EMP-2026-0847/0848 which are both PENDING.
  2. Bonus fix: agent.py's call_llm() hardcoded the model llama-3.3-70b-versatile, which Groq has since retired from its catalogue — every fresh GROQ_API_KEY hit a 404 model_not_found on the very first LLM call, before a student saw any agent behavior at all. Swapped to openai/gpt-oss-120b (currently available on Groq's free tier) behind a single GROQ_MODEL constant, and updated the --dry-run provider line to print it instead of the old hardcoded string.

What I tested

  • python agent.py --dry-run — all file/tool checks pass, JSON parses cleanly for both edited files.
  • python agent.py --employee EMP-2026-0849 — with the model fix in place, the agent completes the full ReAct loop end to end: retrieves the profile, confirms compliance CLEARED, goes straight to provision_access (no ask_human pause, correctly distinguishing this from the PENDING employees), and sends the welcome email to arjun.reddy@meridian.com — the real address from the profile, not the employee_id, per the system prompt's PII-in-logs-vs-email rule.
  • Ran the existing EMP-2026-0847 (PENDING) case too, to confirm the fix didn't change the ask_human path — still pauses for confirmation as before.

Notes for the reviewer

The model-name fix (commit 2) goes slightly beyond what docs/first_task.md suggests as a stretch change — it touches agent.py rather than a docs file. I included it because without it, the repo's core "run the real agent" instruction fails for literally any student picking up a fresh Groq key today, which seemed worth flagging and fixing rather than working around silently. Happy to split it into a separate PR if you'd rather review it independently from the first-task change.

Adds Arjun Reddy (Platform Engineering, L4) with overall_status:
CLEARED so the agent can be exercised on the straight-through path
(no ask_human pause), compared against EMP-2026-0847/0848 which are
both PENDING. Verified with python agent.py --dry-run (JSON valid)
and python agent.py --employee EMP-2026-0849 (agent went straight to
provisioning + welcome email, as expected for a cleared employee).
call_llm() hardcoded 'llama-3.3-70b-versatile', which Groq has since
retired from its catalogue — every fresh GROQ_API_KEY gets a 404
model_not_found on the very first LLM call, before a student sees any
agent behavior at all. Swapped to openai/gpt-oss-120b (currently
available on Groq's free tier) via a single GROQ_MODEL constant, and
updated the --dry-run provider line to print it instead of the old
hardcoded string. Verified: python agent.py --employee EMP-2026-0849
now completes the full ReAct loop end to end.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant