ak journal
ak journal show
Resolve one registered project's journal by slug or filename and print the complete Markdown record.
Use ak journal show after ak journal list when you need the full historical
record rather than its summary.
Usage
ak journal show <id-or-slug>Provide exactly one of these forms:
- a slug such as
fix-install-race; - a filename stem such as
2026-07-27-fix-install-race; - a
.mdfilename such as2026-07-27-fix-install-race.md.
The value is resolved only inside the selected project's plans/journals/
directory. Path separators and traversal are rejected in filename lookup.
Option
| Flag | Default | Description |
|---|---|---|
--project <name> | Project registered for the current working directory | Select an exact registered project name. |
From an unregistered current directory, lookup uses the directory's base name
as a registry name. It can therefore select another registered project with
the same name. Register the directory or pass a valid --project explicitly.
Examples
ak journal show 2026-07-27-fix-install-race
ak journal show fix-install-race --project myproj
ak journal show fix-install-race --project myproj --jsonA short slug must resolve to exactly one file. If entries on different dates share that slug, use the date-prefixed filename stem to disambiguate.
Output and privacy
Pretty output adds a title and date - filename header, then prints the stored
Markdown. Plain output prints the stored Markdown body exactly. JSON success
uses kind=journal.show; data includes summary fields plus body and the
absolute path.
--quiet suppresses success output. Successful output can contain the complete
journal, internal project details, and an absolute local path. Review or redact
it before logging, pasting into an issue, or sharing it outside the project.
The command is local and read-only. It performs no network, auth, process, prompt, preview, cache, or filesystem mutation.
Exit status
| Exit | Meaning |
|---|---|
0 | Exactly one entry was resolved and printed. |
1 | The entry or registered project could not be found, or a read failed. |
2 | Project selection, ID resolution, ambiguity, or argument parsing was invalid. |
An unknown explicit --project is classified as exit 2, while a missing
entry in a valid project is exit 1. With --json, these failures can produce
no JSON error envelope; use the process exit code.