From a coding question to a video walkthrough.

Connect Codecast

You need an Armature beta account and Claude Code or Codex on Mac or Linux. If you have an invite, create your account or log in. If not, join the waitlist.

1. Open Codecast setup while signed in.
2. Copy its installation prompt into your coding agent and review the installation steps it proposes.
3. Follow the browser connection flow and approve the intended connection. Keep connection codes and credentials private.
4. Start a fresh agent session if the client needs one to discover the installed skill and tools, then ask for an explanation.

Use the live setup prompt rather than an installation command copied from an old post. Available integrations and installation details can change.

Ask a useful question

Tell the agent what you want to understand, and name the relevant change or component when you can. You can ask for an overview, the underlying ideas, the code itself, or both.

/codecast explain how requests move through this repo
/codecast explain the bug you just fixed and why the fix works
/codecast explain this PR compared with the base branch
/codecast explain this plan before we build it

For a PR walkthrough, the agent needs the intended base and head revisions available locally. For a plan, it needs the plan text; an explanation of a proposal is not evidence that the code has been implemented.

The agent selects relevant code ranges and supplies context explaining the question, background and important ideas. The video cannot inspect files or conversation details that were not supplied. If the result misses an important dependency, check the selected context rather than assuming the video author saw the whole repository.

Compatible chat hosts show a progress and video card. Other clients provide a browser player link. If a private player link expires, ask the agent to reopen the existing job instead of generating another video.

Understand what you share

Codecast sends the explanation request, selected code or diff excerpts, and supporting context such as a plan or relevant background. The collector does not automatically walk and upload the entire repository.

Sensitive-path and content filters provide defense in depth, not a complete secret scanner. Check that you are authorized to share the material. Do not include credentials, customer records or unrelated private conversation just because the agent can read them.

Context is processed to generate the explanation, including by the services described in the Armature privacy policy. Never publish a private player link as if it were a permanent public demo.

Troubleshooting

The agent cannot find Codecast

Check that installation and connection completed for the client you are actually using. Try a new client session, then consult the current setup page. Do not paste a credential into a public issue or change security settings to bypass an error.

There is progress text but no video card

Ask the agent to open the existing job’s player. Embedded cards depend on the host; a browser player is the fallback. Missing UI alone is not a reason to submit the same request again.

The explanation is incomplete or incorrect

Compare it with the selected code and the actual diff. Clarify the question or provide the missing context. Treat a walkthrough as an aid to understanding, not an automated correctness or security review.

The job reports a failure

Keep its job ID and error message. Ask the agent to check that existing job before retrying; do not start repeated duplicate generations. For help, send a non-sensitive description to hiarmature@gmail.com. Do not email secrets or private source code.