Title: GitHub Actions runner logs for every job, in Console
URL: https://codemany.com/features/job-logs
Description: Codemany keeps every job's runner logs in Codemany Console, with a plain hint when a job failed because a tool is missing. Find why a job broke fast.
All pages as Markdown: https://codemany.com/llms.txt

---

[Home](https://codemany.com/) › [Features](https://codemany.com/features)

# Job logs and failure hints

Codemany keeps the GitHub Actions runner logs of every job and shows them in Codemany Console and the app. When a job fails because a tool is missing, it says which one.

## Where logs live

Each machine saves the log of every job it runs, in Codemany's own folder. Old logs are removed over time, so they don't fill the disk. Codemany also sends job logs to Codemany Console. Secrets are masked on your machine first. Code never leaves your machine.

So you can read a job's log from any device, not just the machine that ran it.

## Logs from every machine in one place

A red CI check tells you a job failed. It doesn't tell you which machine ran it. Console shows each machine's newest runs, with each job's log. Open a run, and the log is right there.

You can also watch jobs in the app, under Overview and Runs. See the [fleet view](https://codemany.com/features/fleet-view) and [Machines › Console](https://codemany.com/docs/machines#console).

## Failure hints for missing tools

When a job fails, Codemany reads the end of its log. It looks for signs that a tool is missing or too old. Then it names the tool and the line that showed it. For example:

```
Failed here: mapfile: command not found (needs Bash 4 or newer)
```

Codemany can then install the tool. It holds the job's next run for a machine that has it. Jobs from public repos are left out.

## Xcode test notes

Some Macs run jobs as a separate user per runner. There, Xcode tests need a setting turned on. If it is off, the test can't start. That would look like a flaky test.

So the log ends with an error instead. It names the setting to turn on: **Allow Xcode tests on runners**.

## Logs in GitHub still work

GitHub still schedules each job and shows its log, as with any runner. Nothing changes in your actions log on github.com.

For the service itself on Linux, read its own logs and run a health check:

```
journalctl --user -u codemany
codemany doctor
```

Those GitHub self-hosted runner logs help when a machine stops taking jobs. See [self-hosted runner offline](https://codemany.com/problems/self-hosted-runner-offline) and [Troubleshooting](https://codemany.com/docs/troubleshooting).

## Privacy

Here is what goes to Console:

- Runner states.
- Short run summaries: names, status and times.
- Job logs, with secrets masked on your machine.

Your code never goes. To turn Console off, use Settings › General on a Mac or Account on Linux. Or run `codemany console off`. Everything that leaves your machine is listed in [Security and privacy](https://codemany.com/docs/security).

## Questions

### Do logs still show in GitHub?

Yes. GitHub still shows each job's log.

### What is a failure hint?

A short note when a job failed because a tool is missing or too old. It names the tool and the log line that showed it.

### Where are the logs kept?

On the machine, and in Codemany Console, so you can read them from any device. Secrets are masked first. See [Security and privacy](https://codemany.com/docs/security) for what leaves your machine.

## Related

Read next: [the fleet view](https://codemany.com/features/fleet-view), [self-hosted runner offline](https://codemany.com/problems/self-hosted-runner-offline), [Troubleshooting](https://codemany.com/docs/troubleshooting), [Security and privacy](https://codemany.com/docs/security) and [Codemany Console](https://codemany.com/docs/machines#console).

Codemany is $20 a month for 2 machines. Try it free for 14 days, with no card.

[Start a 14-day trial](https://codemany.com/docs/get-started)