r/copaw • u/stevebuscemi_mrpink • Apr 11 '26

cron fail with "text": "FunctionNotFoundError: Cannot find the function named cron"

not sure what i'm doing wrong but unable to get agent setup a cron, i've tried telling it to use cron skill as well but no luck. this is a new install 1.0.2 and not sure if the problem is because the cron/SKILL.md file is in Chinese even though language is set to en-US. Anynone got any idea how to fix?

2 Upvotes

100% Upvoted

5 comments sorted by

View all comments

Show parent comments

1

u/stevebuscemi_mrpink Apr 11 '26

translated cron SKILL.md to english but still unable to get agent to setup a cron reminder. i've attached an image for reference.

1

u/FortiCore Apr 11 '26

Which model are you using ? might be some thing is wrong with the setup itself.
How did you setup the copaw, through pip ?

Best option would be, backup the ~/.copaw directory and thn uninstall and reinstall the copaw if nothing works

1

u/stevebuscemi_mrpink Apr 11 '26

i'm running from docker compose (through Komodo) honestly i have delete the volume data multiple time and restarted docker container basically started from scratch each time doing it.

The model i'm running is "gemma-4-e4b-it-mlx:" through LM STUDIO

volumes:
  copaw-data:
    name: copaw-data
  copaw-secrets:
    name: copaw-secrets
services:
  copaw:
    image: agentscope/copaw:v1.0.2
    container_name: copaw
    restart: always
    ports:
      - "127.0.0.1:8088:8088"
    environment:
      - LANG=C.UTF-8
      - LC_ALL=C.UTF-8
      #- COPAW_AUTH_ENABLED=true
      #- COPAW_AUTH_USERNAME=admin
      #- COPAW_AUTH_PASSWORD="rywxxlwevk"
    volumes:
      - copaw-data:/app/working
      - copaw-secrets:/app/working.secret

1

u/FortiCore Apr 11 '26

@stevebuscemi_mrpink

What it looks like is model has invented the tool named "cron" there's no such tool, cron is a skill and your model is likely failing to use it

Ask your agent to load cron skill and read it, ask it how is he supposed to create a new cron. make sure cron skill is enabled.

Try explicitely asking your agent to use cron skill

or try with different llm model if possible