Joshua 5:14

Look at where Joshua is standing when this happens: just outside the walls of Jericho, the first fortified city he has to take, with no siege equipment, no army of professionals, just a nation that spent forty years wandering. Verse 13 (right before this one) shows Joshua looking up and seeing a man standing there with a drawn sword. Joshua asks the obvious military question: "Are you for us or against us?" And the answer he gets is startling — "Neither." This figure isn't there to be recruited to Joshua's side. He's not a mascot for Team Israel. He's come as Commander, the one giving orders, not taking sides in a dispute between armies.

Then watch what Joshua does. He doesn't salute. He doesn't ask for battle strategy first. He falls facedown on the ground and asks, "What does my Lord have to say to His servant?" That word "worship" isn't in this verse explicitly in the BSB translation you have, but the posture — face to the dirt — is the same posture Abram took in Genesis 17:3 when God spoke to him, and it's the posture reserved in the Old Testament for God alone, not for created angels (compare how angels react in Revelation 22:8-9 when someone tries to worship them — they refuse it immediately).

That's the detail easy to miss: this "Commander of the LORD's army" accepts worship. He doesn't stop Joshua and say "get up, I'm just a messenger." Tyndale Christians have long debated exactly who this figure is — the majority reading across church history (and several of the old commentators) is that this is a pre-incarnate appearance of the Son of God, sometimes called a Christophany, precisely because he receives worship no ordinary angel would accept Matthew Henry. Others argue it's simply an unusually exalted angel acting as God's representative. Either way, the scene marks a turning point in the book: Joshua stops being the one giving orders and becomes, for a moment, the one taking them — before God ever hands him the battle plan for Jericho in chapter 6.

