[GH-ISSUE #124] [BUG]: No deliverables folder being created after workflow execution

kerem commented

2026-02-27 07:20:08 +03:00

Owner

Originally created by @tscodeler on GitHub (Feb 12, 2026).
Original GitHub issue: https://github.com/KeygraphHQ/shannon/issues/124

Describe the bug

I'm running Shannon by following the README instructions. After a workflow execution, I couldn't find the deliverables folder.

Command executed:
./shannon start URL=https://www.myapp REPO=/repos/my-app

Command log output in terminal:

✓ Systems initialized. 

Connecting to Temporal at temporal:7233...
✓ Workflow started: www-myapp_shannon-1770844390609

  Target:     https://www.myapp
  Repository: /target-repo

Monitor progress:
  Web UI:  http://localhost:8233/namespaces/default/workflows/www-myapp_shannon-1770844390609
  Logs:    ./shannon logs ID=www-myapp_shannon-1770844390609
  Query:   ./shannon query ID=www-myapp_shannon-1770844390609

Output:
  Reports: ./audit-logs/www-myapp_shannon-1770844390609

Folder after execution:

ls  ./audit-logs/www-myapp_shannon-1770844390609
agents       prompts      session.json workflow.log

Audit logs result:

Workflow COMPLETED
────────────────────────────────────────
Workflow ID: www-myapp_shannon-1770844390609
Status:      completed
Duration:    179m 54s
Total Cost:  $35.0545
Agents:      12 completed

Agent Breakdown:
  - pre-recon (26m 2s, $5.4728)
  - recon (27m 24s, $6.3952)
  - injection-vuln (13m 14s, $1.8425)
  - injection-exploit (3m 26s, $0.8923)
  - xss-vuln (45m 34s, $5.3357)
  - xss-exploit (19m 38s, $0.6494)
  - auth-vuln (104m 45s, $7.3156)
  - auth-exploit (18m 59s, $3.2239)
  - ssrf-vuln (3m 57s, $0.8303)
  - authz-vuln (13m 15s, $2.0737)
  - authz-exploit (2m 37s, $0.6240)
  - report (2m 36s, $0.3991)

Temporal dashboard:

Expected behaviour

Deliverables folder is generated in host or container.

Actual behaviour

No deliverables folder is generated

Pre-submission checklist (required)

I have searched the existing open issues and confirmed this bug has not already been reported.
I am running the latest released version of shannon.

If applicable

I have included relevant error messages, stack traces, or failure details.
I have checked the audit logs and pasted the relevant errors.
I have inspected the failed Temporal workflow run and included the failure reason.
I have included clear steps to reproduce the issue.
I have redacted any sensitive information (tokens, URLs, repo names).

Debugging details

No response

Screenshots

Authentication method used

ANTHROPIC_API_KEY

Full ./shannon command with all flags used (with redactions)

./shannon start URL=https://www.myapp REPO=/repos/my-app

No response

Are you using any experimental models or providers other than default Anthropic models?

No

If Yes, which one (model/provider)?

No response

OS (with version)

15.5

Docker version ('docker -v')

24.0.6

Additional context

No response

Originally created by @tscodeler on GitHub (Feb 12, 2026). Original GitHub issue: https://github.com/KeygraphHQ/shannon/issues/124 ### Describe the bug I'm running Shannon by following the README instructions. After a workflow execution, I couldn't find the deliverables folder. Command executed: `./shannon start URL=https://www.myapp REPO=/repos/my-app` Command log output in terminal: ``` ✓ Systems initialized. Connecting to Temporal at temporal:7233... ✓ Workflow started: www-myapp_shannon-1770844390609 Target: https://www.myapp Repository: /target-repo Monitor progress: Web UI: http://localhost:8233/namespaces/default/workflows/www-myapp_shannon-1770844390609 Logs: ./shannon logs ID=www-myapp_shannon-1770844390609 Query: ./shannon query ID=www-myapp_shannon-1770844390609 Output: Reports: ./audit-logs/www-myapp_shannon-1770844390609 ``` Folder after execution: ``` ls ./audit-logs/www-myapp_shannon-1770844390609 agents prompts session.json workflow.log ``` Audit logs result: ``` Workflow COMPLETED ──────────────────────────────────────── Workflow ID: www-myapp_shannon-1770844390609 Status: completed Duration: 179m 54s Total Cost: $35.0545 Agents: 12 completed Agent Breakdown: - pre-recon (26m 2s, $5.4728) - recon (27m 24s, $6.3952) - injection-vuln (13m 14s, $1.8425) - injection-exploit (3m 26s, $0.8923) - xss-vuln (45m 34s, $5.3357) - xss-exploit (19m 38s, $0.6494) - auth-vuln (104m 45s, $7.3156) - auth-exploit (18m 59s, $3.2239) - ssrf-vuln (3m 57s, $0.8303) - authz-vuln (13m 15s, $2.0737) - authz-exploit (2m 37s, $0.6240) - report (2m 36s, $0.3991) ``` Temporal dashboard: <img width="1406" height="82" alt="Image" src="https://github.com/user-attachments/assets/ab03ac6d-ce02-4bd8-9bda-6f3680b0f905" /> ### Expected behaviour Deliverables folder is generated in host or container. ### Actual behaviour No deliverables folder is generated ### Pre-submission checklist (required) - [x] I have searched the existing open issues and confirmed this bug has not already been reported. - [x] I am running the latest released version of `shannon`. ### If applicable - [x] I have included relevant error messages, stack traces, or failure details. - [ ] I have checked the audit logs and pasted the relevant errors. - [x] I have inspected the failed Temporal workflow run and included the failure reason. - [x] I have included clear steps to reproduce the issue. - [x] I have redacted any sensitive information (tokens, URLs, repo names). ### Debugging details _No response_ ### Screenshots <img width="1689" height="665" alt="Image" src="https://github.com/user-attachments/assets/7e3d0086-107b-429d-bd8c-7eb69bdfb7ee" /> ### Authentication method used ANTHROPIC_API_KEY ### Full ./shannon command with all flags used (with redactions) `./shannon start URL=https://www.myapp REPO=/repos/my-app` _No response_ ### Are you using any experimental models or providers other than default Anthropic models? No ### If Yes, which one (model/provider)? _No response_ ### OS (with version) 15.5 ### Docker version ('docker -v') 24.0.6 ### Additional context _No response_

kerem closed this issue

2026-02-27 07:20:08 +03:00

kerem commented

2026-02-27 07:20:08 +03:00

Author

Owner

@ezl-keygraph commented on GitHub (Feb 12, 2026):

Thanks for reporting @tscodeler

Currently deliverables folder is being created inside the target repo which will be ./repos/target-repo/deliverables.

In the future updates it will be included in the ./audit-logs/target_url_shannon-1770844390609 folder along with the other files related to the run

@ezl-keygraph commented on GitHub (Feb 12, 2026): Thanks for reporting @tscodeler Currently deliverables folder is being created inside the target repo which will be `./repos/target-repo/deliverables`. In the future updates it will be included in the `./audit-logs/target_url_shannon-1770844390609` folder along with the other files related to the run

kerem commented

2026-02-27 07:20:08 +03:00

Author

Owner

@tscodeler commented on GitHub (Feb 12, 2026):

@ezl-keygraph still can't find the deliverables under the target-repo folder

@tscodeler commented on GitHub (Feb 12, 2026): @ezl-keygraph still can't find the deliverables under the target-repo folder

kerem commented

2026-02-27 07:20:08 +03:00

Author

Owner

@ezl-keygraph commented on GitHub (Feb 12, 2026):

@tscodeler Could you share the terminal output by running the below cmd from shannon folder?

ls ./repos/*/deliverables

@ezl-keygraph commented on GitHub (Feb 12, 2026): @tscodeler Could you share the terminal output by running the below cmd from shannon folder? ``` ls ./repos/*/deliverables ```

kerem commented

2026-02-27 07:20:08 +03:00

Author

Owner

@tscodeler commented on GitHub (Feb 13, 2026):

@ezl-keygraph command output:
no matches found: ./repos/*/deliverables

@tscodeler commented on GitHub (Feb 13, 2026): @ezl-keygraph command output: `no matches found: ./repos/*/deliverables`

kerem commented

2026-02-27 07:20:08 +03:00

Author

Owner

@ezl-keygraph commented on GitHub (Feb 13, 2026):

@tscodeler I think you have set the repo as REPO=/repos/my-app.
In the latest version you should place the target repo inside ./repos and only pass the repo name in the REPO= flag.
For eg: if the repo name is test then the flag should be REPO=test

@ezl-keygraph commented on GitHub (Feb 13, 2026): @tscodeler I think you have set the repo as `REPO=/repos/my-app`. In the latest version you should place the target repo inside `./repos` and only pass the repo name in the `REPO=` flag. For eg: if the repo name is test then the flag should be `REPO=test`

kerem commented

2026-02-27 07:20:08 +03:00

Author

Owner

@tscodeler commented on GitHub (Feb 13, 2026):

@ezl-keygraph you mean this:

ls .repos/
my-app

./shannon start URL=https://www.myapp REPO=my-app
Starting Shannon containers...
service "worker" refers to undefined volume my-app: invalid compose project

Is the folder called "repos" or ".repos"?

@tscodeler commented on GitHub (Feb 13, 2026): @ezl-keygraph you mean this: ``` ls .repos/ my-app ``` ``` ./shannon start URL=https://www.myapp REPO=my-app Starting Shannon containers... service "worker" refers to undefined volume my-app: invalid compose project ``` Is the folder called "repos" or ".repos"?

kerem commented

2026-02-27 07:20:08 +03:00

Author

Owner

@ezl-keygraph commented on GitHub (Feb 13, 2026):

@tscodeler I have added some steps that will be helpful

Update Shannon

git pull

If you pulled new changes and need a clean container rebuild (no cache), do

./shannon start REBUILD=true URL=https://www.myapp REPO=my-app

Otherwise, normal scan run:

./shannon start URL=https://www.myapp REPO=my-app

Notes

Put the target repo under ./repos/ (e.g., ./repos/my-app).
Deliverables end up at

./repos/my-app/deliverables

@ezl-keygraph commented on GitHub (Feb 13, 2026): @tscodeler I have added some steps that will be helpful 1. Update Shannon ```bash git pull ``` 2. If you pulled new changes and need a clean container rebuild (no cache), do ```bash ./shannon start REBUILD=true URL=https://www.myapp REPO=my-app ``` 3. Otherwise, normal scan run: ```bash ./shannon start URL=https://www.myapp REPO=my-app ``` Notes * Put the target repo under `./repos/` (e.g., `./repos/my-app`). * Deliverables end up at ```bash ./repos/my-app/deliverables ```

kerem commented

2026-02-27 07:20:08 +03:00

Author

Owner

@tscodeler commented on GitHub (Feb 13, 2026):

thank you @ezl-keygraph

ls .repos/
my-app

./shannon start URL=https://my-app REPO=my-app
ERROR: Repository not found at ./repos/my-app

Place your target repository under the ./repos/ directory

@tscodeler commented on GitHub (Feb 13, 2026): thank you @ezl-keygraph ``` ls .repos/ my-app ``` ``` ./shannon start URL=https://my-app REPO=my-app ERROR: Repository not found at ./repos/my-app Place your target repository under the ./repos/ directory ```

kerem commented

2026-02-27 07:20:08 +03:00

Author

Owner

@ezl-keygraph commented on GitHub (Feb 13, 2026):

@tscodeler
Hope so you're able to find the deliverables

@ezl-keygraph commented on GitHub (Feb 13, 2026): @tscodeler Hope so you're able to find the deliverables

kerem commented

2026-02-27 07:20:08 +03:00

Author

Owner

@tscodeler commented on GitHub (Feb 13, 2026):

@ezl-keygraph no, the execution was not started.

./shannon start URL=https://my-app REPO=my-app
ERROR: Repository not found at ./repos/my-app

Place your target repository under the ./repos/ directory

@tscodeler commented on GitHub (Feb 13, 2026): @ezl-keygraph no, the execution was not started. ``` ./shannon start URL=https://my-app REPO=my-app ERROR: Repository not found at ./repos/my-app Place your target repository under the ./repos/ directory ```

kerem commented

2026-02-27 07:20:08 +03:00

Author

Owner

@tscodeler commented on GitHub (Feb 18, 2026):

@ezl-keygraph any recommendation on that?

@tscodeler commented on GitHub (Feb 18, 2026): @ezl-keygraph any recommendation on that?

kerem commented

2026-02-27 07:20:08 +03:00

Author

Owner

@ezl-keygraph commented on GitHub (Feb 18, 2026):

@tscodeler

Many things have changed in the shannon since last week. I would suggest you to pull the latest code and follow the steps from the latest README.md If you are still facing problems with running shannon, please provide the new logs from temporal and workflow.log which will help us to reproduce the error. You can also join our discord and ping me there. I can help you with running shannon. Thanks!

@ezl-keygraph commented on GitHub (Feb 18, 2026): @tscodeler Many things have changed in the shannon since last week. I would suggest you to pull the latest code and follow the steps from the latest `README.md` If you are still facing problems with running shannon, please provide the new logs from temporal and `workflow.log` which will help us to reproduce the error. You can also join our discord and ping me there. I can help you with running shannon. Thanks!

kerem commented

2026-02-27 07:20:08 +03:00

Author

Owner

@tscodeler commented on GitHub (Feb 19, 2026):

@ezl-keygraph The latest code is working well now, and the deliverables folder has been generated.

@tscodeler commented on GitHub (Feb 19, 2026): @ezl-keygraph The latest code is working well now, and the deliverables folder has been generated.

Rows
Columns

[GH-ISSUE #124] [BUG]: No deliverables folder being created after workflow execution #42

Describe the bug

Expected behaviour

Actual behaviour

Pre-submission checklist (required)

If applicable

Debugging details

Screenshots

Authentication method used

Full ./shannon command with all flags used (with redactions)

Are you using any experimental models or providers other than default Anthropic models?

If Yes, which one (model/provider)?

OS (with version)

Docker version ('docker -v')

Additional context