# Console access

The console is a target's standard input and output. You can type in it, you can read it, and that is the whole surface. There is no root shell and no file browser.

## Which targets have one

Containers and game servers do. Databases do not, because a Postgres does not take commands on stdin, and offering a prompt for one would be a control that could not work. For a database the equivalent is the query log, which streams the same way and is not written to disk either.

## From a terminal

```
kraftify logs <id> --attach
```

With `--attach` the console is bidirectional, so anything you type is sent to the target. Detach with `Ctrl+C`; the target keeps running.

## From the dashboard

The dashboard has the same console in a browser tab, for the times you want a screenshot rather than a scrollback. Both attach to the same stream, so two of them at once interleaves confusingly. Pick one.

## From an agent

The [MCP server](/docs/mcp) exposes `kraftify_logs` for reading. Writing to a console from an agent is deliberately not exposed.

> Console output is never written to disk. If you need to keep it, redirect it yourself. See What we store.