The book of Joshua covers events traditionally dated to around 1400 BC (though some scholars argue for a later date closer to 1200 BC), right after the death of Moses. The people of Israel have just crossed the Jordan River on dry ground — an echo of the Red Sea crossing a generation earlier — and set up camp at Gilgal, right in enemy territory. Jericho sits in front of them: a walled city, shut tight, because the people inside have heard what happened to Egypt and are terrified ( Joshua 2:9-11 tells us this directly through Rahab's words).

This is a raw, dangerous moment for Israel. They've just performed mass circumcision on an entire generation of men who grew up in the wilderness without it ( Joshua 5:2-9) — meaning the whole camp was physically vulnerable, recovering from surgery, at the exact moment they were deepest into hostile land Keil-Delitzsch Old Testament. They've just eaten the produce of Canaan for the first time and the manna that fed them for forty years has stopped ( Joshua 5:11-12). The safety net is gone. No more daily bread falling from heaven, no more distinguishing mark of uncircumcision to separate them from the nations around them — they are now fully exposed, fully committed, standing at the edge of a war they cannot win by numbers or experience.

It's in this exact moment — not before the crossing, not before the circumcision, but right before the first battle — that God shows up in this arresting form: a man with a drawn sword. Ancient readers would have recognized this as a war scene. A "commander" with a "host" (an army) drawn up for battle was a picture straight out of their own world, where armies had generals and long, visible battle lines. The difference here is that this general isn't Israel's employee. He commands the army; Joshua serves under him.

The title here is שַׂר (sar, H8269) — a head person, someone of rank — paired with צָבָא (tsâbâʼ, H6635), meaning an army, a mass of organized fighters Strong's. Put together, sar tsava YHWH means "Commander of the army of the LORD" — and that word for army is the same word used elsewhere for the stars of heaven and for angelic hosts, which is part of why so many readers through history have heard this as more than a human military title.

Notice too what Joshua does physically: נָפַל (nâphal, H5307), "to fall," combined with פָּנִים (pânîym, H6440), "face," and אֶרֶץ (ʼerets, H776), "ground" or "earth" — he fell facedown to the ground Strong's. This isn't a polite bow. It's total collapse, the body language of someone who suddenly understands he is small and the one in front of him is not.

Then Joshua calls him אָדוֹן (ʼâdôwn, H113) — "Lord," "sovereign," the one who rules — and calls himself עֶבֶד (ʻebed, H5650), "servant" or "slave" Strong's. That word pair, Lord and servant, flips the entire relationship Joshua thought he had walking into this conversation. He came expecting to ask a scout a tactical question. He leaves having named himself a slave under someone else's command.

It's also worth just sitting with the name יְהוֹשׁוּעַ (Yᵉhôwshûwaʻ, H3091) — Joshua's own name means "Yahweh saves" Strong's, the same root that gives us the name Jesus later. The man named "The LORD Saves" is the one falling facedown before the true source of the salvation his own name points to.

This is one of those places in the Old Testament where you can feel the seams of the story straining forward toward something — someone — the text hasn't fully named yet. A figure who commands God's own armies, who speaks with divine authority, and who receives worship without correcting the worshiper — that's not the profile of a created being. It's the profile of God himself showing up in a form a man like Joshua could actually stand in front of and survive.

Centuries later, the prophet Isaiah would speak of a coming "leader and commander of the peoples" ( Isaiah 55:4) — language that echoes right back to this scene. And centuries after that, when Jesus quotes Psalm 110 and asks the religious leaders how the Messiah can be both David's son and David's Lord ( Matthew 22:44, Luke 20:42), he's pointing at the exact same mystery this scene raises: how can a man bow down to another man and call him "Lord" unless that other man is more than a man?

When Thomas finally sees the risen Jesus and says "My Lord and my God!" ( John 20:28), he's doing, in words, what Joshua did in posture — falling before someone who is unmistakably God, and having that worship accepted, not deflected. That's the thread. The book of Daniel later gives us Michael, "the great prince who stands watch over your people" ( Daniel 12:1), fighting on Israel's behalf — and Revelation 12:7 shows a similar heavenly army at war. Some readers connect this Commander directly to that angelic warfare; others see him as something greater still, standing above even the angel armies as their King.

You don't need the debate settled to feel the weight of it: before Jesus ever walked into Galilee healing the sick, God had already shown Joshua what he looks like leading an army — not recruited to a side, but commanding the whole field, and worthy of a face in the dirt.

Here's the question this verse puts to you, personally: are you trying to get God to sign up for your battle plan, or are you willing to find out you're actually a soldier in his? Joshua's first instinct — "are you for us or against us?" — is completely natural. It's what you do when you're scared and outmatched: you look for allies. You want God on your team, backing your plan, blessing your effort, showing up when you call.

The Commander's answer, "Neither," should sting a little. It stings because it means your crisis, your Jericho, your impossible wall in front of you, isn't actually about recruiting God to your side of the fight. It's about finding out whose side you're already supposed to be standing on.

And here's the cost this verse actually asks of you: face-in-the-dirt honesty. Not a polite nod toward God on your way to your own plans. Joshua's whole posture changes the moment he understands who he's talking to — from a man asking questions to a servant asking for orders. "What does my Lord have to say to His servant?" is a genuinely dangerous question to ask, because it means you actually have to do whatever the answer is. Notice, too, that Joshua asks this question before he's told anything about Jericho, before there's a strategy on the table. He surrenders control before he knows what surrender will cost him.

That's the pattern for you today. Before you know what God is going to ask of you this week, are you willing to say those words first? Not "bless my plan," but "what do you have to say to your servant" — and then actually wait, facedown, for the answer.

• Lord, forgive me for the times I've tried to recruit you to my side instead of asking whether I'm standing on yours.
• Teach me the posture of Joshua — not a polite nod toward you, but real surrender, before I even know what you're going to ask of me.
• Where I'm facing my own Jericho — a wall that looks impossible — help me remember you command the field; I don't have to.
• Give me the courage to ask, "What do you have to say to your servant?" and actually wait for the answer instead of rushing ahead with my own plan.
• Thank you that you didn't stay distant — that the same God who stood before Joshua came all the way to us in Jesus, worthy of worship and near enough to know.

• When was the last time you asked God to bless your plan instead of asking what his plan actually was?
• What's your "Jericho" right now — the wall in front of you that feels too big for the resources you have?
• If God showed up right now with a drawn sword, not to fight for you but to command you, how would that change what you're doing this week?
• Is there an area of your life where you've quietly assumed you're the general and God is your consultant?
• What would it cost you, specifically, to say "what do you have to say to your servant" and mean it?